OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|1 month ago|
|deployment_scripts/puppet||2 months ago|
|repositories||2 years ago|
|.gitreview||1 month ago|
|LICENSE||3 years ago|
|README.md||2 months ago|
|components.yaml||2 years ago|
|deployment_tasks.yaml||2 years ago|
|environment_config.yaml||2 years ago|
|metadata.yaml||2 months ago|
|node_roles.yaml||3 years ago|
|pre_build_hook||2 years ago|
|tasks.yaml||2 years ago|
|volumes.yaml||3 years ago|
This plugin will install Open Network Operating System (ONOS) controller, which is a typical SDN controller, and set it as a manager of ovs.
Log in Fuel Master and clone GIT repository of fuel-plugin-onos from openstack:
git clone -b Mitaka https://git.openstack.org/openstack/fuel-plugin-onos
Preparing an environment for plugin development by three easy steps:
A. Install the standard Linux development tools.
For Ubuntu 14.04 LTS, run:
sudo apt-get install createrepo rpm dpkg-dev
For Centos 6.5, run:
yum install createrepo rpm rpm-build dpkg-devel
B. Install the Fuel Plugin Builder. To do that, you should first get pip:
C. Then, install Fuel Plugin Builder (fpb) itself:
pip install fuel-plugin-builder
Build ONOS plugin for fuel:
fpb --build fuel-plugin-onos/
The onos rpm will be built in the folder of fuel-plugin-onos.
Install the onos plugin:
fuel plugins --install onos*.rpm
Check if you successfully install the plugin:
fuel plugins id | name | version | package_version ---|--------|---------|---------------- 1 | onos | 0.9.0 | 4.0.0
Check if the plugin is enabled on the settings table.
Notice: Step 1-4 aren’t limitted with the environment of master, you can also make it everywhere, but after the rpm is made, you should copy it to the master. In addition, the info of a new plugin at settings table can only be ready when a new environment is created.
All described actions below are described from a Fuel GUI provisioning perspective.
Create a new environment.
Select ‘onos plugin’ on Settings tab. If you want to try sfc functions, select SFC features as well.
Select a node with role ‘onos’
Click ‘Deploy changes’ to enable nodes with ONOSFW.
In order to run ONOS, the following are required:
Notice: In case of version problems, the onos rpm uses jdk and onos packages that have been tested.
Web UI is recommended for ONOS controller with tuitive information of topo, devices and etc. For that purpose, IP address of horizon should be ready, which can be found in fuel master after successful deployment. The web will run into the log page after inputing the path, username and password are both ‘karaf’. Now enjot ONOS!
Web UI: http://horizon_ip:8181/onos/ui
CLI is capable of more diverse functionality by running /opt/onos/bin/onos. More about CLI can be found in The ONOS CLI.
Interested in contributing? Follow Fuel Plugins Development.
Wu Wenbin email@example.com