Open Stack

Hi Eric,

(1) "virtual machine" is bug. This need to be corrected as physical machine
or hypervisor.
      Masakari host is a physical host/hypervisor. I will correct this.

(2) Not through masakari APIs. You have to add metadata key
'HA_Enabled=True' to each VM by using nova API.
     Masakeri monitors check for failures and send notification to masakari
API if detected any failure (i.e host, VM or process failures).
     In host failure (hypervisor down) scenario, Masakari engine get the VM
list on that hypervisor and start evacuate VMs.
     Operator can configure masakari to evacuate all VMs or only the VMs
with the metadata key   'HA_Enabled=True.
     Please see the config file [1] section [host_failure] for more details.

Let me know if you need more info on this.

[1] https://docs.openstack.org/masakari/latest/sample_config.html

--- Regards,
Sampath



On Sun, Oct 7, 2018 at 8:55 AM Eric K <ekcs.openstack at gmail.com> wrote:

> Hi all, I'm working on a potential integration between masakari and
> congress. But I am stuck on some basic usage questions I could not
> answer in my search of docs and demos. Any clarification or references
> would be much appreciated!
>
> 1. What does a host refer to in masakari API? Here's the explanation in
> API doc:
> "Host can be any kind of virtual machine which can have compute
> service running on it."
> (https://developer.openstack.org/api-ref/instance-ha/#hosts-hosts)
>
> So is a masakari host usually a nova instance/server instead of a
> host/hypervisor?
>
> 2. Through the masakari api, how does one go about configuring a VM to
> be managed by masakari instance HA?
>
> Thanks so much!
>
> Eric Kao
>
> __________________________________________________________________________
> 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/20181007/188bded7/attachment.html>