Dynamic routing: draft v3

Author: weizhouapache

source/adminguide/networking.rst

@@ -290,11 +290,13 @@ To create a network offering:
 
    -  **Network mode**. This option indicates the mode with which the network will operate.
       Valid options are NATTED (default) or ROUTED. This applies on isolated networks only.
-      For more information on Network mode, Dynamic and Static routing, see `“Dynamic and
-      Static Routing” <networking_and_traffic.html#dynamic-and-static-routing>`_.
+      For more information on Network mode, see `“About Network
+      Mode” <networking_and_traffic.html#about-network-mode>`_.
 
    -  **Routing mode**. This option indicates the routing mode for the network offering.
       Supported types are: Static or Dynamic.
+      For more information on Routing mode, see `“About Routing
+      Mode” <networking_and_traffic.html#about-routing-mode>`_.
 
    -  **Promiscuous Mode**. Applicable for guest networks on VMware hypervisor only. It accepts the following values for desired behaviour of the network elements:
 

source/adminguide/networking/dynamic_static_routing.rst

@@ -17,26 +17,48 @@
 Dynamic and Static Routing
 -----------------------------
 
-The IPv6 static routing has been introduced in Apache CloudStack 4.17.0.0.
+For VMs on Isolated networks, the IP of VMs are not publicly accessible.
+To access the VMs from the Internet, Users need to create Load balanceing rules,
+Port Forwarding rules, enable Static NAT, or enable VPN.
+
+The IPv6 static routing feature has been introduced in Apache CloudStack 4.17.0.0, so that
+users are able to access the IPv6 address of guest VMs on Isolated networks from the Internet or public network.
 For more information, see `“IPv6 support for isolated networks and VPC Network Tiers” <../plugins/ipv6.html#isolated-network-and-vpc-network-tier>`_.
 
-From Apache CloudStack 4.20.0.0, users are able to create isolated networks and VPCs with more options
+From Apache CloudStack 4.20.0.0, users are able to create isolated networks and VPCs with ROUTED mode.
 
-- Static Routing for IPv4
-- Manage IPv4 Routing Firewall
-- Dynamic Routing for IPv4 and IPv6
+- Manage IPv4 subnets for Zones (ROOT admin/operator only)
+- Create Networks with Static Routing for IPv4
+- Manage IPv4 Routing Firewall for Networks
 - Manage AS number and BPG peers for Dynamic Routing (ROOT admin only)
+- Create Networks with Dynamic Routing for IPv4 and IPv6
 
 
 About Network Mode
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-TODO
+Network mode indicates the mode with which the isolated network or VPC will operate.
+There are two valid options
+
+- NATTED. This is the default network mode of isolated networks. The VR of isolated networks and VPCs provides Source NAT services, as well as Static NAT, Load Balancer, Port Forwarding, Vpn if the network offering supports.
+- ROUTED. For isolated networks in ROUTED mode, the VR no longer supports Source NAT, Static NAT, Load Balancer, Port Forwarding and Vpn. The supported services are Dns, Dhcp, Userdata, Firewall (for isolated networks) and Network ACL (for vpc and vpc networks).
+
+
+About Routing mode
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Routing mode indicates how routing will operate with the isolated networks with ROUTED network mode.
+There are two valid options
+
+- Static. The operators need to add the static routes to the isolated networks or VPCs in the upstream router manually.
+- Dynamic. The AS number will be automatically allocated, and BGP peer sessions will be set up automatically in the VR of the isolated networks or VPCs. The operators need to add the AS number ranges and BGP peers for each zone before creating network with Dynamic routing mode.
+
 
 Create Network and VPC Offering with ROUTED mode
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-for static and dynamic routing
+For more information, see `“Creating a New Network Offering” <networking.html#creating-a-new-network-offering>`_.
+
 TODO