prehistoric-systems/scottslowe-learning-tools
1
0
Fork 0
mirror of https://codeberg.org/scottslowe/learning-tools.git synced 2026-03-11 09:04:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
scottslowe-learning-tools/ovn
History
Scott S. Lowe 21df937172 Add final changes for working OVN learning environment 
Add README.md with instructions on how to use the environment. Add final changes to the Vagrantfile and Ansible provisioning script. Add Jinja2 template for final setup script.

Signed-off-by: Scott S. Lowe <scott.lowe@scottlowe.org>
2016-12-02 17:52:38 -07:00
..
ansible.cfg Commit initial Ansible files 2016-12-01 20:02:03 -07:00
machines.yml Commit working files for OVN environment 2016-12-01 19:47:56 -07:00
provision.yml Add final changes for working OVN learning environment 2016-12-02 17:52:38 -07:00
README.md Add final changes for working OVN learning environment 2016-12-02 17:52:38 -07:00
setup.sh.j2 Add final changes for working OVN learning environment 2016-12-02 17:52:38 -07:00
Vagrantfile Add final changes for working OVN learning environment 2016-12-02 17:52:38 -07:00

README.md

Open Virtual Network (OVN)

These files were created to allow users to use Vagrant (http://www.vagrantup.com) to quickly and easily spin up an environment to test Open Virtual Network (OVN), a part of the Open vSwitch project.

Contents

  • ansible.cfg: This is an Ansible configuration file that instructs Ansible to use the "vagrant" remote user, and to use Vagrant's built-in Ansible inventory.

  • machines.yml: This YAML file contains a list of VM definitions and associated configuration data. It is referenced by Vagrantfile when Vagrant instantiates the VMs.

  • provision.yml: This Ansible playbook installs the OVS/OVN components on each Vagrant machine. It's called automatically by Vagrant.

  • README.md: This file you're currently reading.

  • setup.sh.j2: This Jinja2 template is used by Ansible to build a customized OVS/OVN configuration script for each Vagrant machine. The shell script created by this template is placed by Ansible in /home/vagrant/setup.sh.

  • Vagrantfile: This file is used by Vagrant to spin up the virtual machines. This file is fairly extensively commented to help explain what's happening. You should be able to use this file unchanged; all the VM configuration options are stored outside this file.

Instructions

These instructions assume you've already installed Vagrant, your back-end virtualization provider (such as VMware Fusion or VirtualBox), and any necessary plugins (such as the Vagrant VMware plugin). Please refer to the documentation for those products for more information on installation or configuration.

  1. Use vagrant box add to add an Ubuntu 16.04 box to your system. The "bento/ubuntu-16.04" box is very good for both VirtualBox and VMware Fusion/Workstation. (Note that the "ubuntu/xenial64" box for VirtualBox is currently broken under Vagrant.)

  2. Edit the machines.yml file to ensure the box you downloaded in step 1 is specified on the "box:" sections of this file. Specify the name of a VMware-formatted box on the "vmw:" line; place the name of a VirtualBox-formatted box on the "vb:" line.

  3. Run vagrant up to have Vagrant instantiate the three machines configured by default in this environment, and provision them using Ansible. (Note you'll need Ansible installed locally on the system where you're running vagrant up.)

  4. Use vagrant ssh ovn-01 to log into the first system. Run sudo ./setup.sh to perform final configuration steps for OVS/OVN.

  5. Repeat step #4 with ovn-02 and ovn-03.

You now have a three-node system running OVN. The OVN central components are running on "ovn-01".

Enjoy!