Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Cleaned up the page based on the wiki standardization project. Moved excess information to new Info page.
Tip

Welcome to the XOS & NEM Community wiki space. All information on this wiki is publicly accessible. If you would like to contribute to this space, you will need a CORD account: https://opencord.org/registration

Introduction

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 central part of NEM (Network Edge Mediator), which plays a role in both SEBA and COMAC. XOS is a stand-alone tool, with other use cases on the horizon (e.g., multi-cloud service mesh).

Read more about XOS and NEM.

Communication Channels

To participate in the XOS project...

...

  • Join the CORD team (#xos channel) on Slack.

For more information see:

  • XOS Guide.
    • Describes XOS support for defining and processing models.
  • 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.)

NEM: Network Edge Mediator

...

  • .

...

Image Removed

For more information on NEM, including the role XOS plays in NEM and the role NEM plays in SEBA, see the following presentations: