Network Configuration Management with NETCONF and YANG - IETF

More documents

Recommendations

Info

RESTful API for YANG A RESTful protocol that provides a programmatic interface over HTTP for accessing data defined in YANG, using the datastores defined in NETCONF. ⊲ Configuration data and state data are exposed as resources that can be retrieved with the GET method. ⊲ Resources representing configuration data can be modified with the DELETE, PATCH, POST, and PUT methods. ⊲ Data-model specific RPC operations defined with the YANG “rpc” statement can be invoked with the POST method. ⊲ Optional transaction resource is used to allow to allow batching of edits and handling of concurrent editing transactions. 82 / 90
RESTful API for YANG Example C: GET /yang-api HTTP/1.1 C: Host: example.com S: HTTP/1.1 200 OK S: Date: Mon, 23 Apr 2012 17:01:00 GMT S: Server: example-server S: Content-Type: application/vnd.yang.api+json S: S: { S: "yang-api": { S: "capabilities": { S: "edit-model": "direct", S: "persist-model": "automatic", S: "transaction-model": "none" S: }, S: "modules": { S: "module": [ S: "urn:ietf:params:xml:ns:yang:ietf-yang-api?module=ietf-yang-api&r S: ] S: }, S: "version": "1.0" S: } S: } 83 / 90
Page 1 and 2:
Network Configuration Management wi
Page 3 and 4:
Today’s Menu . . . NETCONF The Ne
Page 5 and 6:
“The Network is the Record” Pol
Page 7 and 8:
Configuration Management Requiremen
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
NETCONF and YANG Timeline Date Mile
Page 19 and 20:
NETCONF RFCs (as of today) RFC Stat
Page 21 and 22:
Layering Model (RFC6241) Layer Exam
Page 23 and 24:
Transaction Models (RFC6241) Direct
Page 25 and 26:
Remote Procedure Calls (RFC6241) Th
Page 27 and 28:
NETCONF Operations (RFC6241) ⊲ ge
Page 29 and 30:
NETCONF Operations (RFC6241) ⊲ ge
Page 31 and 32: More NETCONF Operations (RFC5717, R
Page 33 and 34: Editing (Patching) Configuration Ex
Page 35 and 36: Subtree Filtering (cont.) ⊲ conta
Page 37 and 38: NETCONF over SSH (RFC6242) Motivati
Page 39 and 40: NETCONF over SSH: End-of-Message Fr
Page 41 and 42: NETCONF over SSH: Chunked Framing S
Page 43 and 44: YANG RFCs (as of today) RFC Status
Page 45 and 46: Modules and submodules import inclu
Page 47 and 48: Built-in Data Types Category Types
Page 49 and 50: Data Nodes: Leafs, Leaf-lists, Cont
Page 51 and 52: Example: container container system
Page 53 and 54: Augment, Must, When, Presence ⊲ a
Page 55 and 56: Example: augment and must augment /
Page 57 and 58: Grouping, Choice, Notification, RPC
Page 59 and 60: Example: choice container transfer
Page 61 and 62: Example: rpc rpc activate-software-
Page 63 and 64: Core Interfaces Data Model +--rw in
Page 65 and 66: Core IP Interfaces Data Model +--rw
Page 67 and 68: Core IP Routing Data Model (ietf-ro
Page 69 and 70: Core System Data Model: System Iden
Page 71 and 72: Core System Data Model: User Authen
Page 73 and 74: Implementations, Tools, and Usage [
Page 75 and 76: NETCONF in Devices Device Vendors (
Page 77 and 78: YANG Data Models IETF (not necessar
Page 79 and 80: YANG Mapping to JSON The mapping de
Page 81: YANG to JSON Example (XML) eth0 e
Page 85 and 86: Discussion [20 min] 1 Configuration
Page 87 and 88: Reading Material I [1] J. Schönwä
Page 89 and 90: Reading Material III [17] S. Chisho
show all

Network Configuration Management with NETCONF and YANG - IETF

Create successful ePaper yourself

Delete template?

Save as template?