get_started_experiment1
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
get_started_experiment1 [2015/06/17 16:07] Randy Levensalor [Overview] |
get_started_experiment1 [2015/09/21 15:59] (current) Sai Sindhur Malleni [Overview] |
||
|---|---|---|---|
| Line 35: | 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 ===== | ||
| Line 50: | 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 116: | 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 128: | 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.1434557260.txt.gz · Last modified: 2015/06/17 16:07 by Randy Levensalor
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
