I did some experiments. And it seems easy. I only replaced all the foo.com specified in /etc/openshift of the broker machine.
And now rhc works. If I create a new app, its url is app-mypaas.bar.com as expected. Interestingly, rhc ssh app reports it is connecting app-mypaas.bar.comin, while in the ssh session I saw I am on app-mypaas.foo.com J I guess I need to do similar hacking on the node machine to make it consistent…
Although it seems work, I am not sure if there are any potential issues doing this way.
There is no good way to do this at the moment. The cloud domain is used and possibly stored inside a lot to gear and cartridge configurations as well as DNS.
Changing the cloud domain using puppet will work for new applications but will cause existing applications to break.
Is there a reason you need to change the cloud domain? perhaps we can think of an alternative?
On Sep 11, 2013, at 1:02 AM, "Yan, Shoumeng" <shoumeng yan intel com> wrote:
To be accurate, I meant my CLOUD_DOMAIN="foo.com".
Just want to check the list, before I do something dangerous.