diff --git a/docs/en-US/creating-network-offerings.xml b/docs/en-US/creating-network-offerings.xml
index 0269ce024cb..07f5a9e7cdf 100644
--- a/docs/en-US/creating-network-offerings.xml
+++ b/docs/en-US/creating-network-offerings.xml
@@ -22,146 +22,209 @@
under the License.
-->
- Creating a New Network Offering
- To create a network offering:
-
- Log in with admin privileges to the &PRODUCT; 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 these terms, see
-
- Specify VLAN. (Isolated guest networks only) Indicate whether
- a VLAN should be specified when this offering is used
- 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
- &PRODUCT; 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:
-
-
-
- Supported Services
- Description
- Isolated
- Shared
-
-
-
-
- DHCP
- For more information, see .
- Supported
- Supported
-
-
- DNS
- For more information, see .
- Supported
- Supported
-
-
- Load Balancer
- If you select Load Balancer, you can choose the &PRODUCT; virtual router or any other load
- balancers that have been configured in the cloud.
- Supported
- Supported
-
-
- Source NAT
- If you select Source NAT, you can choose the &PRODUCT; virtual router or any other Source
- NAT providers that have been configured in the
- cloud.
- Supported
- Supported
-
-
- Static NAT
- If you select Static NAT, you can choose the &PRODUCT; virtual router or any other Static
- NAT providers that have been configured in the
- cloud.
- Supported
- Supported
-
-
- Port Forwarding
- If you select Port Forwarding, you can choose the &PRODUCT; virtual router or any other
- Port Forwarding providers that have been configured in
- the cloud.
- Supported
- Not Supported
-
-
- VPN
- For more information, see .
- Supported
- Not Supported
-
-
- User Data
- For more information, see .
- Not Supported
- Supported
-
-
- Network ACL
- For more information, see .
- Supported
- Not Supported
-
-
- Security Groups
- For more information, see .
- Not Supported
- Supported
-
-
-
-
-
- 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
- &PRODUCT; default system service offering and any custom system service
- offerings that have been defined by the &PRODUCT; root administrator.
- For more information, see System Service Offerings.
- 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. &PRODUCT; 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 the 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 SaticNAT
- or load balancing. When the conserve mode is on, you can define more than
- one service on the same public IP.
- 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.
-
- Click Add.
-
-
-
+ Creating a New Network Offering
+ To create a network offering:
+
+
+ Log in with admin privileges to the &PRODUCT; 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 .
+ For a description of this term, see the Administration Guide.
+
+
+
+ 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 .
+
+
+ Specify VLAN. (Isolated guest networks only)
+ Indicate whether a VLAN should be specified when this offering is used.
+
+
+ VPC. This option indicate whether the guest network
+ is Virtual Private Cloud-enabled. A Virtual Private Cloud (VPC) is a private, isolated
+ part of &PRODUCT;. A VPC can have its own virtual network topology that resembles a
+ traditional physical network. For more information on VPCs, see .
+
+
+ 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 &PRODUCT; 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:
+
+
+
+
+ Supported Services
+ Description
+ Isolated
+ Shared
+
+
+
+
+ DHCP
+ For more information, see .
+ Supported
+ Supported
+
+
+ DNS
+ For more information, see .
+ Supported
+ Supported
+
+
+ Load Balancer
+ If you select Load Balancer, you can choose the &PRODUCT; virtual
+ router or any other load balancers that have been configured in the
+ cloud.
+ Supported
+ Supported
+
+
+ Firewall
+ For more information, see .
+ For more information, see the Administration
+ Guide.
+ Supported
+ Supported
+
+
+ Source NAT
+ If you select Source NAT, you can choose the &PRODUCT; virtual router
+ or any other Source NAT providers that have been configured in the
+ cloud.
+ Supported
+ Supported
+
+
+ Static NAT
+ If you select Static NAT, you can choose the &PRODUCT; virtual router
+ or any other Static NAT providers that have been configured in the
+ cloud.
+ Supported
+ Supported
+
+
+ Port Forwarding
+ If you select Port Forwarding, you can choose the &PRODUCT; virtual
+ router or any other Port Forwarding providers that have been configured in the
+ cloud.
+ Supported
+ Not Supported
+
+
+ VPN
+ For more information, see .
+ Supported
+ Not Supported
+
+
+ User Data
+ For more information, see .
+ For more information, see the Administration
+ Guide.
+ Not Supported
+ Supported
+
+
+ Network ACL
+ For more information, see .
+ Supported
+ Not Supported
+
+
+ Security Groups
+ For more information, see .
+ Not Supported
+ Supported
+
+
+
+
+
+
+ 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 &PRODUCT; default system service offering and any custom
+ system service offerings that have been defined by the &PRODUCT; root
+ administrator.
+ For more information, see .
+ For more information, see the Administration Guide.
+
+
+ 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. &PRODUCT; 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 SaticNAT or load balancing. When the conserve
+ mode is on, you can define more than one service on the same public IP.
+
+ 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
+ firewall rules by using the createFirewallRule command.
+
+
+
+ Tags. Network tag to specify which physical network
+ to use.
+
+
+
+
+ Click Add.
+
+
diff --git a/docs/en-US/networks.xml b/docs/en-US/networks.xml
index a7b9ea12466..830576902b1 100644
--- a/docs/en-US/networks.xml
+++ b/docs/en-US/networks.xml
@@ -45,4 +45,5 @@
-
\ No newline at end of file
+
+
diff --git a/docs/en-US/persistent-network.xml b/docs/en-US/persistent-network.xml
new file mode 100644
index 00000000000..e3719405c2d
--- /dev/null
+++ b/docs/en-US/persistent-network.xml
@@ -0,0 +1,99 @@
+
+
+%BOOK_ENTITIES;
+]>
+
+
+
+ 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 &PRODUCT; 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 .
+
+
+ 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.
+
+
+
+