Re: [openstack-dev] [Sahara] Question about Sahara API v2
Sergey and Michael, thanks for explaining these. -Ken From: Sergey Lukjanov [mailto:slukja...@mirantis.com] Sent: Tuesday, March 31, 2015 12:00 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Sahara] Question about Sahara API v2 Agree with Mike, thx for the link. On Mon, Mar 30, 2015 at 4:55 PM, michael mccune m...@redhat.commailto:m...@redhat.com wrote: On 03/30/2015 07:02 AM, Sergey Lukjanov wrote: 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 * hrefs 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. +1 i've started a pad that we can use to collect ideas for the discussion: https://etherpad.openstack.org/p/sahara-liberty-api-v2 things that i'd like to see from the v2 discussion * a full endpoint review, some of the endpoints might need to be deprecated or adjusted slightly (for example, job-binary-internals) * a technology review, should we consider Pecan or stay with Flask? * proposals for more radical changes to the api; use of micro-versions akin to nova's plan, migrating the project id into the headers, possible use of swagger to aid in auto-generation of api definitions. i think we will have a good amount to discuss and i will be migrating some of my local notes into the pad over this week and the next. i invite everyone to add their thoughts to the pad for ideas. mike __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack Data Processing) Principal Software Engineer Mirantis Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Sahara] Question about Sahara API v2
On 03/30/2015 07:02 AM, Sergey Lukjanov wrote: 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 * hrefs 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. +1 i've started a pad that we can use to collect ideas for the discussion: https://etherpad.openstack.org/p/sahara-liberty-api-v2 things that i'd like to see from the v2 discussion * a full endpoint review, some of the endpoints might need to be deprecated or adjusted slightly (for example, job-binary-internals) * a technology review, should we consider Pecan or stay with Flask? * proposals for more radical changes to the api; use of micro-versions akin to nova's plan, migrating the project id into the headers, possible use of swagger to aid in auto-generation of api definitions. i think we will have a good amount to discuss and i will be migrating some of my local notes into the pad over this week and the next. i invite everyone to add their thoughts to the pad for ideas. mike __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Sahara] Question about Sahara API v2
Hi, 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 * hrefs 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. Thanks. On Mon, Mar 30, 2015 at 5:34 AM, Chen, Ken ken.c...@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. -Ken __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack Data Processing) Principal Software Engineer Mirantis Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Sahara] Question about Sahara API v2
Agree with Mike, thx for the link. On Mon, Mar 30, 2015 at 4:55 PM, michael mccune m...@redhat.com wrote: On 03/30/2015 07:02 AM, Sergey Lukjanov wrote: 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 * hrefs 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. +1 i've started a pad that we can use to collect ideas for the discussion: https://etherpad.openstack.org/p/sahara-liberty-api-v2 things that i'd like to see from the v2 discussion * a full endpoint review, some of the endpoints might need to be deprecated or adjusted slightly (for example, job-binary-internals) * a technology review, should we consider Pecan or stay with Flask? * proposals for more radical changes to the api; use of micro-versions akin to nova's plan, migrating the project id into the headers, possible use of swagger to aid in auto-generation of api definitions. i think we will have a good amount to discuss and i will be migrating some of my local notes into the pad over this week and the next. i invite everyone to add their thoughts to the pad for ideas. mike __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack Data Processing) Principal Software Engineer Mirantis Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Sahara] Question about Sahara API v2
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. -Ken __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
