Age | Commit message (Collapse) | Author | Files | Lines |
|
JIRA: DOCTOR-13
Change-Id: Ie7349f71a6938407d439d28cf6f33e32e9301a31
Signed-off-by: bertys <souville@docomolab-euro.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
|
|
|
|
|
|
|
|
Just to get some hands-on experience with git/gerrit.
Signed-off-by: kunzmann <kunzmann@docomolab-euro.com>
|
|
This is mainly to get hands-on experience on how to git commit.
JIRA: DOCTOR-6
Signed-off-by: kunzmann <kunzmann@docomolab-euro.com>
|
|
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-7
Change-Id: I77fd00994f8dbf744bc6e9ff317a5989a02c7971
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
JIRA: DOCTOR-7
Change-Id: Iec3e7242deb52e9467eb35ae16bf6f1a13331cd3
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
JIRA: DOCTOR-7
Change-Id: I080372eac4f4c6b658103faa0739db47a094dc69
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
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: Ie62751f6631c48c4dfecc869d5d95daaf6a1754f
Signed-off-by: Carlos Goncalves <carlos.goncalves@neclab.eu>
|
|
|
|
|
|
|
|
JIRA: DOCTOR-4
Change-Id: Ie80bfc8deac5822a70c1258b9ee8ffeec2b1c3a6
Signed-off-by: Carlos Goncalves <carlos.goncalves@neclab.eu>
|
|
Change-Id: Iab66227b3e030f30455fa9dee560f2c5bc1b62d7
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
JIRA: DOCTOR-6
|
|
|
|
New API call is needed to change the state of compute service "down"
immediately. This allows usage of evacuate API without a delay. Also as
external system will make sure host is down and no VMs left running,
there will be no possibility to break shared storage or use same IPs
again.
Change-Id: I0a9f805df865aadd8a250ee13cbabdf44de9567d
JIRA: DOCTOR-5
Signed-off-by: Carlos Goncalves <carlos.goncalves@neclab.eu>
|
|
Change-Id: Ide8a5b8e64d49ed366c08c5b4fc60561be614024
JIRA: DOCTOR-2
Signed-off-by: Carlos Goncalves <carlos.goncalves@neclab.eu>
|
|
NOTE: This is blueprint spec draft for OpenStack Ceilomter.
This blueprint proposes to add a new alarm evaluator for handling
alarms on events passed from other OpenStack services, that provides
event-driven alarm evaluation which makes new sequence in Ceilometer
instead of the polling-based approach of the existing Alarm Evaluator,
and realizes immediate alarm notification to end users.
JIRA: DOCTOR-3
Change-Id: Ie1a50111d82ad3c808c8ec2350e15119165cebff
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
Change-Id: I7ede23af89aaca6df1f600b84117b32ef95f87a4
JIRA: DOCTOR-1
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
Change-Id: Ia4063ad9ac1eb6fc3c70203d0ad9594681fab38c
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
https://wiki.opendaylight.org/view/Git-review_Workflow
Change-Id: Ib3aa1fb7dc2006d6a3a76d3f9e2773056ef1485c
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
|