Project

General

Profile

Actions
Copy link

action #126941

open

openQA Project - coordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes

openQA Project - coordination #92854: [epic] limit overload of openQA webUI by heavy requests

[spike] Evaluate a move of the osd database to its own VM

Added by livdywan about 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
QA - future
Start date:
2023-03-30
Due date:
% Done:

0%

Estimated time:
Tags:
infra

Description

Motivation

With the database split out the total load could be managed better.

Acceptance Criteria

  • AC1: Benefits of running the openQA database on a dedicated host are known

Suggestions

  • Confirm the effort and impact of using another VM to host the database
  • Evaluate the current side-effects of openQA and postgres running on the same host e.g. hard limits on the VM host we can use
Actions
Copy link
 #1

Updated by okurz about 1 year ago

  • Tags set to infra
  • Project changed from openQA Project to openQA Infrastructure
  • Priority changed from Normal to Low
  • Target version set to future

I would do this if we know that the database execution is a significant contributor. How about you rephrase it to evaluate if that move would help?

Actions
Copy link
 #2

Updated by livdywan about 1 year ago

  • Subject changed from Move the osd database to its own VM to [spike] Evaluate a move the osd database to its own VM
  • Description updated (diff)
Actions
Copy link
 #3

Updated by livdywan about 1 year ago

  • Subject changed from [spike] Evaluate a move the osd database to its own VM to [spike] Evaluate a move of the osd database to its own VM
Actions
Copy link

Also available in: Atom PDF