[openstack-dev] [Murano] python-openstackclient support

Kirill Zaitsev kzaitsev at mirantis.com
Tue Jun 9 14:35:56 UTC 2015


Since it includes a certain research phase (on how to integrate properly) I’d bet on half-a-week to week of work. 
But that’s just a wild guess. Might be less, might be more.

-- 
Kirill Zaitsev
Murano team
Software Engineer
Mirantis, Inc

On 9 Jun 2015 at 14:59:13, Ekaterina Chernova (efedorova at mirantis.com) wrote:

Hi all!

I support the idea!

Kirill, how much time do you think blueprint implementation will take?

On Tue, Jun 9, 2015 at 2:46 PM, Kirill Zaitsev <kzaitsev at mirantis.com> wrote:
https://blueprints.launchpad.net/python-muranoclient/+spec/openstack-client-plugin-support

I’ve done that a while ago, already =). 

Could you please approve it?

-- 
Kirill Zaitsev
Murano team
Software Engineer
Mirantis, Inc

On 9 Jun 2015 at 11:45:56, Serg Melikyan (smelikyan at mirantis.com) wrote:

Hi Kirill,

It's definitely a great idea, it needs to be verified though AFAIK all
openstack projects are moving to support python-openstackclient. I
think we should file a blueprint around that and start looking at that
on background. I think it will be not a big deal to support
python-openstackclient.

On Thu, Apr 23, 2015 at 3:04 AM, Stan Lagun <slagun at mirantis.com> wrote:
>
> +1 for the idea though not sure on priority of this since we have so many way more important things to implement in Kilo. I'd say that would be a great contribution if we find someone willing to contribute it :)
>
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
>
> On Thu, Apr 23, 2015 at 1:55 AM, Kirill Zaitsev <kzaitsev at mirantis.com> wrote:
>>
>> Since python-openstackclient is now a part of openstack — I guess it would be a good idea to support it in murano. It has setuptools-based plugin system, and it should be fairly easy to add murano commands as plugins to it.
>> BTW, It’s based on cliff and has a terrific completion support (which is basically why I started looking into the issue in the first place =))
>>
>> What do you think, is it a good idea?
>>
>> --
>> Kirill Zaitsev
>> Sent with Airmail
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



--
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelikyan at mirantis.com

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__________________________________________________________________________  
OpenStack Development Mailing List (not for usage questions)  
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe  
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150609/4a48d6a1/attachment.html>


More information about the OpenStack-dev mailing list