You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by ch...@apache.org on 2012/10/22 17:20:29 UTC
[47/49] git commit: Docs: Add missing file on security groups.
Docs: Add missing file on security groups.
Project: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/commit/98e74d3f
Tree: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/98e74d3f
Diff: http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/98e74d3f
Branch: refs/heads/4.0
Commit: 98e74d3f4caef91f0c7a6f71a733e02d067969da
Parents: 6a4dc6a
Author: Jessica Tomechak <je...@gmail.com>
Authored: Tue Oct 16 17:57:03 2012 -0700
Committer: Chip Childers <ch...@gmail.com>
Committed: Mon Oct 22 10:49:13 2012 -0400
----------------------------------------------------------------------
docs/en-US/about-security-groups.xml | 35 +++++++++++++++++++++
docs/en-US/cloud-infrastructure-concepts.xml | 3 +-
docs/en-US/security-groups.xml | 1 +
3 files changed, 38 insertions(+), 1 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/98e74d3f/docs/en-US/about-security-groups.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/about-security-groups.xml b/docs/en-US/about-security-groups.xml
new file mode 100644
index 0000000..85e8477
--- /dev/null
+++ b/docs/en-US/about-security-groups.xml
@@ -0,0 +1,35 @@
+<?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="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>
+ <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>
+ <para>Each &PRODUCT; account comes with a default security group that denies all inbound traffic and allows all outbound traffic. The default security group can be modified so that all new VMs inherit some other desired set of rules.</para>
+ <para>Any &PRODUCT; user can set up any number of additional security groups. When a new VM is launched, it is assigned to the default security group unless another user-defined security group is specified. A VM can be a member of any number of security groups. Once a VM is assigned to a security group, it remains in that group for its entire lifetime; you can not move a running VM from one security group to another.</para>
+ <para>You can modify a security group by deleting or adding any number of ingress and egress rules. When you do, the new rules apply to all VMs in the group, whether running or stopped.</para>
+ <para>If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule.</para>
+</section>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/98e74d3f/docs/en-US/cloud-infrastructure-concepts.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/cloud-infrastructure-concepts.xml b/docs/en-US/cloud-infrastructure-concepts.xml
index 7fc9efa..5ab39ec 100644
--- a/docs/en-US/cloud-infrastructure-concepts.xml
+++ b/docs/en-US/cloud-infrastructure-concepts.xml
@@ -31,4 +31,5 @@
<xi:include href="about-primary-storage.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="about-secondary-storage.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="about-physical-networks.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-</chapter>
\ No newline at end of file
+ <xi:include href="security-groups.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+</chapter>
http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/98e74d3f/docs/en-US/security-groups.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/security-groups.xml b/docs/en-US/security-groups.xml
index 55f2a72..3c08965 100644
--- a/docs/en-US/security-groups.xml
+++ b/docs/en-US/security-groups.xml
@@ -24,6 +24,7 @@
<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="enable-security-groups.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" />