action #90164


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

coordination #43934: [epic] Manage o3 infrastructure with salt again

Make public

Added by okurz about 3 years ago. Updated about 3 years ago.

Feature requests
Target version:
Start date:
Due date:
% Done:


Estimated time:



To be able to use the salt recipes for o3 as well as provide it as a solution to manage any openQA infrastructure we decided to make public, e.g. put it on github within

Acceptance criteria

  • AC1: is available on a public, non-personal git repository
  • AC2: SUSE QE Tools team member have read-write access to the repository
  • AC3: Changes in the repo are still automatically applied within the OSD infrastructure


  • Research about best practices to move from internal gitlab repo to external github/gitlab
  • Copy to github, e.g. in scope, and create back-mirror into salt-states repo or get rid of it completely
Actions #1

Updated by okurz about 3 years ago

  • Status changed from Workable to In Progress
  • Assignee set to okurz mentions a script solution to move from gitlab to github which mostly concerns transferring issues and such. As we only use the git repo itself plus CI but no issues or wiki we do not need that. explains how gitlab repositories can be automatically synced with github repos. Of course this – same as all other solutions I found except for polling – need access to the gitlab server from github so that github can trigger actions within gitlab. But given that we also pull test code by cron job every minute in I don't see a problem with that.

to replace hardcoded mentions of with jinja variables.

Actions #2

Updated by openqa_review about 3 years ago

  • Due date set to 2021-04-17

Setting due date based on mean cycle time of SUSE QE Tools

Actions #3

Updated by okurz about 3 years ago

  • Status changed from In Progress to Feedback

waiting for MR feedback

Actions #4

Updated by okurz about 3 years ago

  • Status changed from Feedback to In Progress

Followed to sync with . This pushed , so far so good. Now about the other direction. Pulling from github is a "premium" feature for gitlab: so I am thinking of a gitlab CI job to pull periodically, maybe as often as every 5 minutes or even every minute. For production use I would prefer to use a non-personal email-adress.

I created a new github account "openqa-git-sync", created a new github project and invited that user as a member, created a personal token within that user account and setup mirroring in with that token to

Actions #5

Updated by okurz about 3 years ago

  • Status changed from In Progress to Resolved

password stored in

split out the sync from to into #91332

Actions #6

Updated by okurz about 3 years ago

  • Tracker changed from coordination to action
  • Due date deleted (2021-04-17)

Also available in: Atom PDF