Use Keystone internal endpoint instead of admin for services
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Fri, 10 Feb 2017 18:47:13 +0000 (20:47 +0200)
committerEmilien Macchi <emilien@redhat.com>
Tue, 14 Feb 2017 02:41:13 +0000 (02:41 +0000)
commitd1eb0bc0dc1955c70e262101d07d857a35682333
treedb3face0157edc0cee17434fff431b30e20103c0
parentfab8f5226376c62848fb73df8eddea398ef63be1
Use Keystone internal endpoint instead of admin for services

The admin endpoint is listening on the ctlplane network by default;
services should ideally be using the internal api network for this kind
of traffic, as the ctlplane network is mostly for provisioning. On the
other hand, the admin endpoint shouldn't be as relevant with services
switching to keystone v3.

Change-Id: I1213a83ef8693c1cca1d20de974f7949a801d9f1
23 files changed:
puppet/services/aodh-base.yaml
puppet/services/barbican-api.yaml
puppet/services/ceilometer-base.yaml
puppet/services/ceph-rgw.yaml
puppet/services/cinder-api.yaml
puppet/services/ec2-api.yaml
puppet/services/glance-api.yaml
puppet/services/gnocchi-api.yaml
puppet/services/heat-base.yaml
puppet/services/ironic-api.yaml
puppet/services/manila-api.yaml
puppet/services/manila-share.yaml
puppet/services/mistral-base.yaml
puppet/services/neutron-api.yaml
puppet/services/neutron-metadata.yaml
puppet/services/neutron-plugin-plumgrid.yaml
puppet/services/nova-api.yaml
puppet/services/nova-base.yaml
puppet/services/octavia-api.yaml
puppet/services/panko-base.yaml
puppet/services/sahara-base.yaml
puppet/services/swift-proxy.yaml
puppet/services/zaqar.yaml