On Sun, Feb 16, 2014 at 3:26 AM, Salvatore Orlando wrote:
> It seems this work item is made of several blueprints, some of which are not
> yet approved. This is true at least for the Neutron blueprint regarding
> policy extensions.
>
> Since I first looked at this spec I've been wondering why nova
I agree with JC that we need to pause and discuss VPC model with in
openstack before considering AWS compatibility. As Subbu said, We need this
discussion in Juno summit and get consensus.
Thanks,
-Ravi.
On Sun, Feb 16, 2014 at 10:31 AM, Allamaraju, Subbu wrote:
> Harshad,
>
> This is great. A
Harshad,
This is great. At least there is consensus on what it is and what it is not. I
would leave it to others to discuss merits of a an AWS compat VPC API for
Icehouse.
Perhaps this is a good topic to discuss at the Juno design summit.
Subbu
On Feb 16, 2014, at 10:15 AM, Harshad Nakil wro
As said I am not disagreeing with you or Ravi or JC. I also agree that
Openstack VPC implementation will benefit from these proposals.
What I am saying is it is not required AWS VPC API compatibility at
this point. Which is what our blueprint is all about. We are not
defining THE "VPC".
Let me ask
Harshad,
But the key question that Ravi brought up remains though. A project is a very
small administrative container to manage policies and resources for VPCs. We've
been experimenting with VPCs on OpenStack (with some mods) at work for nearly a
year, and came across cases where hundreds/thous
Yes, [1] can be done without [2] and [3].
As you are well aware [2] is now merged with group policy discussions.
IMHO all or nothing approach will not get us anywhere.
By the time we line up all our ducks in row. New features/ideas/blueprints
will keep Emerging.
Regards
-Harshad
On Feb 16, 2014,
It seems this work item is made of several blueprints, some of which are
not yet approved. This is true at least for the Neutron blueprint regarding
policy extensions.
Since I first looked at this spec I've been wondering why nova has been
selected as an endpoint for network operations rather than
Ravi,
It seems that the following Blueprint
https://wiki.openstack.org/wiki/Blueprint-aws-vpc-support
has been approved.
However, I cannot find a discussion with regard to the merit of using project
vs. domain, or other mechanism for the implementation.
I have an issue with this approach as
Hi,
We had some internal discussions on role of Domain and VPCs. I would like
to expand and understand community thinking of Keystone domain and VPCs.
Is VPC equivalent to Keystone Domain?
If so, as a public cloud provider - I create a Keystone domain and give it
to an organization which wants
