This document discusses XOS and its role in OpenCORD. It describes how XOS uses a synchronizer to manage state changes to data models and synchronize them with OpenStack. Core components of OpenCORD include OpenStack, ONOS, XOS, and OCP. OpenCORD projects on GitHub include platform installation tools, XOS, MaaS, and services like AAA and Voltha. XOS assembles services using separate containers for the database, webserver, and synchronizer. TOSCA is used to describe application topologies and orchestrate operations across cloud providers.
This document discusses CORD (Central Office Re-architecture as a DC) and its components. CORD combines SDN, NFV and cloud technologies to deliver services for telecommunications providers using open source software and commodity hardware. It discusses the requirements and types of CORD (M-CORD for mobile, E-CORD for enterprise, R-CORD for residential services). The core components that make up CORD are OpenStack for infrastructure, ONOS for control, and XOS as the service controller. XOS assembles and orchestrates the virtual network functions and services on top of the infrastructure and control layers.
This document discusses XOS and its role in OpenCORD. It describes how XOS uses a synchronizer to manage state changes to data models and synchronize them with OpenStack. Core components of OpenCORD include OpenStack, ONOS, XOS, and OCP. OpenCORD projects on GitHub include platform installation tools, XOS, MaaS, and services like AAA and Voltha. XOS assembles services using separate containers for the database, webserver, and synchronizer. TOSCA is used to describe application topologies and orchestrate operations across cloud providers.
This document discusses CORD (Central Office Re-architecture as a DC) and its components. CORD combines SDN, NFV and cloud technologies to deliver services for telecommunications providers using open source software and commodity hardware. It discusses the requirements and types of CORD (M-CORD for mobile, E-CORD for enterprise, R-CORD for residential services). The core components that make up CORD are OpenStack for infrastructure, ONOS for control, and XOS as the service controller. XOS assembles and orchestrates the virtual network functions and services on top of the infrastructure and control layers.
ONOS Raspberry Pi 蠍磯 螳覓朱Μ SDN れ 蟆 蟲豢螻 螳覦sangyun han
油
The document provides information about setting up an SDN testbed using ONOS and Raspberry Pi. It introduces ONOS, an open source SDN operating system, and provides details on installing and running a single ONOS instance. It also covers setting up and managing multiple ONOS instances in a distributed deployment. Finally, it introduces OpenVirteX, a network virtualization platform, and provides an overview of its key features and the installation process.
Introduction of ONOS and core technologysangyun han
油
This document provides an overview of ONOS (Open Network Operating System) including:
- ONOS is an open-source SDN controller created by ON.LAB to provide carriers with an SDN/NFV solution.
- It aims to be carrier-grade with high availability, scalability, and performance through a distributed architecture.
- ONOS uses southbound protocols like OpenFlow and Netconf to configure network elements while providing northbound APIs and applications.
YANG is a data modeling language used to model configuration and state data transported via the NETCONF protocol. It uses a tree structure and modular design to define data models. YANG models can be encoded in formats like XML or JSON and stored on network devices for configuration and state data.
The document discusses several network configuration protocols:
- NETCONF uses XML and RPC to install, manipulate, and delete configurations on network devices. It operates over SSH.
- YANG is a data modeling language used to define configuration and state data for NETCONF in XML format.
- RESTCONF provides RESTful operations on NETCONF datastores containing YANG data, using HTTP.