This section records high-level the plan of record, but is typically less detailed than information on the Development Mailing List. Also see bug reports and short-term feature requests filed at the GitHub Issue Tracker.
Separate subsystems into their own containers. For example, XOS and Postgress should run in separate containers. Synchronizers should also be isolated in their own containers. We also need to do some design work around how to best extend the data model schema.
Address XOS scalability and high availability. Both are a function of the underlying database solution.
Leverage OpenStack domains so XOS can run on autonomous OpenStack clusters.
Generalize Compute Instances to include both VMs and Containers.
Extend support for “subscribers” (and other “service users”) by taking advantage of external identity management systems; e.g., via OpenID.
Related to (5), revisit the XOS data model for users, roles, and privileges.
Improve UI programming environment, including (a) re-engineering xoslib to support Single Page Application, (b) re-factoring to support a Js StyleGuide, and (c) providing a view-generation tool.
Integrate Monitoring Service into XOS. The plan is to make OpenStack’s Ceilometer a first-class XOS service, including instrumentation of all software services.
Integrate ONOS into XOS. The plan is to make ONOS a first-class XOS service, including replacing the default OpenStack/Neutron networking support with ONOS.
XOS can be deployed on different hardware configurations and populated with different service portfolios. We expect the following deployment configurations to be based on the Burwell release.
Development: A minimal configuration used for development, with backend cloud resources provided by CloudLab. Corresponds to the environment described in Developer Guide. Available with the Burwell release.
Test: A configuration used used to run regression tests on the XOS core, with backend cloud resources provided by CloudLab. Available with the Burwell release.
CORD Development: A configuration used for CORD development. Includes vSG, ONOS, and minimal vOLT and vRouter. Leverages CloudLab servers rather than actual POD hardware. Avaiable by end of October 2015.
OpenCloud: Deployed across multiple Internet2 sites. Service portfolio includes OpenStack, EC2, Syndicate, and vCDN. Available by end of November 2015.
CORD POD: A configuration to be deployed on a CORD POD with OLT hardware support. Service portfolio includes OpenStack, ONOS, Ceilometer, vCDN, vOLT, vSG, and vRouter. Avaiable by end of December 2015.