Open Stack

IMO, VPC means to have managed set of resources not just limited to
networks but also projects.
I feel its not about incrementally starting with AWS compatibility, But
doing it right with AWS compatibility into consideration.

Thanks,
-Ravi.


On Sun, Feb 16, 2014 at 8:47 AM, Harshad Nakil
<hnakil at contrailsystems.com>wrote:

> Comments Inline
>
> Regards
> -Harshad
>
>
> On Sat, Feb 15, 2014 at 11:39 PM, Allamaraju, Subbu <subbu at subbu.org>wrote:
>
>> Harshad,
>>
>> Curious to know if there is a broad interest in an AWS compatible API in
>> the community?
>
>
> We started looking at this as some our customers/partners were interested
> in get AWS API compatibility. We have this blueprint and code review
> pending for long time now. We will know based on this thread wether the
> community is interested. But I assumed that community was interested as the
> blueprint was approved and code review has no -1(s) for long time now.
>
>
>> To clarify, a clear incremental path from an AWS compatible API to an
>> OpenStack model is not clear.
>>
>
> In my mind AWS compatible API does not need new openstack model. As more
> discussion happen on JC's proposal and implementation becomes clear we will
> know how incremental is the path. But at high level there two major
> differences
> 1. New first class object will be introduced which effect all components
> 2. more than one project can be supported within VPC.
> But it does not change AWS API(s). So even in JC(s) model if you want AWS
> API then we will have to keep VPC to project mapping 1:1, since the API
> will not take both VPC ID and project ID.
>
>



> As more users want to migrate from AWS or IaaS providers who want compete
> with AWS should be interested in this compatibility.
>
> There also seems to be terminology issue here Whats is definition of "VPC"
> if we assume what AWS implements is "VPC"
> then what JC is proposing "VOS" or "VDC" (virtual openstack or virtual DC)
> as all or most of current openstack features are available to user in  this
> new Abstraction. I actually like this new abstraction.
>
>
>> Subbu
>>
>> On Feb 15, 2014, at 10:04 PM, Harshad Nakil <hnakil at contrailsystems.com>
>> wrote:
>>
>> >
>> > I agree with problem as defined by you and will require more
>> fundamental changes.
>> > Meanwhile many users will benefit from AWS VPC api compatibility.
>>
>>
>> _______________________________________________
>> 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
>
>


-- 
Ravi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140216/745d6d7d/attachment.html>