User Tools

Site Tools


get_started_experiment1

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
get_started_experiment1 [2015/04/17 16:17]
Tim Rozet
get_started_experiment1 [2015/09/21 15:59] (current)
Sai Sindhur Malleni [Overview]
Line 9: Line 9:
 ===== Overview ===== ===== Overview =====
 OPNFV testing environment is achieved by using a handful of open source tools. ​ They are listed in order below in hierarchical order: OPNFV testing environment is achieved by using a handful of open source tools. ​ They are listed in order below in hierarchical order:
-  - Khaleesi - An Ansible framework responsible kicking off builds and tests+  - [[https://​www.vagrantup.com/​|Vagrant]] - Create and configure lightweight,​ reproducible,​ and portable development environments. 
 +  - [[https://​www.virtualbox.org/​|VirtualBox]] - A "​hosted"​ hypervisror used to host the Foreman node. 
 +  - [[https://​github.com/​trozet/​khaleesi|Khaleesi]] - An Ansible framework responsible kicking off builds and tests
   - Foreman - A baremetal/​virtual host management tool   - Foreman - A baremetal/​virtual host management tool
   - OPNFV/​Genesis - Puppet modules for invoking QuickStack ​     - OPNFV/​Genesis - Puppet modules for invoking QuickStack ​  
Line 16: Line 18:
   - [[https://​github.com/​dfarrell07/​puppet-opendaylight|OpenDaylight Puppet Module]] - Used to install OpenDaylight   - [[https://​github.com/​dfarrell07/​puppet-opendaylight|OpenDaylight Puppet Module]] - Used to install OpenDaylight
  
-The tools above work together to create the OPNFV target system, but they are not dependent on each other. ​ For example, instead of using Foreman you could just use another baremetal provisioner or simply use raw puppet to install OPNFV. ​ Khaleesi contains a playbook/​library to interact with Foreman, but is also used to provision other OpenStack clouds (rackspace, etc.) and is capable of using other OpenStack installers.+The tools above work together to create the OPNFV target system, but they are not dependent on each other. ​ For example, instead of using Foreman you could just use another baremetal provisioner or simply use raw puppet to install OPNFV. ​ Khaleesi contains a playbook/​library to interact with Foreman, but is also used to provision other OpenStack clouds (rackspace, etc.) and is capable of using other OpenStack installers.  The order below is based on the deploy.sh script running on a baremetal server.
  
 The order of operations for how these tools interact from start to end are as follows: The order of operations for how these tools interact from start to end are as follows:
 +
 +//Vagrant -> invokes VirtualBox to build a CentOS VM for Foreman node and a shared filesystem with the host ->//
  
 //Khaleesi -> invokes playbook to rebuild Foreman nodes ->// //Khaleesi -> invokes playbook to rebuild Foreman nodes ->//
Line 31: Line 35:
  
 //Khaleesi -> runs Tempest and provides results// //Khaleesi -> runs Tempest and provides results//
----- 
  
 +The below diagram presents a brief summary of the various components in the installer and interactions between them.
 +
 +{{:​flow.png|}}
 +
 +[[Foreman_QuickStack_Tool_Interaction| Click here for more details on tool interactions]]
 +----
 ===== QuickStack/​Foreman Video Recordings ===== ===== QuickStack/​Foreman Video Recordings =====
  
   * [[https://​bluejeans.com/​s/​88tD/​| OPNFV Puppet Module Walkthrough]]   * [[https://​bluejeans.com/​s/​88tD/​| OPNFV Puppet Module Walkthrough]]
   * [[https://​bluejeans.com/​s/​89gb/​| Foreman Walkthrough]]   * [[https://​bluejeans.com/​s/​89gb/​| Foreman Walkthrough]]
 +  * [[https://​bluejeans.com/​s/​8kkr/​| Khaleesi Walkthrough]]
  
  
Line 46: Line 56:
   - All servers will run CentOS 7.   - All servers will run CentOS 7.
   - Provisioning Host installed with [[http://​isoredirect.centos.org/​centos/​7/​isos/​x86_64/​|CentOS7]]   - Provisioning Host installed with [[http://​isoredirect.centos.org/​centos/​7/​isos/​x86_64/​|CentOS7]]
 +  - Provisioning Host is on Baremetal or a VM capable of running Virtualbox with hardware virtualization extensions (Intel VT-x or AMD-V) and Physical Address Extensions (PAE/NX) enabled.
   - Management network should not have a DHCP server if using Foreman. ​ Foreman will run its own DHCP server.   - Management network should not have a DHCP server if using Foreman. ​ Foreman will run its own DHCP server.
   - If behind a firewall in your network you will need to use a proxy. ​ This guide has instructions on how to setup the tools to use your network'​s proxy server.   - If behind a firewall in your network you will need to use a proxy. ​ This guide has instructions on how to setup the tools to use your network'​s proxy server.
 +  - If OpenStack is being deployed onto baremetal servers, the control and compute nodes need to be:
 +    * Powered off
 +    * Set to PXE boot from the ADMIN network
 +    * Boot with BIOS support (PXE with UEFI is [[http://​projects.theforeman.org/​issues/​431|not supported by Foreman]])
  
 ---- ----
- 
 ===== Topology ===== ===== Topology =====
 Below is the topology being used in Intel POD 1: Below is the topology being used in Intel POD 1:
Line 65: Line 79:
  
 ---- ----
 +
 +===== ISO Installation =====
 +[[ http://​artifacts.opnfv.org/​arno.2015.1.0/​foreman/​arno.2015.1.0.foreman.iso | Download the Foreman ISO ]]\\
 +The ISO is too large to fit on a DVD, use isohybrid and dd to write it to a usb stick:\\
 +//laptop$ isohybrid arno.2015.1.0.foreman.iso//​\\
 +//laptop$ sudo dd if=arno.2015.1.0.foreman.iso of=/dev/sdX bs=4M//\\
 +//laptop$ sync//\\
 +
 +*** important to replace /dev/sdX with the device of your USB stick ***
 +
 +Next boot off of the ISO and run the CentOS installation. The deploy.sh file referenced in the next section Automatic Deployment is installed with the ISO. Continue the OPNFV installation with the Automatic Deployment instructions.
  
 ===== Automatic Deployment ===== ===== Automatic Deployment =====
Line 73: Line 98:
 === Pre-Requisites === === Pre-Requisites ===
   * At least 5 baremetal servers, with 3 interfaces minimum, all connected to separate VLANs   * At least 5 baremetal servers, with 3 interfaces minimum, all connected to separate VLANs
 +  * DHCP should not be running in any VLAN.  Foreman will act as a DHCP server.
   * On the baremetal server that will be your JumpHost, you need to have the 3 interfaces configured with IP addresses   * On the baremetal server that will be your JumpHost, you need to have the 3 interfaces configured with IP addresses
   * On baremetal JumpHost you will need an RPM based linux (CentOS 7 will do) with the kernel up to date (yum update kernel) + at least 2GB of RAM   * On baremetal JumpHost you will need an RPM based linux (CentOS 7 will do) with the kernel up to date (yum update kernel) + at least 2GB of RAM
Line 100: Line 126:
  
 === Execution Instructions === === Execution Instructions ===
-On your JumpHost, clone 'git clone https://​github.com/​trozet/​bgs_vagrant.git' to as root to /root/+On your JumpHost, clone or download the bgs_vagrant Arno repo: 
 +                $ sudo -s 
 +                # cd /root 
 +                 
 +       To download the Arno release 
 +                # git clone -b v1.0 https://​github.com/​trozet/​bgs_vagrant.git 
 +                # cd bgs_vagrant 
 +                 
 +       ​Or ​to use the latest build 
 +                # git clone https://gerrit.opnfv.org/​gerrit/​genesis 
 +                # cd genesis/​foreman/​ci
  
 Edit opnvf_ksgen_settings.yml -> "​nodes"​ section: Edit opnvf_ksgen_settings.yml -> "​nodes"​ section:
Line 112: Line 148:
         For each controller node:         For each controller node:
                   * private_mac - change to mac_address of node's Private NIC (2nd NIC)                   * private_mac - change to mac_address of node's Private NIC (2nd NIC)
 +**Note:** Do not change the domain name of the nodes in opnvf_ksgen_settings.yml. ​ They must be in the opnfv.com domain.
  
-Execute deploy.sh via: ./deploy.sh -base_config ​/​root/​bgs_vagrant/​opnfv_ksgen_settings.yml+Execute deploy.sh via:  
 +        # ./deploy.sh -base_config ​$PWD/​opnfv_ksgen_settings.yml
get_started_experiment1.1429287437.txt.gz · Last modified: 2015/04/17 16:17 by Tim Rozet