Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Email us if you’re stuck, think you’ve found a bug, or just want to send some feedback. Please have a look at the guidelines to learn how to efficiently submit a bug report.

...

You will need to acquire two files: a VirtualBox installer and the Tutorial VMthe latest Tutorial VM from the Download packages and tutorial VMs page. 

After you have downloaded VirtualBox, install it, then go to the next section to verify that the VM is working on your system. 

Amazon Instance for Deployment

We have hosted the AMI used in the tutorial in the Northern California and Oregon zones. It available as a "Community AMI" when you launch an instance in EC2 called: onos-tutorial-v2

Create Virtual Machine

Double-click on the downloaded tutorial zipfile. This will give you an OVF file. Open the OVF file, this will open virtual box with an import dialog. Make sure you provision your VM with 4GB of RAM and if possible 4 CPUs, if not 2 CPUs should be ok.

...

Click on import. When the import is finished start the VM and login using:

USERNAME: onosdistributed

PASSWORD: onosdistributed

Important Command Prompt Notes

...

indicates that you are in mininet.

Start up ONOS for the first time

Double-click the 'Reset' icon on the desktop. This cleans the environment and re-deploys ONOS in a 3 instance configuration.

Verifying that ONOS is deployed

...

 

Code Block
distributed@mininet-vm:~/onos-byon$ mci
[INFO] Scanning for projects...
...
[INFO] byon .............................................. SUCCESS [1.104s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6.719s
[INFO] Finished at: Fri Dec 12 14:28:16 PST 2014
[INFO] Final Memory: 30M/303M
[INFO] ------------------------------------------------------------------------
distributed@mininet-vm:~/onos-byon$

mci is an alias for mvn clean install. Now, that your project has successfully built your project let's push it up to the ONOS cluster..

Code Block
distributed@mininet-vm:~/onos-byon$ onos-app $OC1 install target/byon-1.2.0-SNAPSHOT1.oar
{"name":"org.onos.byon","id":3739,"version":"1.02.SNAPSHOT1",
"description":"Build Your Own Network App",
"origin":"Apps-R-Us LLC, Inc. GmbH","permissions":"[]",
"featuresRepo":"mvn:org.onos.byon/byon/1.2.0-SNAPSHOT1/xml/features","features":"[byon]",
"state":"INSTALLED"}

 

The onos-app command will take the oar file that is generated during the build and push it into the specified ONOS instance. The command can also activate the application if you replace install with install! as well as separately activate, deactivate, and uninstall the application. Every time you update your code you simply need to run onos-app $OC1 reinstall! target/byon-1.0-SNAPSHOT.org and the new application will be loaded and started in the remote ONOS instances.

...

First, you will need to compile byon again with mci and run onos-app $OC1 reinstall! target/byon-1.2.0-SNAPSHOT1.oar again to get your latest bundle loaded into the ONOS docker instances.

...