Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
This patch is based on a related unresolved comment in
https://gerrit.opnfv.org/gerrit/#/c/304
At an earlier stage, we had identified fencing as a gap in Nova, but
this gap was removed. Who remembers why we made this decision? Is the
feature already sufficiently implemented in Nova? The related BP seems
obsoleted.
JIRA: DOCTOR-10
Co-Authored-By: Gerald Kunzmann <kunzmann@docomolab-euro.com>
Signed-off-by: Carlos Goncalves <carlos.goncalves@neclab.eu>
Change-Id: Id31ac1552a8f1e3506c5e4d533416611d6b95217
|
|
JIRA: DOCTOR-4
Change-Id: I1ce28681cf7cc6ffc01f00ddf7e36a2bc9b69978
Signed-off-by: Carlos Goncalves <carlos.goncalves@neclab.eu>
|
|
To make easier to cover the Maintenance Notification gap
a new bp was proposed to have AMQP notification for administrative
nova service status change. As soon as this bp gets implemented
Doctor (via Ceilometer) can get notification if the status of
nova service (e.g. nova-compute) is changed administratively.
Changing the nova-compute service status to down means that
nova will not use the compute node any more for new instances
so this is very much in line with putting a node in maintenance
node.
Signed-off-by: Balazs Gibizer <balazs.gibizer@ericsson.com>
Change-Id: I71a1621eb177ae6dd7da1a09285da68d398a30e8
|
|
JIRA: DOCTOR-4
Change-Id: Iaad32f25279445f9701be37f9baccd33d564372c
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
JIRA: DOCTOR-4
Change-Id: I8e1543eab71d7a24edbd6b839a55fc54f523a3d7
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
JIRA: DOCTOR-4
Change-Id: Ie80bfc8deac5822a70c1258b9ee8ffeec2b1c3a6
Signed-off-by: Carlos Goncalves <carlos.goncalves@neclab.eu>
|