Re: [openstack-dev] [mistral][osc-lib][openstackclient] is it too early for orc-lib?

2016-07-11 Thread Dean Troyer
On Mon, Jul 11, 2016 at 9:24 AM, Dmitry Tantsur wrote: > It seems like OSC now issues warnings if we use bits that are moved to > osc-lib. Does it mean that now osc-lib is ready for all projects to switch > to? If not, could you please revert the warnings? It's a bit

Re: [openstack-dev] [mistral][osc-lib][openstackclient] is it too early for orc-lib?

2016-07-11 Thread Dmitry Tantsur
On 06/30/2016 11:29 PM, Dean Troyer wrote: On Thu, Jun 30, 2016 at 8:38 AM, Hardik > wrote: Regarding osc-lib we have mainly two changes. 1) Used "utils" which is moved from openstackclient.common.utils to

Re: [openstack-dev] [mistral][osc-lib][openstackclient] is it too early for orc-lib?

2016-07-04 Thread Renat Akhmerov
Ok, based on what has been said here I suggest we keep this code for now. The changes were really minimal. If it creates some problems for us we can always easily revert. Renat Akhmerov @Nokia > On 01 Jul 2016, at 04:57, Steve Martinelli wrote: > > The crux of this,

Re: [openstack-dev] [mistral][osc-lib][openstackclient] is it too early for orc-lib?

2016-06-30 Thread Steve Martinelli
The crux of this, as Dean stated, is if the library wants OSC to always be pulled in (along with its many dependencies). We've seen folks include it in requirements, test-requirements, or even not at all (just document that OSC needs to be installed). I tossed up the idea with the ironic team of

Re: [openstack-dev] [mistral][osc-lib][openstackclient] is it too early for orc-lib?

2016-06-30 Thread Dean Troyer
On Thu, Jun 30, 2016 at 8:38 AM, Hardik wrote: > Regarding osc-lib we have mainly two changes. > > 1) Used "utils" which is moved from openstackclient.common.utils to > osc_lib.utils > 2) We used "command" which wrapped in osc_lib from cliff. > > So I think

Re: [openstack-dev] [mistral][osc-lib][openstackclient] is it too early for orc-lib?

2016-06-30 Thread Hardik
Hi, Regarding osc-lib we have mainly two changes. 1) Used "utils" which is moved from openstackclient.common.utils to osc_lib.utils 2) We used "command" which wrapped in osc_lib from cliff. So I think there is no harm in keeping osc_lib. Also, I guess we do not need openstackclient to be

[openstack-dev] [mistral][osc-lib][openstackclient] is it too early for orc-lib?

2016-06-30 Thread Renat Akhmerov
Hi, We already let osc-lib in to Mistral but I found out that such transition was blocked in TripleO, [1]. I’d like to ask the team to read into it and discuss whether we need to revert corresponding patches in Mistral or not. [1] https://review.openstack.org/#/c/11/