Fuel for OpenStack

Can't get acces to Horizon on Mirantis 7

Asked by Gab_OS

Hello everyone,
I have deployed 2 Openstack nodes (1 controller 1 compute) on a vSphere enviorment, I mean, I have 3 virtual machines on vSphere and I deployed MOS from one (fuel master) to the others but using QEMU as hypervisor not ESXi.

The problem comes when fuel says that the deploy has been completed and give me the option to go to the dashboard, it gives me an ip of the Public range (10.20.127.0 in my case) that i can't reach from the outside, I only can reach that IP (which is the 10.20.127.11) inside the controller node, it has the br-ex setting up with the 10.20.127.12 ip address. From my pc I can reach the controller br-ex IP (10.20.127.12) and the gateway (10.20.127.254) but no the horizon dashboard's IP.

Is there any file where I can change the Horizon's IP address in order to be able to see the GUI? I've tried to add the 127.12 ip to the /etc/haproxy/015-horzion file but still can't get access.

Thanks for the help in advance

Gabriel

Question information

Language:
English Edit question
Status:
Expired
For:
Fuel for OpenStack Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Fabrizio Soppelsa (fsoppelsa) said : 		#1

Greetings Gabriel,
I don't know how your network is organized, but looks like a routing problem on your local host.
I can suggest to either add a new route through a controller (but commands vary and depend on your local operating system), or to setup a ssh tunnel. In this case, just create a couple of tunnels like:

ssh -L 80:10.20.127.11:80 root@controller
ssh -L 443:10.20.127.11:443 root@controller

And finally point your browser to localhost:80

Best regards,
Fabrizio
Mirantis Team

Revision history for this message
Gab_OS (gbrlperal) said : 		#2

Hi Fabrizio,
I think that is not the problem, because I can reach the 10.20.127.0/24 from my localhost. However, I've been trying to solving and I discovered that the horizon's ip is in the haproxy namespace, precisely in the b_public interface, I paste the outpout of the ip netstat exec haproxy ip command:

root@node-35:~# ip netns exec haproxy ip a

65: b_public: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 9a:e1:3b:ca:bb:05 brd ff:ff:ff:ff:ff:ff
    inet 10.20.127.12/24 scope global b_public
       valid_lft forever preferred_lft forever
    inet6 fe80::98e1:3bff:feca:bb05/64 scope link
       valid_lft forever preferred_lft forever

This interface has the IP that I'm trying to reach through the browser, and if I type the the ip netstat exec haproxy ip route command I can see that the default route is correct

root@node-35:~# ip netns exec haproxy ip r
default dev b_public scope link metric 10
default via 240.0.0.1 dev hapr-ns metric 10000
10.20.127.0/24 dev b_public proto kernel scope link src 10.20.127.12
10.20.127.0/24 via 240.0.0.1 dev hapr-ns metric 10000
172.2.240.0/24 via 240.0.0.1 dev hapr-ns metric 10000
172.2.253.0/24 dev b_management proto kernel scope link src 172.2.253.2
172.2.253.0/24 via 240.0.0.1 dev hapr-ns metric 10000
172.2.254.0/24 via 240.0.0.1 dev hapr-ns metric 10000
240.0.0.0/30 dev hapr-ns proto kernel scope link src 240.0.0.2

However i can't ping the default gateway, which is the 10.20.127.254 from the haproxy namespace, and I think that is there where the problem is, but the routes seem to be set up in the correct way.

I don't know what else should i do.

P.S: I know that I put the 10.20.127.12 as horizon ip now, but I reset the enviroment and deployed again and that was the IP that Fuel set up.

Best regards:
Gabriel

Revision history for this message
Launchpad Janitor (janitor) said : 		#3

This question was expired because it remained in the 'Open' state without activity for the last 15 days.