CLOUDSTACK-2806

This commit is contained in:
radhikap 2013-07-08 16:55:56 +05:30
parent 24e9797807
commit 03c8f74e98
4 changed files with 198 additions and 119 deletions

View File

@ -144,10 +144,11 @@
<section id="acl-private-gateway"> <section id="acl-private-gateway">
<title>ACL on Private Gateway</title> <title>ACL on Private Gateway</title>
<para>The traffic on the VPC private gateway is controlled by creating both ingress and egress <para>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 network ACL rules. The ACLs contains both allow and deny rules. In addition to the default ACL
ingress traffic to the private gateway interface and all the egress traffic out from the rules, rules you might have created are also listed in the ACL drop-down list. As per the
private gateway interface are blocked. You can change this default behaviour while creating a rule, all the ingress traffic to the private gateway interface and all the egress traffic out
private gateway.</para> from the private gateway interface are blocked. You can change this default behaviour while
creating a private gateway.</para>
</section> </section>
<section id="static-route"> <section id="static-route">
<title>Creating a Static Route</title> <title>Creating a Static Route</title>

View File

@ -25,6 +25,8 @@
default, all incoming and outgoing traffic to the guest networks is blocked. To open the ports, default, all incoming and outgoing traffic to the guest networks 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 you must create a new network ACL. The network ACLs can be created for the tiers only if the
NetworkACL service is supported.</para> NetworkACL service is supported.</para>
<section id="acl-list">
<title>Creating ACL Lists</title>
<orderedlist> <orderedlist>
<listitem> <listitem>
<para>Log in to the &PRODUCT; UI as an administrator or end user.</para> <para>Log in to the &PRODUCT; UI as an administrator or end user.</para>
@ -37,8 +39,7 @@
<para>All the VPCs that you have created for the account is listed in the page.</para> <para>All the VPCs that you have created for the account is listed in the page.</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Click the Configure button of the VPC, for which you want to configure load balancing <para>Click the Configure button of the VPC.</para>
rules.</para>
<para>For each tier, the following options are displayed:</para> <para>For each tier, the following options are displayed:</para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
@ -90,33 +91,56 @@
</listitem> </listitem>
</itemizedlist> </itemizedlist>
</listitem> </listitem>
</orderedlist>
</section>
<section id="add-acl-rule">
<title>Creating an ACL Rule</title>
<orderedlist>
<listitem> <listitem>
<para>Select the ACL list.</para> <para>Log in to the &PRODUCT; UI as an administrator or end user.</para>
</listitem>
<listitem>
<para>In the left navigation, choose Network.</para>
</listitem>
<listitem>
<para>In the Select view, select VPC.</para>
<para>All the VPCs that you have created for the account is listed in the page.</para>
</listitem>
<listitem>
<para>Click the Configure button of the VPC.</para>
</listitem>
<listitem>
<para>Select Network ACL Lists.</para>
<para>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.</para>
</listitem>
<listitem>
<para>Select the desired ACL list.</para>
</listitem> </listitem>
<listitem> <listitem>
<para>Select the ACL List Rules tab.</para> <para>Select the ACL List Rules tab.</para>
<para>To add an ACL rule, fill in the following fields to specify what kind of network traffic <para>To add an ACL rule, fill in the following fields to specify what kind of network
is allowed in the VPC. </para> traffic is allowed in the VPC. </para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para><emphasis role="bold">CIDR</emphasis>: The CIDR acts as the Source CIDR for the <para><emphasis role="bold">CIDR</emphasis>: The CIDR acts as the Source CIDR for the
Ingress rules, and Destination CIDR for the Egress rules. To accept traffic only from or Ingress rules, and Destination CIDR for the Egress rules. To accept traffic only from
to the IP addresses within a particular address block, enter a CIDR or a comma-separated or to the IP addresses within a particular address block, enter a CIDR or a
list of CIDRs. The CIDR is the base IP address of the incoming traffic. For example, comma-separated list of CIDRs. The CIDR is the base IP address of the incoming
192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0.</para> traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0.</para>
</listitem> </listitem>
<listitem> <listitem>
<para><emphasis role="bold">Protocol</emphasis>: The networking protocol that sources use <para><emphasis role="bold">Protocol</emphasis>: The networking protocol that sources
to send traffic to the tier. The TCP and UDP protocols are typically used for data 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 exchange and end-user communications. The ICMP protocol is typically used to send
messages or network monitoring data. All supports all the traffic. Other option is error messages or network monitoring data. All supports all the traffic. Other option
Protocol Number.</para> is Protocol Number.</para>
</listitem> </listitem>
<listitem> <listitem>
<para><emphasis role="bold">Start Port</emphasis>, <emphasis role="bold">End <para><emphasis role="bold">Start Port</emphasis>, <emphasis role="bold">End
Port</emphasis> (TCP, UDP only): A range of listening ports that are the destination Port</emphasis> (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 for the incoming traffic. If you are opening a single port, use the same number in
fields.</para> both fields.</para>
</listitem> </listitem>
<listitem> <listitem>
<para><emphasis role="bold">Protocol Number</emphasis>: The protocol number associated <para><emphasis role="bold">Protocol Number</emphasis>: The protocol number associated
@ -141,3 +165,57 @@
</listitem> </listitem>
</orderedlist> </orderedlist>
</section> </section>
<section id="create-acl-tier">
<title>Assigning a Custom ACL List to a Tier</title>
<orderedlist>
<listitem>
<para>Create a VPC.</para>
</listitem>
<listitem>
<para>Create a custom ACL list.</para>
</listitem>
<listitem>
<para>Add ACL rules to the ACL list.</para>
</listitem>
<listitem>
<para>Create a tier in the VPC.</para>
<para>Select the desired ACL list while creating a tier.</para>
</listitem>
<listitem><para>Click OK.</para></listitem>
</orderedlist>
</section>
<section id="assign-acl-tier">
<title>Assigning a Custom ACL List to a Tier</title>
<orderedlist>
<listitem>
<para>Create a VPC.</para>
</listitem>
<listitem>
<para>Create a tier in the VPC.</para>
</listitem>
<listitem>
<para>Associate the tier with the default ACL rule.</para>
</listitem>
<listitem>
<para>Create a custom ACL list.</para>
</listitem>
<listitem>
<para>Add ACL rules to the ACL list.</para>
</listitem>
<listitem>
<para>Select the tier for which you want to assign the custom ACL.</para>
</listitem>
<listitem><para>Click the Replace ACL List icon.<inlinemediaobject>
<imageobject>
<imagedata fileref="./images/replace-acl-icon.png"/>
</imageobject>
<textobject>
<phrase>replace-acl-icon.png: button to replace an ACL list</phrase>
</textobject>
</inlinemediaobject></para>
<para>The Replace ACL List dialog is displayed.</para></listitem>
<listitem><para>Select the desired ACL list.</para></listitem>
<listitem><para>Click OK.</para></listitem>
</orderedlist>
</section>
</section>

Binary file not shown.

After

Width:  |  Height:  |  Size: 930 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.5 KiB