Markdown Version | Recording 1 | Recording 2
Session Date/Time: 05 Nov 2024 09:30
nmop
Summary
This nmop meeting covered a range of topics related to network management operations, including terminology, digital maps (now C-maps), YANG push to message broker integration, incident management, and anomaly detection. The meeting included updates on existing drafts, discussions of open issues, and requests for feedback from the working group. Four "teaser" presentations of new work were also presented. Several key decisions were made regarding the adoption of drafts and the next steps for ongoing work.
Key Discussion Points
- Digital Map (C-map) Terminology:
- The working group reached a consensus on renaming "Digital Map" to "Service and Infrastructure Maps" (C-maps).
- Adrian Farrell presented the rationale behind the name change and emphasized the importance of a clear definition for the new term.
- Discussions focused on defining the scope of C-maps and avoiding linguistic bias.
- C-map Concept and Requirements:
- Olga presented updates on the C-map concept draft, including progress on terminology and use cases.
- Discussions centered on the need for defining topology, multi-layer topology vs. topology hierarchy, and describing use cases from an API perspective.
- The working group agreed to create a thread per requirement on the mailing list.
- YANG Push to Message Broker Integration:
- Thomas presented updates on the YANG push to message broker integration draft.
- Discussions revolved around the need for a new YANG model for the metadata header and the importance of having a good wrap-up on the YANG push notification and capability side.
- Rob raised concerns about how the YANG schemas are validated and what the encoding is.
- Terminology Draft:
- The working group discussed the progress of the terminology draft and its readiness for working group last call.
- The plan is to target a working group last call by the end of January next year.
- Adrian noted the importance of agreeing on or removing the last few terms that were recently added.
- Incident Manager YANG Module:
- Chin presented updates on the incident manager YANG module.
- Discussions focused on aligning the module with the terminology draft.
- Clarification was provided on focusing on network-level incidents.
- Anomaly Detection Framework:
- Alex and Vincenzo presented updates on the anomaly detection architecture, semantics for symptoms, and lifecycle drafts.
- Discussions revolved around knowledge graph integration, relevant state definition, and the structure of the model.
- Teaser Presentations:
- Robert Peschi presented "Young Templates", a way to scale up models.
- A presenter presented "AI-based Network Management Agent (NMA)", which will integrate AI with network management.
- Rob Wilton presented "Yang Push Light", a more optimized version of Yang Push.
- Diego Lopez presented "Etsi initiative on data governance", an effort to converge different solutions to make data easily accessible.
Decisions and Action Items
- Decision: Rename "Digital Map" to "Service and Infrastructure Maps" (C-maps).
- Action Item: Update all documents to reflect the new terminology.
- Action Item: Olga to create a thread per requirement for the C-map concept draft on the mailing list to gather feedback.
- Action Item: Thomas to address JSON encoding issues and propose solutions in the next revision of the YANG push integration draft.
- Decision: Target working group last call for the terminology draft by the end of January next year.
- Action Item: Chin to work on the alignment with Network Anomaly drafts, and update the incident management draft.
- Decision: Start an adoption call for the Network Economy Lifecycle and Semantic drafts.
- Action Item: Address whether any TMF revisions are required for the incident model.
- Action Item: Contact TMF about the incident young model.
Next Steps
- Authors to incorporate feedback received during the meeting into their respective drafts.
- Working group members to review the drafts and provide feedback on the mailing list.
- Schedule further interim meetings as needed to address specific issues.
Session Date/Time: 05 Nov 2024 18:00
nmop
Summary
This NMOP working group session focused on Hackathon project reports covering three key experiments: Yang Push, Digital Map (C-Map), and Network Anomaly Lifecycle. A presentation was also given on Knowledge Graphs and their application to Yang models. The presentations highlighted progress, challenges, and potential future work for each area.
Key Discussion Points
- Yang Push:
- Validation of Yang Push publisher implementation for configured subscription, aiming for a fully automatable pipeline.
- Three vendor implementations (Cisco, Huawei, Sixwind) and two open-source receiver implementations were tested.
- Focus on end-to-end preservation of metadata, schema retrieval, versioning, and transport (UDP, HTTPS).
- Digital Map (C-Map):
- Mapping network layers (L2, L3, ISIS, etc.) using RFC 8345.
- Integration of simulation/emulation scenarios for topology changes.
- Discovery labs at Swisscom and Telefonica.
- Linking topology information to configuration aspects and external data sources (e.g., RESTCONF).
- Concerns raised about complexity of using TE model as a core base model. Profile approach was discussed as a way to simplify the model for specific applications.
- T-E Topology Graphical Display:
- Development of a Young toolkit for graphically displaying T-E topology JSON instances.
- Demonstrated bi-directional links, multi-layer topologies (OTN/WDM), and underlay paths related to overlay links.
- Discussion of the concept of a profile for simplifying complex models like T-Topology.
- Debate about whether the complexity of T-Topology makes it unsuitable as a core model for CMAP. Need for a core model to be general enough to be augmented to include T-E topologies.
- Network Anomaly Lifecycle:
- Presentation of Antagonist, an open-source label store project for validating lifecycle drafts.
- Focus on enabling detection systems to improve over time by exchanging data between different stages of the lifecycle.
- Integration with rule-based anomaly detection (RFC 9418) and machine learning-based algorithms.
- Young model updates to better formalize the connection between metrics and symptoms.
- Future work involves refactoring the API using ChatGPT, exploring NoSQL databases, and integrating with the Swisscom Lab.
- Knowledge Graph (Yang to RDF):
- Created a Yang to RDF transformer using Xtext and Eclipse Modeling Framework.
- Supports full grammar, all features including augmentations, grouping, and extensions.
- Addresses comments about RDF and Yang being potential barriers.
- Code is open source.
Decisions and Action Items
- The C-Map team will further develop how to connect to external data sources.
- The C-Map and T-E topology teams will coordinate to have a more unified set of goals for the next Hackathon, enabling comparisons.
- The Anomaly Lifecycle team will explore refactoring the API and investigate NoSQL databases.
- Participants expressed interest in collaborating on the Anomaly Lifecycle project through pilots, tests, and lab access.
Next Steps
- The C-Map team will add more layers (BGP, Service X, etc.).
- The Anomaly Lifecycle team will work towards integrating with the Swisscom Lab for the next Hackathon.
- The Yang to RDF team will complete the partial translation of auto-generated IRAs.