Project

General

Profile

action #92149

crosscheck status/goal/maintainership of a machine "qam2"

Added by okurz 3 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
Start date:
2021-05-05
Due date:
% Done:

0%

Estimated time:

Description

I heard from tjyrinki that a machine qam2 should be used also to run an instance of the openQA maintenance bot. That should be clarified and crosschecked.

History

#1 Updated by osukup 3 months ago

there is a production instance of openQABot ....

qam2.suse.de -> run's some QEM services - dashboard, openQA bot, teregen and is intended as the successor of qam.suse.de

#2 Updated by jbaier_cz 3 months ago

Depending on what bot are we talking about, this is already covered by https://gitlab.suse.de/qa-maintenance/qamops/-/blob/master/ansible/roles/openqabot/tasks/main.yml

#3 Updated by okurz 3 months ago

  • Status changed from New to Feedback
  • Assignee set to okurz

thank you, that helps to fight urban legends 😃

#4 Updated by okurz 3 months ago

where can more information about the machine "qam2" itself be found?

#5 Updated by jbaier_cz 3 months ago

As qam2 is meant to be a replacement of qam, there is a page in confluence describing the current state; migrated services are present in the ops repo, documentation will be updated as soon as all relevant and "mission critical" services are on the new machine.

#6 Updated by okurz 3 months ago

jbaier_cz wrote:

As qam2 is meant to be a replacement of qam, there is a page in confluence describing the current state; migrated services are present in the ops repo,

I see, good.

documentation will be updated as soon as all relevant and "mission critical" services are on the new machine.

ok, and who can do that or plan to do that? You / only you? Somebody else?

#8 Updated by okurz 2 months ago

  • Assignee changed from okurz to jbaier_cz

can you please help with questions in #92149#note-6

#9 Updated by jbaier_cz 2 months ago

  • Assignee changed from jbaier_cz to okurz

I am/was driving the change for the "mission critical" services. As of now, all important (to my knowledge) parts but the main SVN endpoint are migrated. The migration of the SVN endpoint can be done almost anytime via changing one DNS record (the preparation for that is already done). No concrete date was selected so far, an announcement of this is needed beforehand as some user stuff could still be there which might depend on being available through the hostname qam.suse.de; after the DNS switch, both servers will be still available under respective names (qam1 and qam2), however the main endpoint for daily usage (qam.suse.de) will be server from the new host. In ideal case, no change from the user side will be needed.

All new applications shall be deployed on the new host and purely through the GitLab automation project, like it is in case of qem-dashboard or openQA bot.

If you need further information, I am probably the right go-to person for this part of QEM infrastructure.

#10 Updated by okurz about 2 months ago

  • Status changed from Feedback to Resolved

Thank you. I consider all the information you provided as sufficient. I added the reference to the qamops gitlab repo and the confluence page to https://progress.opensuse.org/projects/qa/wiki/Wiki/diff?utf8=%E2%9C%93&version=217&version_from=216&commit=View+differences

Also available in: Atom PDF