openstack/openstack-ansible
Code Issues Proposed changes
a47ca31221
openstack-ansible/playbooks/roles/pip_lock_down
History
kevin a4179512bc Changed link lineinfile to template 
This change ensures that all link files created are built from a template
rather than using the lineinfile module which will result in multiple entries
per file. While these multiple entries do not break deployments they do create
a slower install / upgrade time.

Change-Id: I4fef53baf075c953ac73500e72f9388f7ccfa2a0
Closes-Bug: #1468587
2015-06-24 22:11:12 -05:00
..
defaults Convert existing roles into galaxy roles 2015-02-18 10:56:25 +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 Changed link lineinfile to template 2015-06-24 22:11:12 -05: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

README.rst

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.