[openstack-dev] VPC Proposal

Allamaraju, Subbu subbu at subbu.org
Sun Feb 16 07:25:09 UTC 2014


True. The domain hierarchy isn't useful to capture resource sharing across a VPC. For instance, if a VPC admin would like to scope certain networks or images to a projects managed within a VPC, there isn't an abstraction today.

Subbu

On Feb 14, 2014, at 11:42 AM, Martin, JC <jch.martin at gmail.com> wrote:

> Arvind,
> 
> Thanks for point me to the blueprint. I'll add it to the related blueprints.
> 
> I think this could be part of the solution, but in addition to defining administrative boundaries, we need to change the way object sharing works. Today, there is only two levels : project private or public. You can share objects between projects but there is no single model across openstack to define resource scope, each component has a slightly different model. The VPC implementation will also have to address that.
> 
> JC
> 
> On Feb 14, 2014, at 11:26 AM, "Tiwari, Arvind" <arvind.tiwari at hp.com> wrote:
> 
>> Hi JC,
>> 
>> I have proposed BP to address VPC using domain hierarchy and hierarchical administrative boundary.
>> 
>> https://blueprints.launchpad.net/keystone/+spec/hierarchical-administrative-boundary
>> 
>> 
>> Thanks,
>> Arvind
>> -----Original Message-----
>> From: Martin, JC [mailto:jch.martin at gmail.com] 
>> Sent: Friday, February 14, 2014 12:09 PM
>> To: OpenStack Development Mailing List
>> Subject: [openstack-dev] VPC Proposal
>> 
>> 
>> There is a Blueprint targeted for Icehouse-3 that is aiming to implement the AWS VPC api. I don't think that this blueprint is providing the necessary constructs to really implement a VPC, and it is not taking into account the domains, or proposed multi tenant hierarchy. In addition, I could not find a discussion about this topic leading to the approval.
>> 
>> For this reason, I wrote an 'umbrella' blueprint to hopefully start the discussion on how to really implement VPC, and eventually split it into multiple real blueprints for each area.
>> 
>> Please, provide feedback on the following document, and on the best way to move this forward.
>> 
>> https://wiki.openstack.org/wiki/Blueprint-VPC
>> 
>> Thanks,
>> 
>> JC.
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> 
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




More information about the OpenStack-dev mailing list