blob: 1564b51aa85da5c4c22890061bb86f1014a84798 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
Doctor platform components and features
=======================================
..
This section will be compiled into OPNFV composite document.
https://wiki.opnfv.org/doctor
Features
--------
Doctor platform provides these features in `Colorado Release <https://wiki.opnfv.org/display/SWREL/Colorado>`_:
* Immediate Notification
* Consistent resource state awareness for compute host down
* Valid compute host status given to VM owner
These features enable high availability of Network Services on top of
the virtualized infrastructure.
Immediate notification allows VNF managers (VNFM) to process recovery
actions promptly once a failure has occurred.
Consistency of resource state is necessary to properly execute recovery
actions properly in the VIM.
Ability to query host status gives VM owner (VNFM) the possibility to get
consistent state information through an API in case of a compute host
fault.
Components
----------
Doctor platform, as of Colorado release, consists of the following
components:
* OpenStack Compute (Nova)
* OpenStack Telemetry (Ceilometer)
* OpenStack Alarming (Aodh)
* Doctor Inspector
* Doctor Monitor
.. note::
Doctor Inspector and Monitor are sample implementation for reference.
You can see an overview of the Doctor platform and how components interact in
:numref:`figure-p1`.
.. figure:: images/figure-p1.png
:name: figure-p1
:width: 100%
Doctor platform and typical sequence (Brahmaputra)
Detailed information on the Doctor architecture can be found in the Doctor
requirements documentation:
http://artifacts.opnfv.org/doctor/docs/requirements/05-implementation.html
|
