Task #2893


evaluate cloud hosting

Added by Florian Effenberger almost 5 years ago. Updated 10 months ago.

Target version:
Team - Qlater
Start date:
Due date:
% Done:




From the FOSDEM discussion:

  • Cloud hosting
    • trying to avoid maintaining our own Gluster
    • for CI-stuff, renting resource at Amazon too expensive.
    • evaluate migrating a few of them makes sense.
    • helpful - widely shared
      • try to get rid of distributed file-system / crash-recovery
    • not strongly in favour of current setup
      • in favour of hosting ourselves.
      • not in love with Gluster.
    • independent from last 2 glitches.
      • not directly related, not the reason to look.
    • buying new H/W for CI - is it ?
      • perhaps don't need more H/W but shift things around.
      • the non-CPU bound loads into the cloud, and use H/W for CI.
      • current hypervisor wouldn't make good build-bots
Actions #1

Updated by Florian Effenberger almost 5 years ago

  • Hosting vs. Cloud
    • suggest to prefer moving service to cloud before buying new HW (Thorsten)
    • suggest not CI / compile at Amazon (Michael)
    • prefer not to have to run clustered FS ourselves (Florian)
    • does Guilhelm have experience of cloud-iness (Bjoern?)
      • can he look into moving simple websites to Amazon.
    • free up existing hardware for CI
      -> investigate migrating Gluster using workloads to Amazon / elsewhere
Actions #2

Updated by Florian Effenberger over 4 years ago

  • Subject changed from evaluate other storage options to evaluate cloud hosting

From the Munich in-person meeting:

  • cost-wise could be expensive
  • we have no issues atm related to Gluster, didn't have for a long time
  • might face other problems with cloud hosting
  • Amazon expensive, Hetzner cloud cheaper, but less flexible
  • Green IT a requirement, might rule out some cloud providers
  • let's give it a try: Jitsi, Wiki; maybe (!) Redmine; AskBot; Dashboard; OpenGrok; crashtest VM; downloadarchive -> NVMe storage could speed up database operations
  • don't change too much, otherwise hard to compare
  • good contact to manitu vs. Hetzner as mass-hosting
  • Can we get big IP subnet at Hetzner?
  • keep in mind SLA/service availability for cloud (vServer no official support during the weekend)
  • filoo is used for monitoring, so not on the table for services
Actions #3

Updated by Florian Effenberger over 4 years ago

  • Target version changed from Q4/2019 to Q1/2020

Can we look into this during FOSDEM? I'd like to make a start in Q1

Actions #4

Updated by Florian Effenberger over 3 years ago

  • Status changed from New to In Progress
  • Target version changed from Q1/2020 to Q1/2021

In place for some services (eg. Weblate)
Further evaluation by Q1/2021

Actions #5

Updated by Guilhem Moulin over 2 years ago

  • Target version changed from Q1/2021 to Qlater

Some CI bots and the conferencing system are hosted there too.

Actions #6

Updated by Guilhem Moulin 10 months ago

  • Status changed from In Progress to Closed

Also available in: Atom PDF