1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
4 Doctor capabilities and usage
5 =============================
7 :numref:`figure1` shows the currently implemented and tested architecture of
8 Doctor. The implementation is based on OpenStack and related components. The
9 Monitor can be realized by a sample Python-based implementation provided in the
10 Doctor code repository. The Controller is realized by OpenStack Nova, Neutron
11 and Cinder for compute, network and storage, respectively. The Inspector can be
12 realized by OpenStack Congress or a sample Python-based implementation also
13 available in the code repository of Doctor. The Notifier is realized by
16 .. figure:: images/figure1.png
20 Implemented and tested architecture
23 Immediate Notification
24 ----------------------
26 Immediate notification can be used by creating 'event' type alarm via
27 OpenStack Alarming (Aodh) API with relevant internal components support.
29 See, upstream spec document:
30 http://specs.openstack.org/openstack/ceilometer-specs/specs/liberty/event-alarm-evaluator.html
32 An example of a consumer of this notification can be found in the Doctor
33 repository. It can be executed as follows:
37 git clone https://gerrit.opnfv.org/gerrit/doctor -b stable/danube
40 python consumer.py "$CONSUMER_PORT" > consumer.log 2>&1 &
42 Consistent resource state awareness
43 -----------------------------------
45 Resource state of compute host can be changed/updated according to a trigger
46 from a monitor running outside of OpenStack Compute (Nova) by using
50 http://artifacts.opnfv.org/doctor/danube/manuals/mark-host-down_manual.html
53 Valid compute host status given to VM owner
54 -------------------------------------------
56 The resource state of a compute host can be retrieved by a user with the
57 OpenStack Compute (Nova) servers API.
60 http://artifacts.opnfv.org/doctor/danube/manuals/get-valid-server-state.html