[openstack-dev] [Sahara] Question about Sahara API v2
slukjanov at mirantis.com
Mon Mar 30 11:02:14 UTC 2015
in a few words - we're finding out some places that were designed not very
well (or our vision changed) and so we'd like to update the API to have a
much better interface to work with Sahara. The blueprint you've listed was
created in Atlanta summit timeframe and so it's not actual now.
My personal opinion for API 2.0 - we should discuss design of all object
and endpoint, review how they are used from Horizon or python-saharaclient
and improve them as much as possible. For example, it includes:
* get rid of tons of extra optional fields
* rename Job -> Job Template, Job Execution -> Job
* better support for Horizon needs
If you have any ideas ideas about 2.0 - please write them up, there is a
99% chance that we'll discuss an API 2.0 a lot on Vancouver summit.
On Mon, Mar 30, 2015 at 5:34 AM, Chen, Ken <ken.chen at intel.com> wrote:
> Hi all,
> Recently I have read some contents about Sahara API v2 propose, but I am
> still a bit confused why we are doing so at this stage. I read the bp
> https://blueprints.launchpad.net/sahara/+spec/v2-api-impl and the
> involved gerrit reviews (although already abandoned). However, I did not
> find anything new than current v1+v1.1 APIs. So why do we want v2 API? Just
> to combine v1 and v1.1 APIs? Is there any deeper requirement or background
> needs us to do so? Please let me know that if yes.
> Btw, I also see some comments that we may want to introduce PECAN to
> implement Sahara APIs. Will that be soon in Liberty, or not decided yet?
> Thanks a lot.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
Sahara Technical Lead
(OpenStack Data Processing)
Principal Software Engineer
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev