Roberto Polli

@markllama @tomassedovic exposing masters and infra gives access to port 10250 too. Is that fine? Thx++, R.

@jeremyeder iirc now those templates require an external dns and don't deploy one anymore.

@javierpena seems it's in the docs. Worth closing?

1- from where do you run this command? 2- you need an exernal DNS to run openshift-on-openstack. afaik these templates don't install a DNS on the loadbalancer no more.

Which is the output of ``` bastion# grep -r dns /var/log/* ``` What's the 192.168.0.6 node? What's the address of your DNS?

@bartpved thx++! I implemented a different solution adding a PoolMember in every master in master.yaml. I saw you used %index%. Your solution seems cool as you didn't modify master.yaml

@bartpved I just added update_dns support for LBaaS. Check #330. Feedback welcome!

@bartpved I'm adding a lbaas configuration for the wildcard domain too (balancing nodes). Would you do it in the same lbaas.yaml or in a different one?

To me it worked nicely. I just modified: - the LB to point to the fixed_network avoiding to passing twice thru the external_network - removed from openshift.yaml all lbaasv1 staff...

Could this be implemented for LBaaS too triggering a SoftwareDeployment on the bastion node?