Open Transport Configuration & Control
Space shortcuts
Expand all   Collapse all
Child pages
  • 2021-11-24 5G-xHaul Meeting notes
Skip to end of metadata
Go to start of metadata

 | 2am PST | 5am EST | 10:00 UTC | 10:00 GMT | 11:00 CET | 12:00 EET | 15:30 IST | 18:00 CST | 19:00 JST |


Web Conference:

https://thorsten-heinze-telefonica-de.webex.com/thorsten-heinze-telefonica-de/j.php?MTID=m849236edb092dffd10071725f5b8839f 

Invited:

(please feel free to correct and update your names (wink) Thank you very much!!!) 

Info to: 

Goals

  • going forward


Mailings

Discussion items

TimeItemWhoNotes
00:00Chair topic 
no update 

00:01

Admin

2021-12-01: Martin Skorupski

2021-12-08: Martin Skorupski

2021-12-15: Martin Skorupski 

2021-12-22: Martin Skorupski

2021-12-29: proposal: canceled

2022-01-05: proposal: canceled

2022-01-12: Martin Skorupski

00:01Synchronization

@Alexander Wenk

@Prathiba

Some answer about modeling and mappings can be found here

Looks like there are different versions with similar but different content.

YANG generation process:

  • core-model-1-4.yang → pending (5/11 issues are done)
  • sync-model-1-0.yang → generated but requires core-model updates

addressing circular dependencies for "configuration-and-switch-control"

Options

  1. fc-switch attribute should result in a leaf-list of type leafref
  2. the internal-configuration-and-switch-control should use a different grouping


00:10Mediator Instance Manager

Thorsten Heinze

Pre- Discussion happened yesterday 

  • info send by Thorsten on Monday 2021-05-177
  • in addition Thorsten will send the "background discussion slide"....

Mediator Instance Manager 

  • What is the protocol? NETCONF or REST or RESTCONF or ...
    • Working Assumption:  not decided
    • SIAE would like to decide based on efforts after analysis. 
    • UML include the "service" - but not the operational and maintenance layer
    • YAML (OpenAPI3) → UML (papyrus) → YANG → 

2021-05-25

  • Any questions?
    • no questions

2021-06-16

  • please see "App layer on top of the SDN controller" above.

2021-11-24

  • Introduction to the topic 
  • functional requirements
  • how to address security constrains and its key management
  • impact on MediatorInstanceManager
    • including logging mechanism
  •  option to reuse code provided by TEF
00:45

Centralized alarm list

(alarm definition, capability and notification)

Thorsten Heinze 

Continue UML Modeling

  • Clarification of alarmTypeId and probableCause based on examples...

END OF THE MEETING

00:00Relation between planning and actual data from the network

Question related Sequence-Id

  • live-cycle: How to share the usage between vendor and operator
  • Impact for changes during run-time
  • Target: no additional document by vendors required - not sure?!?!?!

Question to be ask to Thomas and Alex.

00:00Synchronization

@Alexander Wenk

@Prathiba

Some answer about modeling and mappings can be found here

Looks like there are different versions with similar but different content.

YANG generation process:

  • core-model-1-4.yang → pending (5/11 issues are done)
  • sync-model-1-0.yang → generated but requires core-model updates
00:

Relation between planning and actual data from the network


@Andreas Lattoch

Quick synch from last week

  • connector types to be standardized
  • work in progress - to be continued
  • Current work bases on the "EquipmentModel"

updated proposal

  • holders identified by a, c, ...
  • connectors identified by 0, 1, ...

See updated document:

https://wiki.opennetworking.org/download/attachments/265093121/proposal-sequence-id.docx?api=v2

Action items