Project

General

Profile

Actions
Copy link

action #37300

closed

Create salt config for openqa-service

Added by dheidler almost 6 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
nicksinger
Category:
-
Target version:
-
Start date:
2018-06-13
Due date:
% Done:

0%

Estimated time:

Description

openqa-service.suse.de is running the openqa_bugfetcher for o3 and osd, the hermes amqp->irc bot and the osd totest-manager.

The documentation for this machine should be done by salt.

Related issues 2 (0 open — 2 closed)

Related to openQA Tests - action #27735: [tools][sle][functional][u][hard]Use ttm (totest-manager.py) from http://github.com/openSUSE/osc-plugin-factory/ for SLEResolveddheidler2017-11-142018-07-31

Actions
Related to QA - action #132362: Bring openqa-service.qe.suse.de up-to-dateResolvedokurz2023-06-28

Actions
Actions
Copy link
 #1

Updated by dheidler almost 6 years ago

  • Related to action #27735: [tools][sle][functional][u][hard]Use ttm (totest-manager.py) from http://github.com/openSUSE/osc-plugin-factory/ for SLE added
Actions
Copy link
 #2

Updated by okurz almost 6 years ago

  • Category set to Infrastructure
Actions
Copy link
 #3

Updated by coolo over 5 years ago

  • Project changed from openQA Tests to openQA Infrastructure
  • Subject changed from [tools] create salt config for openqa-service to Create salt config for openqa-service
  • Category deleted (Infrastructure)
Actions
Copy link
 #4

Updated by nicksinger over 5 years ago

  • Status changed from New to Workable
  • Assignee set to dheidler

Please add my key there so we can at least start by making this machine accessible:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDUXU3S8tB5NqhSN+pycYJwxWqmDeGUbo8MlwhCYAd7f9YlPVgSaVeKkUdI1wXGeYUh8yY+7Btohjt1GG1blwrwauBFOaAbWoQcm0/e7dpU8ggB/JnDrKrDIw2sBAE3xEOtJ+d1weAA+/8QgtP+GB9XdzUeyg9KEVv9WTcaKNylEu7zks61QIwS5F8JqOA7TxNamdp8V4rpwuJYUzWoLNbJM8Cr2Fj3RXLghoWoc+kclkkxCIvNm3b3ceCqIRtu4EDsRW24Y3L+tLrJ6a4F13A4xTBnOyi1f8CAMS4/oJlCqh+MX5k6akPJTp4INgcxBcm077L9zKO1H9FxccuG4mktbbDPq19avl5SmdWDszGkHsXQ+wJHNL4R5vGU+pm66qIWDN0bbTBWDq90ckui7dDS+r4SbJIbdkp5Xlqlp04doIo7VZImi1kL+ydWIyPv6Q/pRa3XEIy0Kiy0POs9Mf6mtnXhwOWAu7yruFEfOoXHl6WbejoDaaFcjURxmb3sNYmSHa5E5owjX3MhCVdez90jQgmI8tinsskVRUfh9wv71rAK+qAnoX0y1jrBC/4xXFr947FR2y6z6n7rhdip2i7l5f/iPxRRzVxLUTf55zBi3B3HheOVbz41R/Bm9JBzbkGXJ/tp54G7GjM+ZsuyFulKapLHs23TXva/Q+VWVeYzPw== nsinger@suse.de
Actions
Copy link
 #5

Updated by dheidler over 5 years ago

  • Assignee changed from dheidler to nicksinger

I added your key but this might not be permanent as the machine is somehow managed by infra salt (somewhere in gitlab).

Actions
Copy link
 #6

Updated by nicksinger over 5 years ago

  • Status changed from Workable to Rejected

dheidler wrote:

I added your key but this might not be permanent as the machine is somehow managed by infra salt (somewhere in gitlab).

This way it doesn't make sense to salt the machine in our setup. Please clarify first the responsibility (because there is o3 as well as OSD stuff on there) and if we should take this machine over; take the necessary steps to get the machine removed out of infras "domain" (as this seems to be the decision in the first place).

Actions
Copy link
 #7

Updated by okurz 10 months ago

  • Related to action #132362: Bring openqa-service.qe.suse.de up-to-date added
Actions
Copy link

Also available in: Atom PDF