Page History

...

• Add check box "Enable Security Group" to the first page of create Zone dialog. If Security Group selected, pass
  securitygroupenabled=true to the addZone api call.
• When create physical network(s) on the next page, show L3(security groups) isolation option as a choice only when "Enable SecurityGroup" was checked when create the zone. And show it only for one of the physical networks as we allow to have only one Shared SG enabled network in the zone at this point.
• Add an ability to select multiple Isolation methods at the same time (Vlan, L3, GRE). Pass it as a coma separated list to createPhysicalNetwork call (API already supports it)
• Like in Basic zone, we should force admin to create Guest Network as a part of zone creation. With the only one difference 2 differences - Vlan field is required; and network offering should be SG enabled.
• No Public traffic type support when add SG Advance zone
• Allow having multiple physical networks though.
• When add first cluster/host, show KVM as the only one available hypervisor.

...

• Only allow adding KVM cluster to Advance SG enabled zone

Infrastructure -> PhysicalNetworks Diagram -> Modify Guest traffic type->AddNetwork

• Only allow adding Shared Account specific network networks (SG disabled) when the zone is Advance SG enabled
• If there are no Shared Zone wide SG enabled network in the zone (user created the zone using API and didn't add the network yet); allow to add SG enabled Zone wide shared network.

Networks tab

• Add SecurityGroup to the list of Views (drop box) on the top of the view. Show it only when 1) there is at least 1 Basic zone in the cloudStack 2) There is at least one Advance zone that is SG enabled (execute listZones&securitygroupenabled=true)

...

• Get all the networks available to the User with a simple listNetworks&account=&domainId&type=Shared API call
• Don't allow user to select combination of SG enabled and disabled network
• When SG enabled network is selected, show Security Group list to select from

...