Age | Commit message (Collapse) | Author | Files | Lines |
|
Update requirement documentation about fencing.
Change-Id: I3c0b4aaaa31c3eb958efc5cc483821ce96082aa8
Jira: DOCTOR-10
|
|
|
|
|
|
JIRA: DOCTOR-13
Change-Id: Ie7349f71a6938407d439d28cf6f33e32e9301a31
Signed-off-by: bertys <souville@docomolab-euro.com>
|
|
JIRA: DOCTOR-15
Change-Id: Ib81f349e22cc1345831765b646ab56983f6a5f31
Signed-off-by: bertys <souville@docomolab-euro.com>
|
|
JIRA: DOCTOR-8
Change-Id: I7b9fae85bd60b1ae2d0e51f1ffb970316d7d92ad
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
|
|
|
|
A fault affecting a physical resource my affect
another physical or virtual resources. This fault correlation
shall be configurable in VIM
This patch is based on the related unresolved comment in
https://gerrit.opnfv.org/gerrit/#/c/304
JIRA: DOCTOR-4
Signed-off-by: Balazs Gibizer <balazs.gibizer@ericsson.com>
Change-Id: Ife1da03f31fc9d06bb5295157825760fc1139a36
|
|
This patch is based on the related unresolved comment in
https://gerrit.opnfv.org/gerrit/#/c/304
JIRA: DOCTOR-4
Signed-off-by: Balazs Gibizer <balazs.gibizer@ericsson.com>
Change-Id: I2cc90e0df808d5aa39fa278405327952c368baa9
|
|
|
|
|
|
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>
|
|
JIRA: DOCTOR-4
Change-Id: I089eb1dcfb9f4a6c0a24f83d626ab24e46b94a57
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
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>
|