Defining more api endpoints.

asked 2014-06-11 01:29:29 -0500

Krist gravatar image


In Keystone one can define three different enpoints for each service. These are the publicurl, the internalturl and the adminurl. From what I understand all the command line tools first contact keystone to get an auth token and a list of service urls.

Now I have the following issue.

We want to offer a public cloud, and it needs to be visible to the world under different domain names.

For example the api's should be accessible using both:

We will use a load balancer/ssl off loader for this, and rewriting incoming urls is not a problem. However what we need is for keystone to offer a different service catalogue based on what url the client used to request it.

Basically a request to should result in urls being offered that are relative to and a requests to should result in url's being offered that are relative to .

Is this possible, and if so how do I do this?

edit retag flag offensive close merge delete


Doesn't anybody have an idea here? Has nobody before encountered the need to have different branded api endpoints?

Krist gravatar imageKrist ( 2014-06-12 06:19:36 -0500 )edit