DeviceDomainManager version 1.0.0 Specification

[PrathibaJee]

Analysis

• Information data structure
  • control-construct
    • controller
      • ltp - own information
      • ltp - connected devices
    • mediator
      • ltp - own information
      • ltp - connected devices
    • device
  • forwarding-domain
    • forwarding-construct
      • routes
  • links
  • alarms
• Functionality formulation
  • Interpretation
  • Validation
  • Monitoring
  • Implementation
  • Measurement
• NMDA and datastore concepts
  • candidate - after interpretation , accept user input and create data objects mimicing the actual
  • running - after validation, content of candidate will be copied
  • Operational - after measurement, operational details will be updated to this DS

---

Tasks

• service.yaml preparation
• config file auto generation
• validating existing Information data structure
• Interpretation functionalities completeness
• Validation functionalities completeness(functions and mapping)
  • /v1/update-mediator-vm-template
  • /v1/establish-management-plane-transport
  • /v1/dismantle-management-plane-transport
• Monitoring functionalities completeness
  • alarms for devices - done
  • alarms for mediatorvms ?
  • alarms for controller vms ?
• Alarms and implementation tasks (functions and mapping)
  • templates -> running shall be copied to operational
  • /v1/establish-management-plane-transport
  • /v1/dismantle-management-plane-transport
• Measurement functionalities
  • device availability in controller
• OAS completeness
• PlantUML diagram for establish-management-plane-transport end to end
• Examples json objects for
  • alarms
  • controller
  • mediator
  • device
• startup datastore