openstack-ansible/playbooks/roles/pip_lock_down
Kevin Carter cfeec1cc3a adds the config_template to pip_lock_down
The change modifies the pip_lock_down template tasks such that it's now
using the config_template action plugin. This change will make so that
config files can be dynamically updated, by a deployer, at run time,
without requiring the need to modify the in tree templates or defaults.

Partially implements: blueprint tunable-openstack-configuration

Change-Id: I620b7f599a9e41f5fe38a2d038b53cfa227c1d55
2015-09-21 11:14:43 +00:00
..
defaults adds the config_template to pip_lock_down 2015-09-21 11:14:43 +00:00
files Convert existing roles into galaxy roles 2015-02-18 10:56:25 +00:00
meta Convert existing roles into galaxy roles 2015-02-18 10:56:25 +00:00
tasks adds the config_template to pip_lock_down 2015-09-21 11:14:43 +00:00
templates Changed link lineinfile to template 2015-06-24 22:11:12 -05:00
CONTRIBUTING.rst Cleaning up doc8 violations. 2015-06-10 02:09:18 +00:00
LICENSE Convert existing roles into galaxy roles 2015-02-18 10:56:25 +00:00
README.rst Cleaning up doc8 violations. 2015-06-10 02:09:18 +00:00

OpenStack pip lockdown

tags

openstack, pip, lockdown, cloud, ansible

category

*nix

Role to lock pip down to a particular links repo. This will create a .pip.conf which will ensure that the only python packages installed when using pip are from a known repository of packages.

- name: Basic lxc host setup
  hosts: host_group
  user: root
  roles:
    - { role: "pip_lock_down", tags: [ "pip-lock-down" ] }
  vars:
    pip_links:
      name: openstack-release
      link: https://openstack-hostname.something/python_packages/master

This was intended for use with a repository built from the repo role.