Topic Leader(s)
- @Ricardo Gasparetto Stori
- Pankaj.Goyal
- Walter.kozlowski
Topic Overview
60 minutes Riccardo Gasparetto (incl. APAC Topic Leader) Workloads expect certain capabilities and performance from the resources that they will execute on. Creating workload specific configurations becomes not only unmanageable but may render the resources un-shareable. A profile is a set of resource configurations that meet needs of a family of workloads. Profiles partition the infrastructure resources and, thus, the number of profiles affects resource utilisation. Newer workloads, such as for 5G or O-RAN, leads to demand for new profiles or profile extensions. In Anuket, we recently decided on the concept of profile extensions. With the new definition of two high level profile abstractions and associated profile extensions, flavours have also been redefined. This session will seek a discussion on the efficacy of the adopted approach, alternatives, definition of additional profile extensions, and workload flavours.
Slides & Recording
Agenda
Minutes
- (Joao Rodriguez) Need Testing Profile
- how would it differ from Basic profile
- (Heather Kirksey) make sure that Time to Deploy, Time to Market and inter-operability is not impacted; impacts to RC and test cases for Profile-Extensions
- As we add optional extensions, how much do we need to add into testing so that internal deployment issues don't become more complex....while honoring need for some flexibility
- (Walter Kozlowski) need both qualitative and quantitative; can even specify network bandwidth rather than specific
- (Pankaj Goyal) RAs may specify limited number of extensions leaving for operators to choose others