On 6 May 2014 06:13, Clint Byrum 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 contain
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 thro
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
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 that
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 i
rdened stunnel proxy.
Regards,
Mark
-Original Message-
From: Jan Provazník [mailto:jprov...@redhat.com]
Sent: Friday, April 25, 2014 6:31 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [TripleO] HAProxy and Keystone setup (in Overcloud)
Hello,
one of missing bits for runn
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 heat template, e.g.:
haproxy:
nodes:
- name: control1
