1. **DRAFT**
Doctor Southbound API
23 Feb 2016
Ryota Mibu, NEC

2. Doctor Southbound API Configuration Fault Messaging Unified Event API
Admin
Threshold
Enable
Conf.
Policy
Conf.
Enable
NFVI
Monitor
Inspector
Controller
Notifier
User
Monitor
Unified Event API
Monitor
Event
Physical Resource
Virtual Resource

3. [Proposal] Doctor Southbound API - Event
URI:
Entity:
event:
id  This will be added by inspector (UUID).
time  Observed time in monitor
type  This will be used to process correlation
detail:  This contains optional params.
hostname
status
monitor  ID of monitor reporting
ref_id  ID in monitor (log) {
‘event’: {
‘id’: ‘cf674c50-eb9d-…-1e82f7391c73’,
‘time’: ‘ T13:27: ’,
‘type’: ‘compute.host.down’,
‘detail’: {
‘hostname’: ‘compute-1’,
‘status’: ‘down’,
‘monitor’: ‘monitor-1’,
‘ref_id’: ‘123’, }

4. [Alternative] Doctor Southbound API – Physical Resource
URI:
Entity: resource
Difference from event:
Message contains resource ID recognizable by Inspector
Comparison
Pros: Inspector can handle message easily
Cons: Monitor has to know unified types and IDs of target resources
# Inspector becomes resource topology manager rather than functional block inspecting fault referring resource map of controller.