Glance service selection from ServiceCatalog when using keystone
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Medium
|
Stuart McLaren |
Bug Description
When glance receives a token from the keystone server it looks through the
returned json for a serviceName:
for service in resp_auth[
if service['name'] == 'glance':
We were in touch with the Keystone folks about this:
----------
You're correct, they should be looking at the type field. The name is purely an operator-specified, marketing name (I.e. At Rackspace we would call it "Cloud Servers").
Yes, the core openstack services are canonical. Any other services should be added as extensions (ex: "HP-dnsext:dns"). This is specified in the XSD contracts (but not enforced in JSON as
we don't have validation there…. Yet…
Thanks!
Z[iad]
-----------
the change would be something like:
--- a/glance/
+++ b/glance/
@@ -175,7 +175,7 @@ class KeystoneStrateg
# FIXME(sirp): for now just using the first endpoint we get back
# from the service catalog for glance, and using the public url.
for service in resp_auth[
- if service['name'] == 'glance':
+ if service['type'] == 'image-service':
else:
compare the equivalent swift bug: https:/
Changed in glance: | |
milestone: | essex-3 → essex-4 |
Changed in glance: | |
status: | Fix Committed → Fix Released |
Changed in glance: | |
milestone: | essex-4 → 2012.1 |
Note, that in the keystone source they seem to refer to glance
as both of type 'image' and 'image-service':
keystone/ keystone/ test/sampledata .py:
#6 Service Name:glance Type:image
('service', 'add', 'glance',
'image', 'OpenStack Image Service'),
keystone/ keystone/ content/ common/ xsd/services. xsd:
My guess is that 'image-service' is the right type?