Idea is to prepare some advanced template examples for Heat orchestration in OpenStack, which will show: - how HA for VM guests can be used - how auto-scaling works

This following presentation from last OpenStack summit is explaining all problems with that: https://www.openstack.org/assets/presentation-media/ATLOpenStackSummit.HighAvailability.pdf https://www.youtube.com/watch?v=mdFOuwUg6js

Repository where the project is developed:

https://github.com/mjura/heat-templates/blob/hackweek/cfn/SLES11/SingleVMHA.template

Looking for hackers with the skills:

openstack ha

This project is part of:

Hack Week 11

Activity

  • over 10 years ago: ZRen liked this project.
  • about 11 years ago: rsimai liked this project.
  • about 11 years ago: aspiers added keyword "ha" to this project.
  • about 11 years ago: aspiers added keyword "openstack" to this project.
  • about 11 years ago: aspiers joined this project.
  • about 11 years ago: tbechtold liked this project.
  • about 11 years ago: aspiers liked this project.
  • about 11 years ago: KGronlund liked this project.
  • about 11 years ago: jsuchome liked this project.
  • about 11 years ago: osynge liked this project.
  • about 11 years ago: dguitarbite liked this project.
  • about 11 years ago: dguitarbite joined this project.
  • about 11 years ago: mjura started this project.
  • about 11 years ago: mjura originated this project.

  • Comments

    • aspiers
      about 11 years ago by aspiers | Reply

      I'm not sure how much I can help during hackweek due to SLEF events, but please keep me involved for sure :)

    • mjura
      about 11 years ago by mjura | Reply

      Commit from my work https://github.com/mjura/heat-templates/blob/hackweek/cfn/SLES11/SingleVMHA.template

    Similar Projects

    Uyuni read-only replica by cbosdonnat

    Description

    For now, there is no possible HA setup for Uyuni. The idea is to explore setting up a read-only shadow instance of an Uyuni and make it as useful as possible.

    Possible things to look at:

    • live sync of the database, probably using the WAL. Some of the tables may have to be skipped or some features disabled on the RO instance (taskomatic, PXT sessions…)
    • Can we use a load balancer that routes read-only queries to either instance and the other to the RW one? For example, packages or PXE data can be served by both, the API GET requests too. The rest would be RW.

    Goals

    • Prepare a document explaining how to do it.
    • PR with the needed code changes to support it