There is two approaches.
1) You make public endpoints and horizon public. White IP, resolvable
FQDN for endpoints, etc.
2) You hide endpoints from user (boo... no api, no automation), but
expose horizon.
Second case: horizon will sits as middleware between 'internal' networks
where endpoints
I just recently joined a team in charge of implementing OpenStack deployment
which I'm trying to grasp the design of.
One problem I encountered is that the openstack environment is on a pretty
closed network and I need to use ssh
tunnelling to be able to access horizon, so I started to look into
