On 04/28/2014 10:05 PM, Jay Dobies wrote:
We may want to consider making use of Heat outputs for this.
This was my first thought as well. stack-show returns a JSON document
that would be easy enough to parse through instead of having it in two
places.
Rather than assuming hard coding, create
Excerpts from Jan Provaznik's message of 2014-05-05 01:10:56 -0700:
On 04/28/2014 10:05 PM, Jay Dobies wrote:
We may want to consider making use of Heat outputs for this.
This was my first thought as well. stack-show returns a JSON document
that would be easy enough to parse through
On 6 May 2014 06:13, Clint Byrum cl...@fewbar.com wrote:
Excerpts from Jan Provaznik's message of 2014-05-05 01:10:56 -0700:
On 04/28/2014 10:05 PM, Jay Dobies wrote:
We may want to consider making use of Heat outputs for this.
..
The output endpoint list would be quite long, it would have to
We may want to consider making use of Heat outputs for this.
This was my first thought as well. stack-show returns a JSON document
that would be easy enough to parse through instead of having it in two
places.
Rather than assuming hard coding, create an output on the overcloud
template
Hello,
I am somewhat hesitant to bring up the stunnel topic in this thread, but it
needs to be considered in that an endpoint naming solution and a certificate
creation/distribution solution needs to consider both the haproxy and stunnel
requirements because there are many similarities. I am
Excerpts from Jan Provazník's message of 2014-04-25 06:30:31 -0700:
Hello,
one of missing bits for running multiple control nodes in Overcloud is
setting up endpoints in Keystone to point to HAProxy which will listen
on a virtual IP and not-standard ports.
HAProxy ports are defined in
