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

Docs. CLOUDSTACK-737. Documentation for security groups in advanced zones. In about-security-groups.xml, add 1 sentence: "In advanced zones, security groups are supported only on the KVM hypervisor." This replaces a sentence that states they are supported only in basic zones. New section: security-groups-advanced-zones.xml. In security-groups.xml: include the new section.

This commit is contained in:
Jessica Tomechak 2013-01-30 16:16:35 -08:00
parent 397b5b5829
commit 7dbbdd59c7
3 changed files with 60 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/en-US/about-security-groups.xml
View File

@ -24,7 +24,12 @@
<section id="about-security-groups">
<title>About Security Groups</title>
<para>Security groups provide a way to isolate traffic to VMs. A security group is a group of VMs that filter their incoming and outgoing traffic according to a set of rules, called ingress and egress rules. These rules filter network traffic according to the IP address that is attempting to communicate with the VM. Security groups are particularly useful in zones that use basic networking, because there is a single guest network for all guest VMs. In &PRODUCT; 3.0.3 - 3.0.5, security groups are supported only in zones that use basic networking.</para>
<para>Security groups provide a way to isolate traffic to VMs. A security group is a group of
VMs that filter their incoming and outgoing traffic according to a set of rules, called
ingress and egress rules. These rules filter network traffic according to the IP address
that is attempting to communicate with the VM. Security groups are particularly useful in
zones that use basic networking, because there is a single guest network for all guest VMs.
In advanced zones, security groups are supported only on the KVM hypervisor.</para>
<note><para>In a zone that uses advanced networking, you can instead define multiple guest networks to isolate traffic to VMs.</para>
</note>
<para></para>

52
docs/en-US/security-groups-advanced-zones.xml Normal file
View File

@ -0,0 +1,52 @@
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
%BOOK_ENTITIES;
]>
<!-- Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<section id="security-groups-advanced-zones">
<title>Security Groups in Advanced Zones (KVM Only)</title>
<para>&PRODUCT; provides the ability to use security groups to provide isolation between
guests on a single shared, zone-wide network in an advanced zone where KVM is the
hypervisor. Using security groups in advanced zones rather than multiple VLANs allows a greater range
of options for setting up guest isolation in a cloud.</para>
<formalpara>
<title>Limitations</title>
<para>The following are not supported for this feature:</para>
</formalpara>
<itemizedlist>
<listitem>
<para>Two IP ranges with the same VLAN and different gateway or netmask in security
group-enabled shared network.</para>
</listitem>
<listitem>
<para>Two IP ranges with the same VLAN and different gateway or netmask in
account-specific shared networks.</para>
</listitem>
<listitem>
<para>Multiple VLAN ranges in security group-enabled shared network.</para>
</listitem>
<listitem>
<para>Multiple VLAN ranges in account-specific shared networks.</para>
</listitem>
</itemizedlist>
<para>Security groups must be enabled in the zone in order for this feature to be used.</para>
</section>

3
docs/en-US/security-groups.xml
View File

@ -25,7 +25,8 @@
<section id="security-groups">
<title>Security Groups</title>
<xi:include href="about-security-groups.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="add-security-group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="security-groups-advanced-zones.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="enable-security-groups.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="add-security-group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="add-ingress-egress-rules.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
</section>