A Framework for Automating Service and Network Management with YANG
draft-ietf-opsawg-model-automation-framework-06
OPSAWG Q. Wu, Ed.
Internet-Draft Huawei
Intended status: Informational M. Boucadair, Ed.
Expires: March 26, 2021 Orange
D. Lopez
Telefonica I+D
C. Xie
China Telecom
L. Geng
China Mobile
September 22, 2020
A Framework for Automating Service and Network Management with YANG
draft-ietf-opsawg-model-automation-framework-06
Abstract
Data models provide a programmatic approach to represent services and
networks. Concretely, they can be used to derive configuration
information for network and service components, and state information
that will be monitored and tracked. Data models can be used during
the service and network management life cycle, such as service
instantiation, provisioning, optimization, monitoring, diagnostic,
and assurance. Data models are also instrumental in the automation
of network management, and they can provide closed-loop control for
adaptive and deterministic service creation, delivery, and
maintenance.
This document describes an architecture for service and network
management automation that takes advantage of YANG modeling
technologies. This architecture is drawn from a network operator
perspective irrespective of the origin of a data module; it can thus
accommodate modules that are developed outside the IETF.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
Wu, et al. Expires March 26, 2021 [Page 1]
Internet-Draft Service and Network Management Automation September 2020
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 26, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology and Acronyms . . . . . . . . . . . . . . . . . . 5
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Architectural Concepts and Goals . . . . . . . . . . . . . . 6
3.1. Data Models: Layering and Representation . . . . . . . . 6
3.2. Automation of Service Delivery Procedures . . . . . . . . 10
3.3. Service Fullfillment Automation . . . . . . . . . . . . . 10
3.4. YANG Modules Integration . . . . . . . . . . . . . . . . 11
4. Functional Blocks and Interactions . . . . . . . . . . . . . 11
4.1. Service Lifecycle Management Procedure . . . . . . . . . 12
4.1.1. Service Exposure . . . . . . . . . . . . . . . . . . 13
4.1.2. Service Creation/Modification . . . . . . . . . . . . 13
4.1.3. Service Optimization . . . . . . . . . . . . . . . . 13
4.1.4. Service Diagnosis . . . . . . . . . . . . . . . . . . 14
4.1.5. Service Decommission . . . . . . . . . . . . . . . . 14
4.2. Service Fullfillment Management Procedure . . . . . . . . 14
4.2.1. Intended Configuration Provision . . . . . . . . . . 15
4.2.2. Configuration Validation . . . . . . . . . . . . . . 15
4.2.3. Performance Monitoring/Model-driven Telemetry . . . . 16
4.2.4. Fault Diagnostic . . . . . . . . . . . . . . . . . . 16
Show full document text