Problem : Access Horizon without Fuel node
Hi,
I've deployed Mirantis kilo release on VirtualBox. 2 Controllers (not 3 because of resources) and one Compute.
When I remove the master node in the Mirantis kilo release, I can'ping the public ip to access Horizon or even the API of each component.
The access comes up just when I get the master node up, then I can ping it. I really don't understand, HAProxy seems to work and is well configured but it's like if the virtual ip cannot exist without the fuel master node.
I had IceHoust and so, I tried to see the difference of configuration and I have move the snapshots of Icehouse to another computer. Surprise, surprise, I can't also not to access the public ip anymore, like there was a configuration on the computer I miss. That doesn't make any senses.
EDIT :
--
That seems that it is related to the Pacemaker component installed. In IceHouse, that's because it doesn't start any more but when I compare the configuration, that's very strange. It seems that Mirantis has changed his configuration with PaceMaker sice IceHouse.
Now, I can see that the virtual public ip needs to pass through the gateway which represents the ip of the fuel master. Why ? I would like to know because that doesn't make any senses for me to have this behaviour.
--
Any ideas ?
Regards,
Nicolas
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask Nicolas Deixonne for more information if necessary.