UI is not browsable by default in OVB

[Steve Baker]

The TripleO UI cannot be accessed in a new quickstart OVB deploy without extra port tunnelling steps. This raises the barrier to non-UI folk trying or developing the UI.

There are a few changes required for this, which will probably all be done in tripleo-quickstart
- apache should bind to the IP on the private network, not the provision network
- tripleo_ui_config.js should be generated with the IP of the undercloud floating IP
- the undercloud OVB security group should allow incoming TCP port 3000
- the end of the quickstart run should output the url to launch the UI

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/507969

[Dan Trainor (dtrainor)]

Just a note that as described, these type of changes will only affect non-SSL Undercloud deployments. In order to make this work with an SSL Undercloud, in addition to the above, we would need:

- haproxy should bind to the IP on the private network, not the provision network (443/tcp)
- tripleo_ui_config.js should be generated with the IP of the undercloud floating IP (whilst appending :443/<servicename> to the URI
- the undercloud OVB security group should allow incoming TCP port 443

[OpenStack Infra (hudson-openstack)]

Change abandoned by Sagi Shnaidman (<email address hidden>) on branch: master
Review: https://review.openstack.org/507969
Reason: According to TripleO policy of patch abandonment https://github.com/openstack/tripleo-specs/blob/master/specs/policy/patch-abandomment.rst, this patch is abandoned. If you would like to continue to work on it, please ask for restoration either on #tripleo in Freenode IRC, or openstack dev mailing list - <email address hidden> with [TripleO] in subject. Thanks.