Participants
Attendees | Name | Company |
X | Louis Illuzzi | LFN |
Kenny Paul | LFN | |
Jim Baker | LFN | |
X | Casey Cain | LFN |
X | Jonas Arndt | Red Hat |
William Caban | Red Hat | |
X | Bharath Kumar | HPE |
X | Martin Halstead | HPE |
X | Jon Mechling | HPE |
X | Susan Bowen | HPE |
X | Alex Vul | Intel |
John Leung | Intel | |
Piotr Zedlewski | Intel | |
X | Bob Monkman | Intel |
X | Rafal Sztejna | Intel |
Daniel Nilsson | TietoEVRY | |
X | Marcin Nicpon | TietoEVRY |
X | Muthu Ramalingum | AMI |
Jose Inbaraj | AMI | |
Divya Nettum | AMI | |
Tomas Fredberg | Ericsson |
Proposed Agenda
- Start Recording
- LF Antitrust Policy
- Arch Issues:
- DMTF Profiles Proposal
- Properties for UpdateService
- Support redis streams as alternative to Kafka bus (updated proposal as per discussion last week)
- Persist events in online DB during network outages
- Governance Issues:
- Status of Dell plugin
- Status of AMI composition service
Recording link
Architecture discussion notes
We could only discuss the DMTF profiles proposal issue.
DMTF Profiles Proposal
Redfish implementations can have interop issues. Hence there is a provision for profiles. Introducing profiles in ODIM will help
- Hardware vendors adopt the properties
- plugin developers understand what is/not required to integrate with ODIM. Fabric profile needed by for eg. Cisco ACI plugin
BMC emulator or any contributed code should adhere to the same.
OCP profiles were created to ensure some degree of interoperability. It specifies H/W and S/W management. ODIM profile is a super set of OCP profile. As OCP is not updated for around 2 years we need to update the same. TietoEvery also agrees there is benefit in having a profile defined for ODIM. AMI also feels it is good to have a profile.
we don't need vote immediately. Let the members go through the proposal and vote the next week.
Governance meeting notes
Not discussed.