Go to file

kevin 54c18cd99f Compartmentalizing RabbitMQ

Presently all services use the single root virtual host within RabbitMQ
and while this is “OK” for small to mid sized deployments however it
would be better to divide services into logical resource groups within
RabbitMQ which will bring with it additional security. This change set
provides OSAD better compartmentalization of consumer services that use
RabbitMQ.

UpgradeImpact
DocImpact
Change-Id: I6f9d07522faf133f3c1c84a5b9046a55d5789e52
Implements: blueprint compartmentalize-rabbitmq

2015-09-11 11:08:50 -05:00

defaults

Compartmentalizing RabbitMQ

2015-09-11 11:08:50 -05:00

files

Harden our copy of Glance's policy

2015-05-06 13:08:20 +00:00

handlers

Fix glance_nfs_client setting

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

README.rst

OpenStack glance

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

Role to install glance and glance registry.

This role will install the following:

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 }}"