OpenConfig

OpenConfig
Name	OpenConfig
Type	Industry consortium / data modeling initiative
Founded	2016
Focus	Network telemetry and configuration models
Website	(omitted)

OpenConfig

OpenConfig is an industry initiative to develop vendor-neutral, model-driven telemetry and configuration models for network infrastructure. It seeks to harmonize the work of network operators and vendors—bringing together contributors from Google, Facebook, Microsoft, AT&T, Verizon and NTT—to produce shared YANG models and best practices that integrate with orchestration systems such as Ansible, Chef (software), Puppet and SaltStack. The effort aligns with standards activity at organizations like the IETF, IEEE, and ETSI while interfacing with vendor ecosystems including Cisco Systems, Juniper Networks, Arista Networks and Huawei.

Overview

OpenConfig provides a set of vendor-neutral data models and guidance for streaming telemetry, configuration, and operational state targeting routers, switches, and optical systems. The project emphasizes programmable interfaces used by platforms such as Linux, BIRD (routing daemon), and FRRouting while complementing control-plane projects like BGP implementations and routing suites from Cisco IOS XR, Juniper Junos, and Arista EOS. Operators use OpenConfig alongside management systems from IBM and Hewlett Packard Enterprise and cloud providers including Amazon Web Services, Google Cloud Platform, and Microsoft Azure to achieve consistent multi-vendor automation.

History and Governance

OpenConfig originated in multi-operator collaboration involving engineering teams from Google, Facebook, LinkedIn, Netflix, and Microsoft to address shortcomings in SNMP-era telemetry. It evolved through vendor engagement with Cisco Systems, Juniper Networks, Arista Networks, Huawei, and Ciena. Governance combines operator steering, vendor implementation, and community contributions modeled after collaboration seen in Linux Foundation projects and IETF working groups. Decision-making reflects operator requirements similar to processes used in ONAP, OpenStack, and Kubernetes communities; technical contributions often mirror practices from projects like OpenDaylight and FD.io.

Data Models and YANG Schema

The core deliverable is a suite of YANG models covering interfaces, routing protocols, telemetry, and operational state for devices from vendors such as Cisco Systems, Juniper Networks, Arista Networks, and Huawei. Models include representations for BGP, OSPF, IS-IS, EVPN, and MPLS constructs, interoperating with control-plane implementations like Quagga and FRRouting. OpenConfig models integrate with time-series collectors and analytics tools such as Prometheus, InfluxDB, and Grafana and align with streaming protocols including gNMI, gRPC, and NETCONF. The schema work references standardization patterns from IETF documents and tooling used in pyang and yanglint validation workflows.

Implementation and Tooling

Implementations appear across network OS releases from Cisco IOS XR, Juniper Junos, and Arista EOS to open-source platforms like FRRouting and SONiC. Tooling integrates with orchestration and CI systems including Jenkins, GitHub Actions, GitLab CI/CD, and Ansible Tower. Telemetry pipelines leverage collectors and brokers such as Telegraf, Fluentd, Kafka, and RabbitMQ and processing backends like Apache Flink, Apache Spark, and Elasticsearch. SDKs and client libraries in Go (programming language), Python (programming language), Java, and C++ support automation frameworks used by teams at Google, Facebook, and Amazon Web Services.

Adoption and Industry Use Cases

OpenConfig is adopted for intent-based networking, telemetry-driven network assurance, and scale-out data center fabrics operated by companies including Google, Facebook, Microsoft, Amazon, AT&T, and Verizon. Use cases span fiber-optic transport managed with gear from Ciena and Infinera to campus and WAN designs using devices from Cisco Systems, Juniper Networks, and Arista Networks. The models enable features in NFV deployments coordinated with OpenStack and orchestration in Kubernetes-backed edge computing projects. Enterprises and service providers apply OpenConfig in scenarios similar to those addressed by NetOps transformation programs, integrating with analytics vendors like Splunk and Dynatrace.

Security and Operational Considerations

Operational deployment raises security and compliance considerations familiar to operators working with NIST frameworks, ISO/IEC 27001 standards, and regulatory regimes involving FCC-regulated carriers. Secure transport for model-driven interfaces leverages TLS and mutual authentication approaches adopted across gNMI and NETCONF deployments, interoperating with identity systems like OAuth 2.0 and X.509 PKI. Operational tooling must address auditability and change control via systems such as Git and deployment pipelines including Jenkins and GitLab CI/CD. Monitoring and incident response workflows borrow playbooks and methodologies from ITIL and SRE practices developed at organizations like Google and Netflix.

Category:Network management