This is an automated email from the ASF dual-hosted git repository. dahn pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git
The following commit(s) were added to refs/heads/main by this push: new 2318561 Add docs for enabling security groups for a zone without security groups (#422) 2318561 is described below commit 2318561c947ab4e687d9680b5b94784cc56022f6 Author: Vishesh <vishes...@gmail.com> AuthorDate: Fri Sep 6 12:43:15 2024 +0530 Add docs for enabling security groups for a zone without security groups (#422) --- source/adminguide/networking/security_groups.rst | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/source/adminguide/networking/security_groups.rst b/source/adminguide/networking/security_groups.rst index 5211c24..6f14944 100644 --- a/source/adminguide/networking/security_groups.rst +++ b/source/adminguide/networking/security_groups.rst @@ -115,9 +115,12 @@ In order for security groups to function in a zone, the security groups feature must first be enabled for the zone. The administrator can do this when creating a new zone, by selecting a network offering that includes security groups. The procedure is described in Basic Zone -Configuration in the Advanced Installation Guide. The administrator can -not enable security groups for an existing zone, only when creating a -new zone. +Configuration in the Advanced Installation Guide. + +To enable security groups for an existing advanced zone which doesn't have +security groups enabled, the administrator can enable the +`SecurityGroupProvider` for the physical network of the zone. This will allow +user to create networks with Security Groups. Adding Ingress and Egress Rules to a Security Group