In the other day, there were questions about to migrate high availability solution into OpenStack.

With that context, there is no question to run the critical pacemaker and corosync processes inside the cloud. There is no difference between VMs and bare-metals in regarding to the dependency management system for both systemd and pacemaker, which is quit different than the situation of the container world. However,

  • How about the fencing mechanism?
  • How about the shared VIP?

They are small but critical components for every HA cluster. fence_openstack is the one I am going to investigate. Along with that, to use nova and keystone inside openstack cloud be very interesting experience, together with the fun of networking techniques inside the cloud environment.

With that, I tend to build up such solution by using existent SUSE products, namely,

  • SUSE Linux Enterprise Server 12 SP3
  • SUSE High Availability Extention 12 SP3
  • SUSE Public Cloud 12 SP3
  • SUSE Openstack Cloud 8

Looking for mad skills in:

Nothing? Add some keywords!

This project is part of:

Hack Week 18


Comments

  • zzhou
    5 months ago by zzhou | Reply

    The short summary:

    • fence_openstack works like the charm with the help from nova and keystone clients.
    • Virtual IP inside VM works very well with the single public floating IP by taking advantage of --allowed-address-pairs.

    Yet to recap the detailed steps, probably a blog.

    • zzhou
      3 months ago by zzhou | Reply

      It appears there is a resource-agent, namely, openstack-floating-ip, and makes sense for the next hackweek to continue ;)

Similar Projects

This project is one of its kind!