On 08/25/2015 08:04 AM, Matt Riedemann wrote:
On 8/24/2015 9:32 PM, Gary Kotton wrote:
In item #2 below the reboot is down via the guest and not the nova api’s :)
From: Gary Kotton <[email protected] <mailto:[email protected]>>
Reply-To: OpenStack List <[email protected]
<mailto:[email protected]>>
Date: Monday, August 24, 2015 at 7:18 PM
To: OpenStack List <[email protected]
<mailto:[email protected]>>
Subject: [openstack-dev] [nova] periodic task
Hi,
A couple of months ago I posted a patch for bug
https://launchpad.net/bugs/1463688. The issue is as follows: the
periodic task detects that the instance state does not match the state
on the hypervisor and it shuts down the running VM. There are a number
of ways that this may happen and I will try and explain:
1. Vmware driver example: a host where the instances are running goes
down. This could be a power outage, host failure, etc. The first
iteration of the perdioc task will determine that the actual
instacne is down. This will update the state of the instance to
DOWN. The VC has the ability to do HA and it will start the instance
up and running again. The next iteration of the periodic task will
determine that the instance is up and the compute manager will stop
the instance.
2. All drivers. The tenant decides to do a reboot of the instance and
that coincides with the periodic task state validation. At this
point in time the instance will not be up and the compute node will
update the state of the instance as DWON. Next iteration the states
will differ and the instance will be shutdown
In #2 the guest shouldn't be rebooted by the user (tenant) outside of the
nova-api. I'm not sure if it's actually formally documented in the nova
documentation, but from what I've always heard/known, nova is the control plane
and you should be doing everything with your instances via the nova-api. If the
user rebooted via nova-api, the task_state would be set and the periodic task
would ignore the instance.
If we're talking about the guest rebooting itself (ie someone issuing a "reboot"
from within the guest) then I think we should be able to handle that. Guests
might want to reboot for any number of reasons, and there's no reason to force
every guest to require access to the nova API in order to reboot.
If we're talking about someone logging onto a compute node and running a virsh
command (or similar) then I agree, that sort of thing should be done via nova.
Chris
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
