Files

Kevin Carter 8e6dbd01c9 Convert existing roles into galaxy roles

This change implements the blueprint to convert all roles and plays into
a more generic setup, following upstream ansible best practices.

Items Changed:
* All tasks have tags.
* All roles use namespaced variables.
* All redundant tasks within a given play and role have been removed.
* All of the repetitive plays have been removed in-favor of a more
  simplistic approach. This change duplicates code within the roles but
  ensures that the roles only ever run within their own scope.
* All roles have been built using an ansible galaxy syntax.
* The `*requirement.txt` files have been reformatted follow upstream
  Openstack practices.
* Dynamically generated inventory is now more organized, this should assist
  anyone who may want or need to dive into the JSON blob that is created.
  In the inventory a properties field is used for items that customize containers
  within the inventory.
* The environment map has been modified to support additional host groups to
  enable the seperation of infrastructure pieces. While the old infra_hosts group
  will still work this change allows for groups to be divided up into seperate
  chunks; eg: deployment of a swift only stack.
* The LXC logic now exists within the plays.
* etc/openstack_deploy/user_variables.yml has all password/token
  variables extracted into the separate file
  etc/openstack_deploy/user_secrets.yml in order to allow seperate
  security settings on that file.

Items Excised:
* All of the roles have had the LXC logic removed from within them which
  should allow roles to be consumed outside of the `os-ansible-deployment`
  reference architecture.

Note:
* the directory rpc_deployment still exists and is presently pointed at plays
  containing a deprecation warning instructing the user to move to the standard
  playbooks directory.
* While all of the rackspace specific components and variables have been removed
  and or were refactored the repository still relies on an upstream mirror of
  Openstack built python files and container images. This upstream mirror is hosted
  at rackspace at "http://rpc-repo.rackspace.com" though this is
  not locked to and or tied to rackspace specific installations. This repository
  contains all of the needed code to create and/or clone your own mirror.

DocImpact
Co-Authored-By: Jesse Pretorius <jesse.pretorius@rackspace.co.uk>
Closes-Bug: #1403676
Implements: blueprint galaxy-roles
Change-Id: I03df3328b7655f0cc9e43ba83b02623d038d214e

2015-02-18 10:56:25 +00:00

holland.yml

Convert existing roles into galaxy roles

2015-02-18 10:56:25 +00:00

openstack_clients.yml

Convert existing roles into galaxy roles

2015-02-18 10:56:25 +00:00

openstack_other.yml

Convert existing roles into galaxy roles

2015-02-18 10:56:25 +00:00

openstack_services.yml

Convert existing roles into galaxy roles

2015-02-18 10:56:25 +00:00

python2_lxc.yml

Convert existing roles into galaxy roles

2015-02-18 10:56:25 +00:00

readme.rst

Convert existing roles into galaxy roles

2015-02-18 10:56:25 +00:00

turbolift.yml

Convert existing roles into galaxy roles

2015-02-18 10:56:25 +00:00

readme.rst

Packages built by python from git

date: 2014-09-01 09:57
tags: python, pip, wheel, lxc, openstack, cloud, ansible
category: *nix

Packages Downloads and Installable

Any and all packages that need to be installed for this repository to work should be specified here in the, repo_packages directory. The files in this directory are given to the python wheel builder for construction.

Inside these files all download-able objects such as tar-balls and random files should also be specified. While the packaging roles may not be used to process these links the stated purpose of this directory is to have anything that is "installable" in a single location with the goal to allow for easily manipulation of requirements as they change.

NOTICE on items in this file:

If you use anything in the "*._git_install_branch" field that is not a TAG make sure to leave an in-line comment as to "why".

For the sake of anyone else editing this file:

If you add clients to this file please do so in alphabetical order.
Every entry should be name spaced with the name of the client followed by an "_"

The basic structure of all of these files:

git_repo: string URI to the git repository to clone from.
git_fallback_repo: string URI to an alternative git repository to clone from when git_repo fails.
git_dest: string full path to place a cloned git repository. This will normally incorporate the repo_path variable for consistency purposes.
git_install_branch: string branch, tag or SHA of a git repository to clone into.
git_repo_plugins: list of hashes with keys: path, package | This is used to install additional packages which may be installable from the same base repository.