Open Stack

Hi All, 

Totally agree with Allamaraju. Only hierarchical administrative boundary is not enough, the definition of internal network architecture within one domain is very important. The networking among projects in one domain could be isolated or not, the access to external network may be not only controlled at domain level, but also at project level. Allamaraju's proposal can solve these issues well.

My question is how to solve multi-region scenario?  May the VPC cross multiple OpenStack instances?

The role for different resources visibility is also need to be defined for the VPC solution.

Best Regards
Chaoyi Huang( Joe Huang)


-----邮件原件-----
发件人: Allamaraju, Subbu [mailto:subbu at subbu.org] 
发送时间: 2014年5月13日 20:55
收件人: OpenStack Development Mailing List (not for usage questions)
主题: Re: [openstack-dev] Hierarchical administrative boundary [keystone]

Hi Arvind,

This seems to be covering one of the use cases listed by https://wiki.openstack.org/wiki/Blueprint-VPC. Others to isolate between VPCs include shared resources like networks, images, roles, and other configuration. 

Subbu

On May 8, 2014, at 7:55 PM, Tiwari, Arvind <arvind.tiwari at hp.com> wrote:

> Hi All,
>  
> Below is my proposal to address VPC use case using hierarchical administrative boundary. This topic is scheduled in Hierarchical Multitenancysession of Atlanta design summit.
>  
> https://wiki.openstack.org/wiki/Hierarchical_administrative_boundary
>  
> Please take a look.
>  
> Thanks,
> Arvind
>  
> _______________________________________________
> 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