Many public cloud providers allow you to utilize Virtual Private Clouds (VPC). In this context a VPC is a logically isolated virtual network dedicated to a private cloud account.
While there is currently no 1:1 comparison in OpenStack a simplified version would be as follows.
|VPC Features||OpenStack Features|
|Elastic IP||Floating IP|
|Network ACLs||Network ACLs|
|Security groups||Security groups|
|Route Table||Route Table|
The OpenStack community has a blueprint in place with the goal of creating additional parity with the VPC concept which can be reviewed on the OpenStack Wiki
In future articles we will be delving deeper into OpenStack private cloud resource isolation, and it's relation to public cloud VPCs.
VPC using OpenStack
Projects in OpenStack separate your cloud infrastructure from other workloads. If you have multiple DevOps teams with varying workloads and use cases each team can be provided a project tailored to their resource requirements.
In this context users are any entity requiring access to resources. This may be administrators, regular users or automated tasks and actions requiring varying levels of access to cloud infrastructure. In combination with projects and quotas you are provided with fine-grained control of who and what can access resources while maintaining accountability with comprehensive logging.
Refer to the OpenStack documentation for additional information regarding Managing Projects and Users.
Quotas are operational limits you can use to prevent system capacity exhaustion without notification. Quotas are currently enforced at the project, rather than user, level and are broken down to Image, Compute, and Storage (Object and Block).
The table below (extracted from the OpenStack documentation) summarizes available options for the most commonly implemented limits, Compute Service quotas.
|Fixed IPs||Number of fixed IP addresses allowed per project. This number must be equal to or greater than the number of allowed instances.|
|Floating IPs||Number of floating IP addresses allowed per project.|
|Injected file content bytes||Number of content bytes allowed per injected file.|
|Injected file path bytes||Number of bytes allowed per injected file path.|
|Injected files||Number of injected files allowed per project.|
|Instances||Number of instances allowed per project.|
|Key pairs||Number of key pairs allowed per user.|
|Metadata items||Number of metadata items allowed per instance.|
|RAM||Megabytes of instance RAM allowed per project.|
|Security group rules||Number of security group rules per project.|
|Security groups||Number of security groups per project.|
|VCPUs||Number of instance cores allowed per project.|
|Server Groups||Number of server groups per project.|
|Server Group Members||Number of servers per server group.|
See the upstream documentation for additional information on quota management.
In OpenStack a project provides logical isolation of all resources generated within. Users and roles can be used to provide fine-grained access to specific resources within a project for further isolation. As projects can span resources across all accessible availability zones they provide the core isolation inherent in the virtual private cloud concept.