diff --git a/docs/en-US/network-offering-usage-record-format.xml b/docs/en-US/network-offering-usage-record-format.xml index 853554460f6..5dfc36178ff 100644 --- a/docs/en-US/network-offering-usage-record-format.xml +++ b/docs/en-US/network-offering-usage-record-format.xml @@ -1,3 +1,27 @@ + + +%BOOK_ENTITIES; +]> + + +
Network Offering Usage Record Format @@ -16,5 +40,4 @@ 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 -
- + diff --git a/docs/en-US/network-offerings.xml b/docs/en-US/network-offerings.xml index 87af7eb916b..ccfb93cc4cc 100644 --- a/docs/en-US/network-offerings.xml +++ b/docs/en-US/network-offerings.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Network Offerings For the most up-to-date list of supported network services, see the CloudPlatform UI or call listNetworkServices. diff --git a/docs/en-US/network-service-providers.xml b/docs/en-US/network-service-providers.xml index 2c711ca1cef..af570977259 100644 --- a/docs/en-US/network-service-providers.xml +++ b/docs/en-US/network-service-providers.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Network Service Providers For the most up-to-date list of supported network service providers, see the CloudPlatform UI or call listNetworkServiceProviders. @@ -13,5 +32,4 @@ Supported Network Service Providers CloudPlatform ships with an internal list of the supported service providers, and you can choose from this list when creating a network offering. -
diff --git a/docs/en-US/network-usage-record-format.xml b/docs/en-US/network-usage-record-format.xml index fbcc88318cb..742f26be9e6 100644 --- a/docs/en-US/network-usage-record-format.xml +++ b/docs/en-US/network-usage-record-format.xml @@ -1,3 +1,27 @@ + + +%BOOK_ENTITIES; +]> + + +
Network Usage Record Format For network usage (bytes sent/received), the following fields exist in a usage record. @@ -13,5 +37,4 @@ 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 -
- +
diff --git a/docs/en-US/networking-in-a-pod.xml b/docs/en-US/networking-in-a-pod.xml index 39287154278..1033b15ebc3 100644 --- a/docs/en-US/networking-in-a-pod.xml +++ b/docs/en-US/networking-in-a-pod.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Networking in a Pod Figure 2 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. @@ -19,5 +38,4 @@ 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. - -
+ diff --git a/docs/en-US/networking-in-a-zone.xml b/docs/en-US/networking-in-a-zone.xml index e5450bc614c..6f4e92a97f1 100644 --- a/docs/en-US/networking-in-a-zone.xml +++ b/docs/en-US/networking-in-a-zone.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Networking in a Zone Figure 3 illustrates the network setup within a single zone. @@ -14,5 +33,4 @@ 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. - -
+ diff --git a/docs/en-US/networking-overview.xml b/docs/en-US/networking-overview.xml index bff714fc9c7..6f244df1ea5 100644 --- a/docs/en-US/networking-overview.xml +++ b/docs/en-US/networking-overview.xml @@ -1,8 +1,27 @@ - %BOOK_ENTITIES; ]> + + +
Networking Overview @@ -13,5 +32,4 @@ Advanced. For more sophisticated network topologies. This network model provides the most flexibility in defining guest networks. For more details, see Network Setup. -
- + diff --git a/docs/en-US/networking_overview.xml b/docs/en-US/networking_overview.xml index 1080ed72622..f00094c2728 100644 --- a/docs/en-US/networking_overview.xml +++ b/docs/en-US/networking_overview.xml @@ -1,4 +1,28 @@ -
+ + +%BOOK_ENTITIES; +]> + + + +
Networking Overview CloudStack offers two types of networking scenario: @@ -8,5 +32,5 @@ Advanced. For more sophisticated network topologies. This network model provides the most flexibility in defining guest networks. For more details, see Network Setup. -
+
diff --git a/docs/en-US/nfs-shares-on-management-server.xml b/docs/en-US/nfs-shares-on-management-server.xml index dcddc47ff2a..f1c0f422f3a 100644 --- a/docs/en-US/nfs-shares-on-management-server.xml +++ b/docs/en-US/nfs-shares-on-management-server.xml @@ -1,13 +1,11 @@ - %BOOK_ENTITIES; ]>
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. + 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 the Management Server host, create two directories that you will use for primary and secondary storage. For example: @@ -38,19 +36,19 @@ STATD_OUTGOING_PORT=2020 Edit the /etc/sysconfig/iptables file. # vi /etc/sysconfig/iptables - Add the following lines at the beginning of the INPUT chain: + Add the following lines at the beginning of the INPUT chain where <NETWORK> is the network that you'll be using: --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 +-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: @@ -92,4 +90,4 @@ STATD_OUTGOING_PORT=2020 -
\ No newline at end of file + diff --git a/docs/en-US/nfs-shares-on-separate-server.xml b/docs/en-US/nfs-shares-on-separate-server.xml index 7d70d8c4e01..e2a7b39d2b2 100644 --- a/docs/en-US/nfs-shares-on-separate-server.xml +++ b/docs/en-US/nfs-shares-on-separate-server.xml @@ -1,3 +1,27 @@ + + +%BOOK_ENTITIES; +]> + + +
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. @@ -25,4 +49,4 @@ # mount -t nfs nfsservername:/nfs/share/secondary /mnt/secondary -
\ No newline at end of file +