On 6 May 2014 06:13, Clint Byrum <[email protected]> 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 >> full list of all possible services (even if a service is not included in >> an image) + SSL URI for each port. >> >> It might be better to get haproxy ports from template params (which >> should be available as stack.params) and define only virtual IP in >> stack.ouputs, then build endpoint URI in os-cloud-config. I'm not sure >> if we would have to change os-cloud-config for LBaaS or not. My first >> thought was that VIP and port are only bits which should vary, so >> resulting URI should be same in both cases. >> > > +1
I think outputs are good here, but indeed we should not be exposing the control plane innards: thats what the virtual IP is for - lets export that out of Heat, along with the port #, and thats it. -Rob -- Robert Collins <[email protected]> Distinguished Technologist HP Converged Cloud _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
