Go to file

Markos Chandras c180998193 playbooks: roles: bifrost-ironic-install: Retry failed PXE downloads

Downloading PXE files could fail for various reasons which may not
always be valid so try to workaround that by simply trying to get the
files a few more times before giving up. This aims to workaround the
following issue which appears from time to time in Jenkins builds
even though the remote certificate and the host's software remain the
same.

"Failed to validate the SSL certificate for boot.ipxe.org:443. Make sure
your managed systems have a valid CA certificate installed. You can use
validate_certs=False if you do not need to confirm the servers identity
but this is unsafe and not recommended. Paths checked for this platform:
/etc/ssl/certs, /etc/pki/ca-trust/extracted/pem, /etc/pki/tls/certs,
/usr/share/ca-certificates/cacert.org, /etc/ansible"

However, it may also assist with general networking issues as well.

Change-Id: Ia2351ed2c7f1dfe26c17770250d150f26432086b

2017-03-07 01:57:41 +00:00

bifrost

Don't assume 'dhcp' if node_network_data set

2017-01-13 16:17:05 +00:00

doc/source

Documentation cleanup

2017-03-02 18:55:41 +00:00

playbooks

playbooks: roles: bifrost-ironic-install: Retry failed PXE downloads

2017-03-07 01:57:41 +00:00

releasenotes

Update release note index for ocata

2017-02-14 10:41:54 -08:00

scripts

scripts: test-bifrost.sh: Initialize the ZUUL_BRANCH variable

2017-03-02 00:41:48 +00:00

tools

Add instructions to setup ip on provisiong on virsh

2016-11-08 17:09:26 +01:00

.gitignore

Always install Ansible with pip

2017-02-13 13:10:54 +02:00

.gitreview

Add .gitreview file

2015-05-25 13:52:46 +00:00

.mailmap

Add cookiecutter-generated files for project

2015-06-10 08:40:19 -07:00

.testr.conf

Add the rest of the cookiecutter-generated files for testing

2015-06-24 16:09:08 -07:00

babel.cfg

Add cookiecutter-generated files for project

2015-06-10 08:40:19 -07:00

CONTRIBUTING.rst

Update CONTRIBUTING.rst to cover conditionals

2015-12-22 15:33:08 -05:00

env-vars

Set OS_AUTH_TOKEN to dummy string, instead of empty space

2016-08-15 12:21:53 +00:00

HACKING.rst

Fix HACKING.rst and canary test for merges

2015-09-08 21:49:02 +00:00

LICENSE

Adding LICENSE file

2015-04-16 15:58:23 -04:00

README.rst

Fix README.rst

2017-03-06 10:50:54 +00:00

README.vagrant.rst

Typo fix: enviroment => environment

2017-01-23 13:19:11 +07:00

requirements.txt

Updated from global requirements

2017-03-02 23:53:04 +00:00

setup.cfg

Update home page link in cfg file

2016-09-20 14:25:34 +05:30

setup.py

Updated from global requirements

2017-03-02 23:53:04 +00:00

test-requirements.txt

Updated from global requirements

2017-03-02 23:53:04 +00:00

tox.ini

Ignore upstream Ansible modules in pep8 tests

2017-02-16 10:20:38 +00:00

troubleshooting.rst

TrivialFix: Fix typo in the RST file

2016-09-30 10:41:43 +07:00

README.vagrant.rst

Vagrant support for developers

Bifrost vagrant file for developers can be found in the tools/vagrant_dev_env directory. Running vagrant up from within this folder will bring up an Ubuntu Trusty box with Bifrost installed.

By default, the VM will have three interfaces:

eth0 - connected to a NAT network
eth1 - connected to Host-only network named: vboxnet1
eth2 - bridged - adapter must be set in Vagrantfile

Walkthrough done on OS X

Setup vagrant by:

Installing git
Installing virtualbox
Installing vagrant
Installing ansible

Configure Vagrant with the correct box:

vagrant box add ubuntu/trusty64

Clone bifrost repo:

git clone https://github.com/openstack/bifrost.git

Change into the bifrost directory:

cd bifrost/tools/vagrant_dev_env

Edit the Vagrantfile:

Change the bifrost.vm.network public_network value to a valid network interface to allow Bare Metal connectivity
Change public_key to correct key name
Change network_interface to match your needs

Boot the VM with:

vagrant up

Installation Options

Ansible is installed within the VM directly from source or from the path set by ANSIBLE_GIT_URL. You can modify the path of installation by setting ANSIBLE_INSTALL_ROOT environment variable. The default value is /opt/stack. When set in the host, this variable will also be set as an environment variable inside the VM for use by test scripts.

Note:

Only the ansible installation path is configurable at this point using the environment variable. All other dependencies will still continue to cloned under /opt/stack.