Release A Scrum (Non-RT RIC/A1 + OAM/O1) #oam


Martin Skorupski
 

Rittwik,

 

thanks for the friendly reminder 😉

The high-level idea is to „reuse“ the activities and functions of ONAP which were demoed end of June and in a series of pervious PoC – however, O1-interface requirements must be adopted.

 

Please see the following diagram: https://wiki.o-ran-sc.org/display/RICNR/Non+real+time+RIC

The content is aligned with ONAP SDN-R for Frankfurt:

https://wiki.onap.org/pages/viewpage.action?pageId=64000196 (the o-ran-sc diagram is just and PlantUml representation of the same content)

https://wiki.onap.org/display/DW/UX+Fault

 

In addition I have to look into the details of ONAP-DCAE portal and whether Kibana is also an option for AlarmLogs, …

 

I doubt that this will be topic of today, but we should add it to the agenda next week.

https://wiki.o-ran-sc.org/display/OAM/calendars?src=sidebar

 

Until then I can prepare also some content …

I will propose, avoiding  that each project creates its own OAM portal, the O1-Interface is for all ManagedElements the same. (not sure if everybody follows such idea, we will see …)

 

Have fun,

Martin

 

 

Von: JANA, RITTWIK (RITTWIK) <rjana@...>
Gesendet: Montag, 29. Juli 2019 15:02
An: VAN BRAKLE, TRACY L <tv8394@...>; 'john.keeney@...' <john.keeney@...>; SMITH JR., PAUL <ps7360@...>; GUPTA, DHRUV <dg285u@...>; KIM, DONGHO <dk5913@...>; 'Haseeb Akhtar' <haseeb.akhtar@...>; Ramakrishnan, Shanthakumar (Shanth) <Shanthakumar.Ramakrishnan@...>; Michalak, Marek (Nokia - PL/Wroclaw) <marek.michalak@...>; 'junhyuk.song@...' <junhyuk.song@...>; 'damian.nowak@...' <damian.nowak@...>; lixaingyjy <lixiangyjy@...>; FOWLER, HENRY J <hf9857@...>; TIMONEY, DAN <dt5972@...>; 'Martin Skorupski' <martin.skorupski@...>
Cc: 'QiSun QiSun (sunqiyjy@...)' <sunqiyjy@...>; 'wujieyjy' <wujieyjy@...>; '
解宇瑄' <xieyuxuan@...>; huangjinri@...; suxin@...; KINSEY, DAVID F <dk8126@...>; MURRAY, JOHN F (JOHN) <jfm@...>
Betreff: RE: Release A Scrum (Non-RT RIC/A1 + OAM/O1)

 

Tracy, Martin,

 

I just wanted to make sure that we do not forget about the epics for dashboard and portal that are also under OAM category. While we discuss OAM/O1, we should keep track of the portal epics also. These are for Release A. Most of these (except for the OTF epic) have already been implemented as part of the RIC co-create.

 

A.      Dashboard/portal

Title

[OAM-A-F01] RIC Dashboard

Description

As a RIC Operator I need an initial way to manage a single RIC instance for monitoring and control during evaluation of the RIC in a network scenario. [RICPLT-R1-F3]

Acceptance Criteria

User interface with connectivity to a RIC instance via pre-standard interfaces.

Source

RIC Co-Create R1 (AT&T)

 

Title

[OAM-A-F02] RIC Connectivity Dashboard

Description

Enable control of connecting/disconnecting the RIC to/from a gNB (via the E2 Manager)

Acceptance Criteria

User Interface to add or delete gNodeB E2 endpoints to the scope of a RIC instance.

Source

RIC Co-Create R1 (AT&T)

 

Title

[OAM-A-F03] RIC Service Assurance Dashboard

Description

Display metrics from each xApp (how to make this generic TBD - JSON/yang/?)

Acceptance Criteria

User Interface to view alarms (optional) and performance metrics collected from a RIC Instance and data received from any of its xAPPs.

Source

RIC Co-Create R1  (AT&T), alarms in Release B

 

Title

[OAM-A-F04] RIC Xapp management Dashboard

Description

Provide a method to LCM (onboard, deploy), configure  Xapps in a generic way (e.g., yang definition of the interface)

Acceptance Criteria

User Interface to compose commands or data to exposed RIC APIs.

Source

RIC Co-Create R1 (AT&T)

 

Title

[OAM-A-F05] O-RAN-SC Certification Dashboard

Description

Provide a Portal for viewing previously executed tests and to visually show current tests in progress.

Acceptance Criteria

User Interface to view test already completed, in progress, or scheduled to be executed.

Source

OTF (AT&T)

 

Thanks,

Rittwik

-----Original Appointment-----

From: VAN BRAKLE, TRACY L <tv8394@...>
Sent: Monday, July 29, 2019 8:43 AM
To: 'john.keeney@...'; SMITH JR., PAUL; GUPTA, DHRUV; KIM, DONGHO; 'Haseeb Akhtar'; Ramakrishnan, Shanthakumar (Shanth); Michalak, Marek (Nokia - PL/Wroclaw); 'junhyuk.song@...'; 'damian.nowak@...'; lixaingyjy; JANA, RITTWIK (RITTWIK); FOWLER, HENRY J; TIMONEY, DAN; 'Martin Skorupski'
Cc: 'QiSun QiSun (sunqiyjy@...)'; 'wujieyjy'; '解宇瑄'; huangjinri@...; suxin@...
Subject: Release A Scrum (Non-RT RIC/A1 + OAM/O1)
When: Monday, July 29, 2019 11:00 AM-12:00 PM (UTC-05:00) Eastern Time (US & Canada).
Where: https://zoom.us/j/436210993

 

 


David Kinsey
 

INRE separate portal for each project. This is likely the best choice to decouple the projects and get them started. However, there should be some basic principles since all elements should develop towards the O1 specification eventually the portals should be collapsed into a single OAM portal.

 

From: martin.skorupski@... <martin.skorupski@...>
Sent: Monday, July 29, 2019 6:51 AM
To: JANA, RITTWIK <rjana@...>; VAN BRAKLE, TRACY L <tv8394@...>; john.keeney@...; SMITH JR., PAUL <PS7360@...>; GUPTA, DHRUV <dg285u@...>; KIM, DONGHO <dk5913@...>; 'Haseeb Akhtar' <haseeb.akhtar@...>; 'Ramakrishnan, Shanthakumar (Shanth)' <Shanthakumar.Ramakrishnan@...>; 'Michalak, Marek (Nokia - PL/Wroclaw)' <marek.michalak@...>; junhyuk.song@...; damian.nowak@...; 'lixaingyjy' <lixiangyjy@...>; FOWLER, HENRY J <hf9857@...>; TIMONEY, DAN <dt5972@...>
Cc: 'QiSun QiSun' <sunqiyjy@...>; 'wujieyjy' <wujieyjy@...>; '
解宇瑄' <xieyuxuan@...>; huangjinri@...; suxin@...; KINSEY, DAVID F <dk8126@...>; MURRAY, JOHN <jfm@...>; main@...; 'Alfons Mittermaier' <alfons.mittermaier@...>; matthias.fischer@...; 'Herbert Eiselt' <herbert.eiselt@...>; 'Alexander Dehn' <Alexander.Dehn@...>
Subject: AW: Release A Scrum (Non-RT RIC/A1 + OAM/O1) #oam

 

Rittwik,

 

thanks for the friendly reminder 😉

The high-level idea is to „reuse“ the activities and functions of ONAP which were demoed end of June and in a series of pervious PoC – however, O1-interface requirements must be adopted.

 

Please see the following diagram: https://wiki.o-ran-sc.org/display/RICNR/Non+real+time+RIC

The content is aligned with ONAP SDN-R for Frankfurt:

https://wiki.onap.org/pages/viewpage.action?pageId=64000196 (the o-ran-sc diagram is just and PlantUml representation of the same content)

https://wiki.onap.org/display/DW/UX+Fault

 

In addition I have to look into the details of ONAP-DCAE portal and whether Kibana is also an option for AlarmLogs, …

 

I doubt that this will be topic of today, but we should add it to the agenda next week.

https://wiki.o-ran-sc.org/display/OAM/calendars?src=sidebar

 

Until then I can prepare also some content …

I will propose, avoiding  that each project creates its own OAM portal, the O1-Interface is for all ManagedElements the same. (not sure if everybody follows such idea, we will see …)

 

Have fun,

Martin

 

 

Von: JANA, RITTWIK (RITTWIK) <rjana@...>
Gesendet: Montag, 29. Juli 2019 15:02
An: VAN BRAKLE, TRACY L <tv8394@...>; 'john.keeney@...' <john.keeney@...>; SMITH JR., PAUL <ps7360@...>; GUPTA, DHRUV <dg285u@...>; KIM, DONGHO <dk5913@...>; 'Haseeb Akhtar' <haseeb.akhtar@...>; Ramakrishnan, Shanthakumar (Shanth) <Shanthakumar.Ramakrishnan@...>; Michalak, Marek (Nokia - PL/Wroclaw) <marek.michalak@...>; 'junhyuk.song@...' <junhyuk.song@...>; 'damian.nowak@...' <damian.nowak@...>; lixaingyjy <lixiangyjy@...>; FOWLER, HENRY J <hf9857@...>; TIMONEY, DAN <dt5972@...>; 'Martin Skorupski' <martin.skorupski@...>
Cc: 'QiSun QiSun (sunqiyjy@...)' <sunqiyjy@...>; 'wujieyjy' <wujieyjy@...>; '
解宇瑄' <xieyuxuan@...>; huangjinri@...; suxin@...; KINSEY, DAVID F <dk8126@...>; MURRAY, JOHN F (JOHN) <jfm@...>
Betreff: RE: Release A Scrum (Non-RT RIC/A1 + OAM/O1)

 

Tracy, Martin,

 

I just wanted to make sure that we do not forget about the epics for dashboard and portal that are also under OAM category. While we discuss OAM/O1, we should keep track of the portal epics also. These are for Release A. Most of these (except for the OTF epic) have already been implemented as part of the RIC co-create.

 

A.      Dashboard/portal

Title

[OAM-A-F01] RIC Dashboard

Description

As a RIC Operator I need an initial way to manage a single RIC instance for monitoring and control during evaluation of the RIC in a network scenario. [RICPLT-R1-F3]

Acceptance Criteria

User interface with connectivity to a RIC instance via pre-standard interfaces.

Source

RIC Co-Create R1 (AT&T)

 

Title

[OAM-A-F02] RIC Connectivity Dashboard

Description

Enable control of connecting/disconnecting the RIC to/from a gNB (via the E2 Manager)

Acceptance Criteria

User Interface to add or delete gNodeB E2 endpoints to the scope of a RIC instance.

Source

RIC Co-Create R1 (AT&T)

 

Title

[OAM-A-F03] RIC Service Assurance Dashboard

Description

Display metrics from each xApp (how to make this generic TBD - JSON/yang/?)

Acceptance Criteria

User Interface to view alarms (optional) and performance metrics collected from a RIC Instance and data received from any of its xAPPs.

Source

RIC Co-Create R1  (AT&T), alarms in Release B

 

Title

[OAM-A-F04] RIC Xapp management Dashboard

Description

Provide a method to LCM (onboard, deploy), configure  Xapps in a generic way (e.g., yang definition of the interface)

Acceptance Criteria

User Interface to compose commands or data to exposed RIC APIs.

Source

RIC Co-Create R1 (AT&T)

 

Title

[OAM-A-F05] O-RAN-SC Certification Dashboard

Description

Provide a Portal for viewing previously executed tests and to visually show current tests in progress.

Acceptance Criteria

User Interface to view test already completed, in progress, or scheduled to be executed.

Source

OTF (AT&T)

 

Thanks,

Rittwik

-----Original Appointment-----
From: VAN BRAKLE, TRACY L <tv8394@...>
Sent: Monday, July 29, 2019 8:43 AM
To: 'john.keeney@...'; SMITH JR., PAUL; GUPTA, DHRUV; KIM, DONGHO; 'Haseeb Akhtar'; Ramakrishnan, Shanthakumar (Shanth); Michalak, Marek (Nokia - PL/Wroclaw); 'junhyuk.song@...'; 'damian.nowak@...'; lixaingyjy; JANA, RITTWIK (RITTWIK); FOWLER, HENRY J; TIMONEY, DAN; 'Martin Skorupski'
Cc: 'QiSun QiSun (sunqiyjy@...)'; 'wujieyjy'; '解宇瑄'; huangjinri@...; suxin@...
Subject: Release A Scrum (Non-RT RIC/A1 + OAM/O1)
When: Monday, July 29, 2019 11:00 AM-12:00 PM (UTC-05:00) Eastern Time (US & Canada).
Where: https://zoom.us/j/436210993