Go to file

Matt Thompson fda42ebd9a Use upper-constraints file in developer mode

Last week, keystone was failing to install in developer mode due to us
not specifying upper constraints.  This was due to an upcapped version
of pysaml2 being installed which is causing problems.  This commit first
clones the requirements repo and then uses the upper constraints file
when installing packages.

Note that we only update pip_install_options when in developer mode if
the constraints aren't already set.  This is because in developer mode
you could have a container with multiple services running on it and the
pip_install_options fact would get updated when already set, resulting
in pip failing to install packages.

Change-Id: I270d7a37541d497ee0e1a576d5fda6f38dd2cb4c
Partial-Bug: #1553960

2016-03-14 15:14:16 +00:00

defaults

Use upper-constraints file in developer mode

2016-03-14 15:14:16 +00:00

doc

[DOCS] Cleanup the role docs for consistency and clarity

2016-03-07 17:03:49 -05:00

handlers

Fix glance_nfs_client setting

2015-07-23 00:28:19 +00:00

README.rst

OpenStack-Ansible Glance

tags: openstack, glance, cloud, ansible
category: *nix

This Ansible role installs and configures OpenStack glance and glance registry.

This role will install the following Upstart services:

glance-api
glance-registry

- name: Install glance server
  hosts: glance_all
  user: root
  roles:
    - { role: "os_glance", tags: [ "os-glance" ] }
  vars:
    external_lb_vip_address: 172.16.24.1
    internal_lb_vip_address: 192.168.0.1
    glance_galera_address: "{{ internal_lb_vip_address }}"