Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

May 6th, 2021 at 1pm UTC

Action Items (In Progress)

Image Added

    • Additional information can be found on the "ONAP for Enterprise" Task Force Wiki (specially on 4/28)
    • Seshu Kumar Mudiganti - Magma may be treated as a 'resource orchestrator', and SO can have an adapter to control it like other resource controllers.Magma does not have LCM capabilities. Magma LCM requires some more research.
    • Catherine Lefevre- SO should remain generic. We need to be consistent from an Architecture's perspective i.e. what's the scope of SO vs SDNC-C? When do we take the decision to create an adapter in SO and when SDNC is used?
    • Deploying the Access GW requires running shell commands as root. This may be improved and better automated with ONAP.
    • Opportunity for ONAP: Automate scaling of Magma GW; automate the "magma services" deploymentice
  • Request from yan yan (CVC Committee) - Anuket Assured Re-Launch Release Plan to provide a go/no-go on their requirements / testing input to the badge launch.
  • CVC received the following feedback about ONAP CNF compliance - Is it correct?
    • H Release – ONAP CNF compliance requirements will be delivered by modeling subcommittee
    • I Release – ONAP CNF compliance tests implementation will be delivered by VTP (under VNFSDK)
  • Seshu Kumar Mudiganti  - Updates or requests from the XGVela project
    • Considering integration with 5G core slicing use case in ONAP.
    • Observability - Looking at VES and Prometheus.
    • In the process of finalizing the use case. More details to come soon.
    • XGVela does no plan to introduce new requirements to ONAP, at least not for Istanbul.
    • XGVela - CNF based
    • Requirements are driven by Anuket community

May 6th, 2021 at 1pm UTC

Action Items (In Progress)

  •  Catherine LefevreFollow-up with the Modeling Subcommittee about yan yanrequest
  •  Kenny Paul - Reach out to FB to meet us on May 12th, 2021 (ONAP For Enterprise Task Force) - request made to LF PM - just checked no name yet.
  •  Byung-Woo Jun: Bring the discussions to the ONAP Architecture Subcommittee about SO/SDNC role etc (see notes from 4/29)
  •  Byung-Woo Jun / Marian Darula - Provide the Ericsson packaging proposal.
  •  (Modeling/Requirements): Need to determine what ETSI CNF package solution we want to move forward (
  •  Byung-Woo Jun / Marian Darula - Provide the Ericsson packaging proposal.
  •  (Modeling/Requirements): Need to determine what ETSI CNF package solution we want to move forward (Fernando OliveiraByung-Woo Jun vs Thinh Nguyenphu)
  •  (Thinh Nguyenphu): Share an alternative (Common CNF Packaging) to what was proposed by Fernando Oliveira , Byung-Woo Jun
  •  (Olivier): Check with CNCF if any cross-meeting with ONAP could be scheduled 
  •  (All): Collect feedback about our current CNF onboarding capabilities from 3rd party vendors
  •  Kamel Idir - Will repeat onboarding with Honolulu (once he has the lab resources) and will report back
  •  (Seshu): Questions for XGVela
    • It would be great to highlight more clearly the purpose of XGVela as a platform to build CNFs and get feedback from 3rd party vendors, who are today already creating CNFS for carriers, to assess the value proposition
    • After the CNF is created via XGVela – can we then deploy the CNF on any Cloud environment without using XGVela at run-time?
    • If we need XGVela then have we performed an analysis to demonstrate the value proposition vs K8S and its ecosystem?
    • Build a slide to highlight how XGVela (i.e. create  CNF) is complementary to ONAP (onboard CNF/orchestrate CNF, etc.) and how it will fit to the CNCF Landscape

Action Items (Closed in 2021)

  •  (All) Try to identify where we are on the CNCF Trail Journey - Needs clarification to comment, need to dig into the details of the actual ask.
  •  (All): Build an ONAP proposition value to collaborate with XGVela Community
  •  (Timo): Ask the Nokia team to present preview material on 1/26
  •  (Catherine): Contact Policy/DCAE/AAI/SO PTLs to attend January 26th CNF Task Force call to review Satoshi FujiiCNF Closed Loop proposal
  •  (Catherine): Send Calendar invite - every Tuesday @2pm UTC
  •  (Catherine): Reconnect with the CNF sub-Task force: Modeling/AAI (Andy Mayer) and ETSI (Byung-Woo Jun and Fernando Oliveira ) to understand their 2021 goals on January 19th 
  •  (Kenny): Follow up with EUAG in order to determine if any particular CNF reqs (or 2021 ONAP requirements including an update to the ONAP TSC)
  •  (Seshu/Lukasz): Invite EMCO representatives
  •  (Olivier): Organise a call with Trevor Lovettand any interested CNF team members to determine how ONAP could contribute to the OVP 2021 activities
  •  (Ranny): Post the topic for the event
  •  (Catherine) Check with Olivier Smithif we can postpone OVP/ONAP discussion to another week so CNF PDN Gateway discussions can be scheduled on  March 2nd, 2021
  •  (Victor MoralesRanny Haiby): Setup additional follow-ups about CNF PDN Gateway
  •  (Timo/Catherine): Promote 2021 goals from OVP program and collect any particular requirement through ONAP Requirement and TSC meetings
  •  (Kenny): Contact EUAG about any CNF badging requirement (OVP)
  •  (Seshu): Check if user-67d6f , Lei Huang , Yan Yang can join March 9th, 2021 to discuss about OVP/ONAP & VNFSDK
  •  (Thinh): Share the ETSI event link when it will be available
  • from 3rd party vendors
  •  Kamel Idir - Will repeat onboarding with Honolulu (once he has the lab resources) and will report back

Action Items (Closed in 2021)

  •  (All) Try to identify where we are on the CNCF Trail Journey - Needs clarification to comment, need to dig into the details of the actual ask.
  •  (All): Build an ONAP proposition value to collaborate with XGVela Community
  •  (Timo): Ask the Nokia team to present preview material on 1/26
  •  (Catherine): Contact Policy/DCAE/AAI/SO PTLs to attend January 26th CNF Task Force call to review Satoshi FujiiCNF Closed Loop proposal
  •  (Catherine): Send Calendar invite - every Tuesday @2pm UTC
  •  (Catherine): Reconnect with the CNF sub-Task force: Modeling/AAI (Andy Mayer) and ETSI (Byung-Woo Jun and Fernando Oliveira ) to understand their 2021 goals on January 19th 
  •  (Kenny): Follow up with EUAG in order to determine if any particular CNF reqs (or 2021 ONAP requirements including an update to the ONAP TSC)
  •  (Seshu/Lukasz): Invite EMCO representatives
  •  (Olivier): Organise a call with Trevor Lovettand any interested CNF team members to determine how ONAP could contribute to the OVP 2021 activities
  •  (Ranny): Post the topic for the event
  •  (Catherine) Check with Olivier Smithif we can postpone OVP/ONAP discussion to another week so CNF PDN Gateway discussions can be scheduled on  March 2nd, 2021
  •  (Victor MoralesRanny Haiby): Setup additional follow-ups about CNF PDN Gateway
  •  (Timo/Catherine): Promote 2021 goals from OVP program and collect any particular requirement through ONAP Requirement and TSC meetings
  •  (Kenny): Contact EUAG about any CNF badging requirement (OVP)
  •  (Seshu): Check if user-67d6f , Lei Huang , Yan Yang can join March 9th, 2021 to discuss about OVP/ONAP & VNFSDK
  •  (Thinh): Share the ETSI event link when it will be available
  •  (Seshu): Questions for XGVela
    • It would be great to highlight more clearly the purpose of XGVela as a platform to build CNFs and get feedback from 3rd party vendors, who are today already creating CNFS for carriers, to assess the value proposition
    • After the CNF is created via XGVela – can we then deploy the CNF on any Cloud environment without using XGVela at run-time?
    • If we need XGVela then have we performed an analysis to demonstrate the value proposition vs K8S and its ecosystem?
    • Build a slide to highlight how XGVela (i.e. create  CNF) is complementary to ONAP (onboard CNF/orchestrate CNF, etc.) and how it will fit to the CNCF Landscape