Have questions? Stuck? Please check our FAQ for some common questions and answers.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

The ONOS incubator tree is a place that allows contributors to add to the API and to the Core implementations of ONOS in a creative way and on their own time-line while making their interfaces/API exempt from the deprecation policy, meaning that the API can change from release to release. This incubator tree will not effect the main line ONOS deliverables, yet can be used as a showcase for new features and APIs.

The idea is to set up onos-incubator-api and onos-incubator-net|store modules, with a corresponding Java package namespace org.onosproject.incubator. This could be then viewed as a sandbox or a nursery of future core code. This will allow physical separation of such code for certain production environments, but at the same time will allow experimenters to treat this as part of the ONOS code.

This is in addition to the existing capability where apps can expose their own APIs that can be consumed by other parts of the app, or by other apps.

The following depicts the module dependencies. Note that no part of the onos-core should depend on onos-incubator-api or onos-app-*.

 

  • No labels