Page History

...

The last ip address of the VPC level super-cidr will be used as the loopback id of the ospf enabled VPC-VR. 

Some of the operators may want their users to have public IP assigned to their VPC-VMs. To facilitate that management server will allow both private and public class super-cidrs to be specified for the zone. There will be provision to add more super-CIDRs of private public kind at later stages.

Routed VPC Network Offering

There will be two default service offerings that will be created for dynamically routed VPCs one corresponding to public class ips and another corresponding to private class ips. These will be "DefaultPublicRoutedVPCNetworkOffering" and "DefaultPrivateRoutedVPCNetworkOffering" respectively. Depending on what offering a user chooses cloudstack will assign ips from the respective range to user's VPC or flag an error if no ips of that particular class exists.

These offerings A new default service offering "DefaultRoutedVPCNetworkOffering" for routed networks will be added in the management server. This will show up with other default network offerings. When a Routed VPC is created it will spin of the VPC-VR with pre-configured ranges and quagga service running on it. This will require that the system vm template have quagga installed on them.

...

Quagga will be pre-installed on the VPC-VR template and will be activated and configured if DefaultRoutedVPCNetworkOffering network Default<Private/Public>RoutedVPCNetworkOffering network offering is used.  (Using cloud-early-config.sh).  Quagga will advertise the VPC routing table across to other VPC routers. 

...

The user while creating a VPC can select the DefaultRoutedVPCNetworkOffering the Default<Private/Public>RoutedVPCNetworkOffering that will enforce the Super IPv4 CIDR to be in the Super IPv4 CIDR of the zone. If the user does not provide any value then the cloudstack will automatically pick a /24 CIDR as the super CIDR for this VPC. An appropriate error will be given if the zone has exhausted all /24 CIDRs.

...