On 15/08/2016, 19:29, "Matt Riedemann" <[email protected]> wrote:
>On 8/15/2016 4:24 AM, Afek, Ifat (Nokia - IL) wrote:
>> Hi,
>>
>> In Vitrage project[1], I would like to add an option to call nova
>> host-evacuate for a failed host. I noticed that there is an api for ‘nova
>> evacuate’, and a cli (but no api) for ‘nova host-evacuate’. Is there a way
>> that I can call 'nova host-evacuate’ from Vitrage code? Did you consider
>> adding host-evacuate to nova api? Obviously it would improve the performance
>> for Vitrage use case.
>>
>>
>> Some more details: The Vitrage project is used for analysing the root cause
>> of OpenStack alarms, and deducing their existence before they are directly
>> observed. It receives information from various data sources (Nova, Neutron,
>> Zabbix, etc.) performs configurable actions and notifies other projects like
>> Nova.
>>
>> For example, in case zabbix detect a host NIC failure, Vitrage calls nova
>> force-down api to indicate that the host is unavailable. We would like to
>> add an option to evacuate the failed host.
>>
>> Thanks,
>>
>> Ifat.
>>
>> [1] https://wiki.openstack.org/wiki/Vitrage
>>
>>
>
>This blog post will probably be helpful:
>
>http://www.danplanet.com/blog/2016/03/03/evacuate-in-nova-one-command-to-confuse-us-all/
>
>The 'nova host-evacuate' CLI is a convenience CLI, it's not for a
>specific API, it just takes a host, finds the instances running on that
>host and evacuates each of them. You could do something similar in vitrage.
>
>--
>
>Thanks,
>
>Matt Riedemann
>
Thanks Matt,
I already read this blog :-)
I asked about moving the cli code to the api, because performance-wise it would
help us.
Thanks,
Ifat.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev