message service is not accessible

[Qiming Teng]

The recent revision has made message service (zaqar) not accessible.
Haven't tried if using Profile will make any differences.
Knowing that Profile is going away, it may not worth trying at all.

The problem of migrating to the new config method is that not all services are by default registered. This may need some work. Previously, SDK will not complain that a service is not registered. It complains when users really want to establish a connection. I'm okay with changes to this behavior, but please do not mask out services because users didn't fill in the configuration. After all most of the information can be obtained from keystone service catalog already.

The problem with zaqar could be that the service is registering itself as 'messaging' service, however, the modules are located under 'message' directory.

[Monty Taylor (mordred)]

Yes - this is absolutely a bug. The underlying issue is that while we create proxy objects for each official type and then also add them to the connection for every alias so that both:

  conn.messaging.messages()

and

  conn.message.messages()

work ... the creation of the keystoneauth Adapter object is not honoring finding services by alias in the catalog.

https://review.openstack.org/#/c/544356/ should address this, although it needs a few more hours work before it'll be ready to land. Ultimately, that patch should be considered a workaround, and the actual place this should be solved is in keystoneauth ... https://review.openstack.org/#/c/484341/ is a patch that does that which needs to be re-done. However, this fix needs to be put in place and then backported to stable/queens in SDK since we can't get it fixed in keystoneauth for queens (is a new ksa feature)

[OpenStack Infra (hudson-openstack)]

Change abandoned by Qiming Teng (<email address hidden>) on branch: master
Review: https://review.openstack.org/543767