IMHO I don't see two implementations. Since right now we have only one. As a community if we decide to add new abstractions then we will have to change software in every component where the new abstraction makes difference. That's normal software development process. Regards -Harshad
> On Feb 16, 2014, at 9:03 AM, "Allamaraju, Subbu" <su...@subbu.org> wrote: > > Harshad, > > Thanks for clarifying. > >> 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. > > Makes sense. I would leave it to others on this list to chime in if there is > sufficient interest or not. > >> 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. > > IMHO that's a tough sell. Though an AWS compatible API does not need an > OpenStack abstraction, we would end up with two independent ways of doing > similar things. That would OpenStack repeating itself! > > Subbu > > _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
