etan39
/
cloudstack
mirror of https://github.com/apache/cloudstack.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

CLOUDSTACK-770

This commit is contained in:
radhikap 2013-07-11 10:26:42 +05:30
parent f56d9d7c63
commit 3e8edd74b9
3 changed files with 21 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/en-US/configure-acl.xml
View File

@ -19,7 +19,7 @@
under the License.
-->
<section id="configure-acl">
<title>Configuring Access Control List</title>
<title>Configuring Network Access Control List</title>
<para>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 and outgoing traffic to the guest networks is blocked. To open the ports,

28
docs/en-US/inter-vlan-routing.xml
View File

@ -19,16 +19,16 @@
under the License.
-->
<section id="inter-vlan-routing">
<title>About Inter-VLAN Routing</title>
<para>Inter-VLAN Routing 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.</para>
<title>About Inter-VLAN Routing (nTier Apps)</title>
<para>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.</para>
<para>This feature is supported on XenServer, KVM, and VMware hypervisors.</para>
<para>The major advantages are:</para>
<itemizedlist>
@ -88,10 +88,10 @@
</itemizedlist>
</listitem>
<listitem>
<para>The administrator can define 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.</para>
<para>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.</para>
</listitem>
</itemizedlist>
<para>The following figure shows the possible deployment scenarios of a Inter-VLAN setup:</para>

6
docs/en-US/vpc.xml
View File

@ -75,6 +75,12 @@
Translation for instances to access the Internet via the public gateway. For more
information, see <xref linkend="enable-disable-static-nat-vpc"/>.</para>
</listitem>
<listitem>
<para><emphasis role="bold">Network ACL</emphasis>: 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 <xref linkend="configure-acl"/>.</para>
</listitem>
</itemizedlist>
<formalpara>
<title>Network Architecture in a VPC</title>