ODIM Training

Agenda for the introductory session:

  • Overview of ODIM software architectures
  • Highlight key components in ODIM
  • go through the software repository layout
  • build ODIM for a docker environment
  • Demo addition/deletion of node (if time permits)
  • Q & A

Meeting Recording

Chat File

Training PPT:

The following notes are from slide #2 that did not make it to the pdf:

External clients will be using https to access the redfish API exposed by ODIM

API service receives all requests and forwards to the required microservice and sends back the response to the requestor.

Event service is the only service that publishes events to registered https URI with out going through the API service.

All communication between microservices use go-micro/grpc(except for aggregation/task services that publish events to event service). All these communications use go-micro/https. The transport can be changed as per go-micro.

All interfaces(including kafka msgbus) need server authentication using x509 certificates by default. We can disable this however it is not recommended for security reasons.

Interfaces between ODIMRA and the plugins

  • use RESTFul interface(https) for control path from odimra to plugin and responses
  • Message bus (currently Kafka) for passing events from plugin to event service in odimra

Note: We do not prevent event based communication. Infact it is minimally used by Aggregation/Event services while pushing odimra generated events to user. Future uses can enable usage of this more often. However we have to be aware of handling issues this raise like publishers tracking the transactions across consumers etc.

Plugins may use whatever interface needed with managed devices(redfish, snmp, socket, IPMI etc.). The compute plugin (generic red fish plugin) uses redfish to talk to BMCs

Redis communication uses TCP connection(6379/6380 ports)

There is no storage plugin implemented currently as sword fish standard is not ratified yet. We do support local storage on computersystem schema

Acronyms used in slide

API – Application program interface

Aggr – Aggregation

Svc – Service

US – micro service

Note: Task service is also implemented as a micro service.

  • No labels