As somebody who has been bitten by trying to perform a create operation and faced validation issues as I've mistakenly sent (or worse, edited) a read-only field in a request, I feel this is really valuable.Īnother great thing from an operations perspective is the ability to test/validate configuration before it's applied to the device. NETCONF understands the difference between configuration data and state data. It's not a new technology, as work started on this approximately 10 years ago, but what it gives us is an extensible and robust mechanism for managing network devices. The NETCONF protocol operations are realized as remote procedure calls (RPCs). It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. NETCONF is defined in RFC 6241 which describes it as follows: This post summarizes where my head is at on this subject. I've had some great discussion with the OpenDaylight OVSDB team around NETCONF, YANG, RESTCONF and what network operations will look like in an SDN world.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |