Application delivery via .oar files

205 views
Skip to first unread message

Thomas Vachuska

unread,
Apr 16, 2015, 5:46:46 PM4/16/15
to onos-dev
Hi everyone,

This is to let you know that a change was made to how the builtin and sample applications are packaged and staged for installation. The applications are now delivered via a .oar file (ONOS Application aRchive). This ZIP file is produced automatically by the build process using the app.xml file in the module base directory and includes the app.xml, features.xml and any bundle artifacts contributed/needed by the application. The oar file is also installed into maven repository, which means upon release, they will also be available in the Maven central.

Part of this change means that the overall features.xml file no longer defines any application specific features. Instead, each application can either define its own set of features in feature.xml file (also in the module base directory) or if the application is a single-bundle one, the features.xml file will be automatically generated to include the project bundle.

The shell utilities onos-setup-karaf and onos-package both stage all *.oar files in the apps directory to make them available as pre-installed applications at run-time. As before, ONOS_APPS variable can be used at onos-setup-karaf/onos-install/onos-configure time to tailor which apps will be marked as activated.

A new CLI has been added ‘app install <url>’ which allows installation of apps from a URL via command-line. Wiki will be updated shortly with these (and more) details.
The onos-app shell utility & REST API continues to work as it did before.

Cheers...

Thomas

Charles Min-Cheng Chan

unread,
Apr 17, 2015, 7:47:03 AM4/17/15
to Thomas Vachuska, onos-dev
Thomas,

The onos-app script does not work properly.

The usage says
usage: onos-app {install|install!} <app-file>
but it should be
usage: onos-app <node IP> {install|install!} <app-file>

I guess you want to fetch node IP automatically by node=${1:-$OCI}
But if we don't input the node IP, the following check will fail.
[ $# -lt 3 -o ! -f $app ] && usage

As a result, I can only see the usage information when I input
onos-app install app.xml

Please check.

Also, we might want to add onos-app list command into the usage information.

Thanks,
Charles

--
Charles Min-Cheng Chan 詹珉誠
Ph.D. Candidate, National Chiao Tung University

--
You received this message because you are subscribed to the Google Groups "ONOS Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to onos-dev+u...@onosproject.org.
To post to this group, send email to onos...@onosproject.org.
Visit this group at http://groups.google.com/a/onosproject.org/group/onos-dev/.
To view this discussion on the web visit https://groups.google.com/a/onosproject.org/d/msgid/onos-dev/277FFD20-9673-4D99-A823-DB1627E12F94%40onlab.us.

Thomas Vachuska

unread,
Apr 17, 2015, 12:17:52 PM4/17/15
to Charles Min-Cheng Chan, onos-dev
Good catch and a good suggestion.

Thomas
Reply all
Reply to author
Forward
0 new messages