XOS brings the Everything-as-a-Service (XaaS) organizing principle to the CORD architecture. In doing so, it addresses several of CORD's high-level design requirements, including a means to seamlessly integrate control plane (SDN) and data plane (NFV) based services; the ability to support both access services and conventional cloud services; support for multiple security domains; and the "end-to-end glue" needed to make CORD both extensible and controllable.
XOS is a self-contained component of CORD – it serves as the "Controller" for CORD as a whole. Although it originally had a life outside of CORD, it is not an independent open source project — it is managed under CORD's project governance.
To participate in the XOS project...
- Join the CORD team (#xos channel) on Slack.
For more information see:
- XOS: Modeling-as-a-Service.
- Describes XOS as a self-contained service that augments micro-service based cloud applications built around systems like Kubernetes.
- Beyond Micro-Services: CORD's Model Driven Design.
- Describes CORD’s model-driven design, and XOS's role as a service control plane layered on top of a collection of micro-services. (Slide Deck)
- Defining Models for CORD.
- Describes XOS support for defining and processing models.
- VTN and Service Composition.
- Describes CORD's model for service composition and the interaction between XOS and VTN to realize it.
- Security in CORD.
- A brief introduction to CORD's security architecture.
- Service Assembly and Composition in CORD.
- An architectural description of how CORD models functionality as the composition of scalable multi-tenant services. (Historical. Above documents make it partially obsolete.)