Add keystone service metadata for v3 client
V3 resources structure/resource relation are completely
different than in v2. This patch introduce metadata for
v3 resources stored in:
* keystone/client/v3/services/*
The new module/state in keystone to work with v3 only was introduced
by https://gerrit.mcp.mirantis.net/19529.
The change is fully backward compatible, as new resources will be
used only when keystone:client:resources:v3:enabled is set explicitly
to True.
Change-Id: I0f0e53dda29572987f221438394083590bb6a6e5
Related-Prod: PROD-19148
diff --git a/keystone/client/v3/service/congress.yml b/keystone/client/v3/service/congress.yml
new file mode 100644
index 0000000..db0085b
--- /dev/null
+++ b/keystone/client/v3/service/congress.yml
@@ -0,0 +1,33 @@
+parameters:
+ _param:
+ cluster_public_protocol: https
+ congress_service_protocol: http
+ keystone:
+ client:
+ resources:
+ v3:
+ users:
+ congress:
+ password: ${_param:keystone_congress_password}
+ email: ${_param:admin_email}
+ roles:
+ service_admin:
+ name: admin
+ project_id: service
+ services:
+ congress:
+ type: policy
+ description: Congress service
+ endpoints:
+ congress_public:
+ interface: 'public'
+ url: ${_param:cluster_public_protocol}://${_param:cluster_public_host}:1789/
+ region: ${_param:openstack_region}
+ congress_internal:
+ interface: 'internal'
+ url: ${_param:congress_service_protocol}://${_param:congress_service_host}:1789/
+ region: ${_param:openstack_region}
+ congress_admin:
+ interface: 'admin'
+ url: ${_param:congress_service_protocol}://${_param:congress_service_host}:1789/
+ region: ${_param:openstack_region}