Go to file

Pavlo Shchelokovskyy eb727f4a01 Allow installing Ansible from PyPI

As of Ansible v2.2 all the missing modules bifrost requires are included
in the pip-installable Ansible package.
Let's allow then for a possiibility for bifrost to install Ansible
directly from PyPI (into the system or in virtualenv) instead
of from cloned source repo.

This patsh first extracts the installation of binary/Python dependencies
and installation of Ansible itself from the "env-setup.sh" script to two
separate scripts "install-deps.sh" and "install-ansible-source.sh".

It also adds a third script "install-ansible-pip.sh" that is called when
environment variable ANSIBLE_FROM_PYPI is set to "True"
(default is "False" for backward compatibility).
It then looks up ANSIBLE_PIP_VERSION env variable (defaults to "2.2")
and pip-installs Ansible of that given version strictly.

Change-Id: Ia72e06d7bf127569d423fa521b8ddab87453809e

2016-12-05 15:17:06 +00:00

bifrost

Replace six.iteritems() with .items()

2016-11-22 19:47:39 +00:00

doc/source

Add initial keystone use documentation

2016-12-02 18:31:20 +00:00

playbooks

Ensure git_root folder exists

2016-12-05 14:38:26 +00:00

releasenotes

Adding keystone support to inspector config

2016-12-02 19:20:51 +00:00

scripts

Allow installing Ansible from PyPI

2016-12-05 15:17:06 +00:00

tools

Add instructions to setup ip on provisiong on virsh

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

.gitignore

Ignore Ansible retry files in .gitignore

2016-09-23 10:25:40 +01: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

openstack-common.conf

Add cookiecutter-generated files for project

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

README.rst

Config drive spec uses network_data.json

2016-12-02 15:59:17 +00:00

README.vagrant.rst

Make ansible installation directory configurable

2016-06-06 13:24:46 -07:00

requirements.txt

Updated from global requirements

2016-11-18 21:23:30 +00:00

setup.cfg

Update home page link in cfg file

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

setup.py

Sync from global requirements

2016-01-22 11:39:17 -05:00

test-requirements.txt

Updated from global requirements

2016-11-04 05:53:49 +00:00

tox.ini

Don't include openstack/common in flake8 exclude list

2016-10-31 04:10:08 +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 enviroment variable. All other dependencies will still continue to cloned under /opt/stack.