Daily meeting sessions
- P1 (09:00 – 10:30 Sydney) (6:00 pm - 7:30 pm New York, day before) (3:00 pm -4:30 pm San Francisco, day before)
- P2 (11:00 – 12:30 Sydney)
- P3 (13:30 – 15:30 Sydney)
- P4 (16:00 – 17:30 Sydney)
ZOOM link: https://ciena.zoom.us/j/658668041 continuously for the whole week
Minutes: 2019-03-18~22 OIMT & OTCC Sydney Meeting Notes
Agenda plan
Day | Period | Topic (Lead & Work Item) | Document / Link | Comment |
---|
Monday 18th | 1.1 | | |
|
- C7 Identify model (CH #41)
| |
|
1.2 | | |
|
1.3 | - T1 Connectivity & Topology (KS, AM)
| |
|
1.4 | | |
|
| |
|
Tuesday 19th | 2.1 | - T12 Photonic connectivity (AM, KS)
| | Send ZOOM invitation to Stephane & Stephen to dial-in |
2.2 | - T9 ML Transitional link (AM)
| |
|
2.L | | |
|
2.3 | | | Will be using the model from TAPI Github https://github.com/nigel-r-davis/TAPI |
2.4 | |
Wednesday 20th | 3.1 | - T12 Alarm/TCA Notification/OamProfile Framework (KS, AM)
|
|
|
3.2 | - T4, T5 (& C11) Catalog driven API & Operation pattern (KS)
| |
|
3.3 | |
|
|
3.4 | | |
|
- C6 Model refactoring (CH/ND #13)
|
|
|
Thursday 21st | 4.1 | |
|
|
4.2 | | oimt.2019.ND.009.01_ProvidingAndMaintainingAView.pptx (ND) |
|
4.3 | |
| Contribution will be late |
4.4 | - C5 Spec re-work (ND #37 (#44, 56, 58))
|
| Contribution will be late |
Friday 22nd | 5.1 | - C4 TOSCA profile (CH #55, #26?)
|
|
|
- C13 Profile & Template (ND #57)
| oimt.2019.ND.008.00_PropertyValueProfiles.pptx (ND) |
|
5.2 | - Review of work item XLS & F2F action items (KL)
| |
|
Key topics (Pink updates are input from the March 5 TAPI call)
- Key Core model topics: (8.5 slots)
- #8 Equipment enhancements (TAPI equipment modeling) (Color code: This color means Have material already) 2 slots
- Complete TAPI equipment (attach to NEP and CEP etc.), including determine which parts we need,
- examine expectation/actual model, and validate the approach
- Define the equipment spec model (which is not in place in the core)
- #35 LTP port (TAPI integration) - 1 slot
- #9 IP switching, #53 IP Segment routing (to support 5G, complement SG15 work) (Kam 1/2 slot)
- #26 Intent/Constraint, #55 TOSCA Profile (Color code: This color means Ready to go) (CH - 1/2 slot)
- #37 Spec re-work, #44 Refactor LTP Spec to be Comp-Sys Spec, #56 Simplied Spec model, #58 Specification Pattern for new comer, including Thorsten's (Core model extension) work request (TAPI critical) ~2 slots
- #13 Model refactoring (Color code: This color means New agenda item) CH/ND - 1/2 slot
- #41 Identity model investigation + other global class attributes (state etc.) (Ready to go) (CH - 1/2 slot)
- #39 Event driven solution investigation, including Streaming (TAPI) 1 slot,
- #43 Operation pattern for general task (ND), #57 Job Task process model, (CH - 1/2 slot)
(related to #54) Managing Cloud Native (Kubernetes, Istio, Containers)- Catalog consideration in TMF, MEF, ONAP, TOSCA,
#55 TOSCA Profile (covered by TAPI item T4)(moved to C4) Examine the storage pattern and the model that relates the views (?) (CH, ND) (from T7)
- Profile & Template (Thorsten requirement) #57
- Entities and Datatypes
NOTE: Description of OIMT work items are in oimt2018.KL.001.14_oimt-work-items.xlsx
- Key TAPI topics (8 slots)
- Enhancement (including re-factoring) of the connectivity and topology models (KS, AM) 1 slot (Total 3 slots including subtopics)
- T3 Topology Pac (1/2 slot)
- T1 Connection/Route relationship to topology (1 slot)
- T8 Link capacity (1 slot)
- T6 Virtual network (1/2 slot)
- Routing constraint & Resilience (need this for 2.2), related to #26 (AM) 1 slot
- How to use the topology Pacs in TAPI (ND) 1/2 slot
- Specification model for Catalog driven API (KS) 1.5 slot → 1 slot (Total 2 slots including subtopics)
- T4 Operation patterns (1 slot)
- T5 Catalog driven API (1 slot)
- Configuration v state, CRUD pattern, operation patterns, intent, RPC v Action (related to Core item 9) (KS) 1.5 slot → 1 slot
- Revisit the TAPI virtual network (What is the difference between VN Service End Point vs Service Interface Point), Service v resource (ND) (related to TAPI item 1) 1/2 slot
- Examine the storage pattern and the model that relates the views (?) (CH, ND) → C12
- Examine Link capacity allocation pattern (MB). Work towards the goal of Virtual Network 1 slot
- The point problem is relatively straight forward
- The two ended link brings in the most basic form of graph
- We can build from the above towards more complex graphs towards the full network problem
- Eventually this will lead to system - system mapping (PC graphs)
- Multilayer transitional link scenario (need this before 2.2) (AM) 1 slot
- Photonic connectivity 1 slot
ONAP usage of TAPI- Alarm/TCA Notification/OamProfile Framework
Aim to finalize the agenda plan by Feb. 18
This is the original table. It will be deleted once the table above has been reviewed.
Day | Period | Topic | Document / Link | Note |
---|
Monday 18th | 1.1 | - T1 Connectivity & Topology
| | KS, AM |
1.2 | | | AM |
1.3 | | | ND #8 |
1.4 | | | ND #8 |
Tuesday 19th | 2.1 | | | MB |
2.2 | | | AM |
2.3 | | | ND #35 |
2.4 | - C3 IP model & C6 Model refactoring
|
| KL #9, #53 & CH/ND #13 |
Wednesday 20th | 3.1 | | | KS |
3.2 | - C9 Job model
& T5 Operation pattern & T12 Photonic connectiivty
| | KS CH #57 |
3.3 | - T3 Topology pac & C7 Identify model
| | ND CH #41 |
3.4 | | | ND #39 |
Thursday 21st | 4.1 | - T4 (& C11) Catalog driven API
| | KS |
4.2 | - T6 TAPI VN
&T4 Catalog driven API & T12 Photonic connectivity
|
| KS |
4.3 | | | ND |
4.4 | | | ND |
Friday 22nd | 5.1 | | | CH #55 |
5.2 | - Review of work item XLS & F2F action items
| | KL |