Open Stack

On 17 June 2013 06:46, Jay Pipes <jaypipes at gmail.com> wrote:
>
> Ah, but there's a catch. SRV records don't contain a number of pieces of
> information that the service catalog supplies...
>
> The service type -- is it a compute service? an identity service? a volume
> service? The only thing the SRV record gives you is "it's a service"... you
> then have to do a further query (and assume some sort of standard
> information discovery format) on the URI in order to determine what it is.
> Since all of our endpoints are TCP/IP, there is no way to use the protocol
> field of the SRV record to differentiate different service types. You would
> still need some sort of service catalog being served up from the URIs
> contained in the SRV record target field in order for the OpenStack clients
> to make sense of anything.

I thought the standard design pattern for that was zones.
say your cloud is cloud.example.com
so SRV for cloud.example.com would be keystone public
SRV for _compute._pub_endpoints.cloud.example.com -> compute public endpoint
SRV for _compute._priv_endpoints.cloud.example.com -> compute private
endpoint (and btw you can use split views to hide that from the
outside world)

SRV for _network._pub_endpoints.cloud.example.com -> openstack network
public endpoint
etc.


E.g. known, solved thing, nothing to see here, move along.

-Rob

-- 
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Cloud Services