Page History

...

• SG is zone-level flag, if a zone is SG enabled, all networks inside this zone must be SG enabled., if zone is SG disabled, all networks inside this zone must be SG disabled.
• All types of shared networks are supported in SG enabled advanced zone, including zone-wide shared network, account-specific shared network, domain-wide shared network.
• Isolated networks cannot be added to advanced SG enabled zone.
• VPC cannot be added to advanced SG enabled zone
• There can be multiple SG enabled shared network in one advanced SG enabled zone
• User VM can be deployed on multiple SG enabled networks.
• SG is on VM level(not NIC level), if a VM has multiple NICs, SG rule applies to all NICs.
• SG can cross multiple networks, VMs on different networks can be in one SG.
• only one SG enabled network.
• Only one network service provider is supported in advanced SG enabled zone - Virtual Router
• external device like F5, SRX cannot be added to advanced SG enabled zone.
• support KVM  and XenServer hypervisor.
• Don't support Vmware, OVM, etc. hypervisor
• SG functionality is as same as in Basic zone in terms of Ingress/Egress rules behavior

...

Deploy VM flow

• User can choose multiple networksUser can choose multiple SGone network

Upgrade flow

• When create physical network traffic types, don't create Public traffic type.
• The rest of the upgrade should be handled the same way we handle it for other zones

...

In the future releases we are going to:

• VM can be on multiple SG enabled networks
• Add support for SG in Isolated networks
• Feature support in VPC networks