From a35e23c58fe93feaf4b5b68532934e8d1a8ca37d Mon Sep 17 00:00:00 2001 From: Jessica Tomechak Date: Tue, 16 Oct 2012 17:57:03 -0700 Subject: [PATCH] Docs: Add missing file on security groups. --- 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 deletion(-) create mode 100644 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 00000000000..85e8477cfb1 --- /dev/null +++ b/docs/en-US/about-security-groups.xml @@ -0,0 +1,35 @@ + + +%BOOK_ENTITIES; +]> + + + +
+ About Security Groups + 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. + In a zone that uses advanced networking, you can instead define multiple guest networks to isolate traffic to VMs. + + + 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. + 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. + 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. + 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. +
diff --git a/docs/en-US/cloud-infrastructure-concepts.xml b/docs/en-US/cloud-infrastructure-concepts.xml index 7fc9efa3b3d..5ab39ec6ba8 100644 --- a/docs/en-US/cloud-infrastructure-concepts.xml +++ b/docs/en-US/cloud-infrastructure-concepts.xml @@ -31,4 +31,5 @@ - \ No newline at end of file + + diff --git a/docs/en-US/security-groups.xml b/docs/en-US/security-groups.xml index 55f2a72d4c3..3c08965c8d3 100644 --- a/docs/en-US/security-groups.xml +++ b/docs/en-US/security-groups.xml @@ -24,6 +24,7 @@
Security Groups +