action #87979
closed
Requirements for access to the openqa VM
Added by nicksinger over 3 years ago.
Updated almost 3 years ago.
Description
Infra asked us to provide a list of users and required commands to provide us access to the openqa.suse.de VM.
I think https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/sshd/users.sls is too broad for access. Therefore we need to define a list of users manually for now:
- Andrii Nikitin
- Christian Dywan
- Ivan Lausuch
- Jan Baier
- Marius Kittler
- Nick Singer
- Oliver Kurz
- Ondřej Súkup
- Sebastian Riedel
- Tina Müller
- Vasileios Anastasiadis
- Liu Xiaojing
- Stephan Kulow
(I took this list from our rocket.chat room, did I forget anybody?)
For now I see a need for the following commands:
- Force power off VM
- Force reset VM
- Start VM
- Spice (serial access)
- Status changed from New to In Progress
- Target version set to Ready
- Due date set to 2021-02-02
I guess this is still blocking on the Jira ticket as of 2020-01-19? Should the status be set accordingly?
- Status changed from In Progress to Blocked
cdywan wrote:
I guess this is still blocking on ...
I assume you mean "blocked by"? Or do you mean that this ticket "blocks" the jira ticket? I have the suspicion that someone ran into a deadlock and someone from SUSE-IT is waiting for us to provide something ...
- Due date deleted (
2021-02-02)
- Priority changed from High to Low
As the ticket is blocked already by the jira ticket I removed the due-date and commented on the jira-ticket what timeframe to expect for progress.
- Status changed from Blocked to Resolved
The Jira ticket is not resolved but we have provided all necessary information and multiple comments in Jira. As we ourselves don't expect more and can live with the current situation well enough anyway we can set this ticket to "Resolved".
Also available in: Atom
PDF