Recording
Chat File
Participants
TBD
Proposed Agenda
- Start Recording
- Antitrust Policy
- Brainstorm about ODIM demos for Super Blueprint
- LFN developer and testing forum- LFN asks that toipic proposals be submitted by Friday 05/14 to allow time for scheduling then sessions.
Notes
ODIM in super blueprint brainstorming
Objective is to get ODIM included in the 5g Super Blueprint architecture slide
ACTION ITEMS:
- Alex sent email with the slide explaining ODIM.
- Daniel will take the slide to the next 5G Super Blueprint meeting (next Tuesday) and explain, ask whether ODIM can be added. OK to add under management and orchestration for now.
Upcoming LFN Developer and Testing Forum Conference (June)
Includes a half hour session describing ODIM updates since last conference (one slide), plus the possibility of doing a BMC Emulator Demo.
ACTION ITEMS:
- Jonas will enter Topic Leader and Topic Overview for the half hour session.
- Alex will check with Rafal about a separate demo of the BMC emulator.
ODIM Architecture
Current and future (add to the ODIM website)
ACTION ITEM:
- Update from Jonas’s work to start a slide deck in Gliffy. Jonas will continue on the slide and start the future architecture slide as well.
ODIM Release Roadmap Update
ODIM 21.08 release, currently planned
Features
- Redfish-compliant Telemetry Service
- Update to 2021.1 DMTF schema
- Dell iDRAC plugin
- Cisco ACI plugin
- BMC Emulator
- Composition Service
Hold off on the following – not agreed. Developer Environment Changes
- Replace Docker with Kubernetes for building and deploying ODIM, single node deployment and three node cluster
-------------------
Detailed notes
ODIM in super blueprint brainstorming
https://www.lfnetworking.org/5g-super-blueprint/
- (Daniel)– there is no perfect fit in the current demos. Potential upcoming demo of end to end network could be an opportunity.
- Right now, basics to get functions to work in container environment
- Long term, super blueprint incorporates a lot of projects that are part of base platform. Edge scenario & a 5G demo that fits into this story.
- Look at initial work and demos (Daniel, simple demo in Dec, internal training – revive and re-use?)
- Short term – June presentation LFN conference, one slide to position ODIM in super blueprint. Why we should be in the picture and where we would fit in. Small box in infrastructure management.
- (Jonas). Current super blueprint, everything up and running, no setting up HW or provisioning
- (Louis) get into next super blueprint meeting (Kenny Paul) and talk about ODIM and super blueprint.
Put ODIM next to ONAP etc.
Alex, open stack has elements of standalone, he talked about what Aunket is doing? Sorry missed it.
ODIM is below all this, Alex said. Infra mgmt vs. Infra Ops (at least get our logo in there)
Daniel – have our own box? Alex could be at same level as SDN Controller (Open Daylight). Put ODIM down below? SDN Controller, next to it ONAP. Then physical network. Above is infra orchestrator. Make Infra Mgmt Infra Orchestration and put ODIM beneath. Jonas – easier to get add ODIM than rearrange their picture.
Jonas – how to push ODIM into 5G Super Blueprint picture.
Daniel – we also need how we fit into CNTT team. Fit that into the Anuket picture? Aunket covers the whole CNTT scope? OPNFV + CNTT = Anuket. (Tomas Fredberg).
Jonas showed slide for this. Tomas – partially inside and partially over and above.
Tomas: Anuket tries to standardize around cloud infra.
Alex showed slides:
Older slide Alex showed where ONAP is. Top down intent based orchestration (Anuket) but sequence of layers. ONAP could be in the boxes. Or Kubernetes or other things.
Airship or Ironic that relates to what ODIM is.
If we substitute logos this may explain where we fit in. Out of band experience mapping into day 1 bare metal provisioning like Airship Ties same single source of truth to OS and ??
Above that ?? sorry missed parts of what he said.
Alex says Daniel was saying where ODIM fits in, get our logo into the super blueprint slide. Daniel – makes sense. We want to be in that box and this slide shows WHY.
Jonas – need the one slide for Dev and Test forum. 1) convince super blueprint, then create for LFN forum.
AVOID them learning that we inserted ourselves into super blueprint.
ACTION ITEM: Alex sent email with the slides. Daniel will pick up there. Meeting is next Tuesday.
Jonas – Q about ONES this fall? Daniel either that or (something earlier?) Daniel we don’t fit in cleanly to anything right now. We have to convince them to include what happens before everything is up and running (the super blueprint view). Alex – day zero, day one etc. and where ODIM fits in. Use of ODIM – onboarding resources, instantiation of resources and in Ops as well. Fantasy to start when it is all done.
Daniel – this is for the presentations not the demos. Demos are one step away from this.
Upcoming Dev and Test Forum (next topic)
Alex – we have the standard deck used in TAC (?) and other conferences. Jonas – short problem description (what we are solving). Alex – put it out there and get consensus. Jonas – we have 30 min. project updates and plan for next release.
Include the slide from Daniel on how ODIM fits into super blueprint effort. Then Q and A. Alex re-use as we can. Jonas – if we have something on Airship by then, include it.
Louis – topic proposal due this Friday. Jonas will take action item to enter. He went back to notes from last week. Louis – we have something to deliver. Jonas – who could add the topic by this Friday? Jonas no time to develop a new demo
fill in Topic leader, Topic overview only
ACTION ITEM: Alex will check with Rafal about Separate DEMO for the BMC Emulator
Jonas took an Action Item to start creating a slide deck (Gliffy)
Jonas – will start the future architecture slide as well.
ODIM 21.08 release, currently planned
Features
- Redfish-compliant Telemetry Service
- Update to 2021.1 DMTF schema
- Dell iDRAC plugin
- Cisco ACI plugin
- BMC Emulator
- Composition Service
Developer Environment Changes
- Replace Docker with Kubernetes for building and deploying ODIM
- single node deployment and three node cluster
