A Framework for
Automating Service and Network Management with YANG
draft-ietf-opsawg-model-automation-framework-00
Networking Working Group Q. Wu, Ed.
Internet-Draft Huawei
Intended status: Informational M. Boucadair, Ed.
Expires: May 20, 2020 Orange
D. Lopez
Telefonica I+D
C. Xie
China Telecom
L. Geng
China Mobile
November 17, 2019
A Framework for Automating Service and Network Management with YANG
draft-ietf-opsawg-model-automation-framework-00
Abstract
Data models for service and network management provides a
programmatic approach for representing (virtual) services or networks
and deriving (1) configuration information that will be communicated
to network and service components that are used to build and deliver
the service and (2) state information that will be monitored and
tracked. Indeed, data models can be used during various phases of
the service and network management life cycle, such as service
instantiation, service provisioning, optimization, monitoring, and
diagnostic. Also, data models are instrumental in the automation of
network management. They also provide closed-loop control for the
sake of adaptive and deterministic service creation, delivery, and
maintenance.
This document provides a framework that describes and discusses an
architecture for service and network management automation that takes
advantage of YANG modeling technologies. This framework is drawn
from a network provider perspective irrespective of the origin of a
data module; it can accommodate even modules that are developed
outside the IETF.
The document aims to exemplify an approach that specifies the journey
from technology-agnostic services to technology-specific actions.
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
Wu, et al. Expires May 20, 2020 [Page 1]
Internet-Draft Service and Network Management Automation November 2019
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
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 May 20, 2020.
Copyright Notice
Copyright (c) 2019 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 . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Architectural Concepts & Goals . . . . . . . . . . . . . . . 5
3.1. Data Models: Layering and Representation . . . . . . . . 5
3.2. Automation of Service Delivery Procedures . . . . . . . . 7
3.3. Service Fullfillment Automation . . . . . . . . . . . . . 8
3.4. YANG Modules Integration . . . . . . . . . . . . . . . . 8
4. Architecture Overview . . . . . . . . . . . . . . . . . . . . 9
4.1. Service Lifecycle Management Procedure . . . . . . . . . 10
4.1.1. Service Exposure . . . . . . . . . . . . . . . . . . 11
4.1.2. Service Creation/Modification . . . . . . . . . . . . 11
4.1.3. Service Optimization . . . . . . . . . . . . . . . . 11
4.1.4. Service Diagnosis . . . . . . . . . . . . . . . . . . 12
4.1.5. Service Decommission . . . . . . . . . . . . . . . . 12
4.2. Service Fullfillment Management Procedure . . . . . . . . 12
4.2.1. Intended Configuration Provision . . . . . . . . . . 12
4.2.2. Configuration Validation . . . . . . . . . . . . . . 13
Show full document text