[openstack-dev] [nova][cinder] how to handle AZ bug 1496235?

Sylvain Bauza sbauza at redhat.com
Thu Sep 24 17:55:29 UTC 2015



Le 24/09/2015 18:16, Mathieu Gagné a écrit :
> On 2015-09-24 11:53 AM, Walter A. Boring IV wrote:
>> The good thing about the Nova and Cinder clients/APIs is that
>> anyone can write a quick python script to do the orchestration
>> themselves, if we want to deprecate this.  I'm all for deprecating this.
> I don't like this kind of reasoning which can justify close to anything.
> It's easy to make those suggestions when you know Python. Please
> consider non-technical/non-developers users when suggesting deprecating
> features or proposing alternative solutions.
>
> I could also say (in bad faith, I know): why have Heat when you can
> write your own Python script. And yet, I don't think we would appreciate
> anyone making such a controversial statement.
>
> Our users don't know Python, use 3rd party tools (which don't often
> perform/support orchestration) or the Horizon dashboard. They don't want
> to have to learn Heat or Python so they can orchestrate volume creation
> in place of Nova for a single instance. You don't write CloudFormation
> templates on AWS just to boot an instance on volume. That's not the UX I
> want to offer to my users.
>

I'd tend to answer that if it's an user problem, then I would prefer to 
see the orchestration done by a python-novaclient wrapping CLI module 
like we have for host-evacuate (for example) and deprecate the REST and 
novaclient APIs so it would still be possible for the users to get the 
orchestration done by the same CLI but the API no longer supporting that.

-Sylvain




More information about the OpenStack-dev mailing list