Joe, I will let others comment, but since I think this BP was proposed much before the multi-tenant hierarchy BP, I would like to at least have the discussion. I would suggest a pause until we agree that this is ok to move this forward independently of the multi tenant hierarchy proposal.
JC On Feb 14, 2014, at 11:42 AM, Joe Gordon <[email protected]> wrote: > On Fri, Feb 14, 2014 at 12:09 PM, Martin, JC <[email protected]> wrote: >> >> 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. > > Nova doesn't support keystone V3 domains or the proposed multi tenant > hierarchy (proposed after this BP) yet. Do you think this BP should be > blocked with those two as dependencies? > >> >> 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 >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
