Hi folks,
My Factory 2.0 teammate Matt Jia, with some help from me, has been working on getting Waiverdb deployed in Fedora infrastructure so that we can start hooking things up to it.
(For anyone who hasn't heard of Waiverdb before, it is a service for recording waivers against test results in ResultsDB. More info at https://pagure.io/waiverdb and in the Focus Doc at https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/WaiverDB).
We would like to request a FAS group be given access to run waiverdb playbooks in stage/prod using rbac-playbook, so that we don't have to keep bugging Ralph for everything. :-) Our first idea was to re-use the `sysadmin-qa` group for this.
I have a bit of experience with using rbac-playbook myself, for the Beaker playbooks, and I'm assuming that ResultsDB and other related services are also set up the same way with `sysadmin-qa`. So I think it makes sense to do the same with Waiverdb.
How does that sound to the Fedora QA team?
Also, would someone be willing to sponsor Matt (FAS username mjia) into sysadmin-qa? Matt and I sit together here in the office so I am always available to help out too.
On Wed, May 3, 2017 at 4:30 AM, Dan Callaghan dcallagh@redhat.com wrote:
Hi folks,
My Factory 2.0 teammate Matt Jia, with some help from me, has been working on getting Waiverdb deployed in Fedora infrastructure so that we can start hooking things up to it.
(For anyone who hasn't heard of Waiverdb before, it is a service for recording waivers against test results in ResultsDB. More info at https://pagure.io/waiverdb and in the Focus Doc at https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/WaiverDB).
We would like to request a FAS group be given access to run waiverdb playbooks in stage/prod using rbac-playbook, so that we don't have to keep bugging Ralph for everything. :-) Our first idea was to re-use the `sysadmin-qa` group for this.
I have a bit of experience with using rbac-playbook myself, for the Beaker playbooks, and I'm assuming that ResultsDB and other related services are also set up the same way with `sysadmin-qa`. So I think it makes sense to do the same with Waiverdb.
How does that sound to the Fedora QA team?
It sounds good to me, more helping hands are always welcome :-)
Also, would someone be willing to sponsor Matt (FAS username mjia) into sysadmin-qa? Matt and I sit together here in the office so I am always available to help out too.
I don't really know the infra processes, so the right person to ping here would be tflink from our team (he's in Raleigh this week on an Infra FAD), or kevin or puiterwijk from Infra team.
On Tue, 9 May 2017 15:25:31 +0200 Kamil Paral kparal@redhat.com wrote:
<snip>
Also, would someone be willing to sponsor Matt (FAS username mjia) into sysadmin-qa? Matt and I sit together here in the office so I am always available to help out too.
I don't really know the infra processes, so the right person to ping here would be tflink from our team (he's in Raleigh this week on an Infra FAD), or kevin or puiterwijk from Infra team.
They're actually in the same room :-P
I've added and sponsored mjia to sysadmin-qa.
Dan, I assume that you'll be helping him figure out the bastion hosts etc.?
Tim
Excerpts from Tim Flink's message of 2017-05-09 10:53 -04:00:
I've added and sponsored mjia to sysadmin-qa.
Thanks!
Dan, I assume that you'll be helping him figure out the bastion hosts etc.?
Yep will do.
On Tue, 2017-05-09 at 15:25 +0200, Kamil Paral wrote:
On Wed, May 3, 2017 at 4:30 AM, Dan Callaghan dcallagh@redhat.com wrote:
Hi folks,
My Factory 2.0 teammate Matt Jia, with some help from me, has been working on getting Waiverdb deployed in Fedora infrastructure so that we can start hooking things up to it.
(For anyone who hasn't heard of Waiverdb before, it is a service for recording waivers against test results in ResultsDB. More info at https://pagure.io/waiverdb and in the Focus Doc at https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/WaiverDB).
We would like to request a FAS group be given access to run waiverdb playbooks in stage/prod using rbac-playbook, so that we don't have to keep bugging Ralph for everything. :-) Our first idea was to re-use the `sysadmin-qa` group for this.
I have a bit of experience with using rbac-playbook myself, for the Beaker playbooks, and I'm assuming that ResultsDB and other related services are also set up the same way with `sysadmin-qa`. So I think it makes sense to do the same with Waiverdb.
How does that sound to the Fedora QA team?
It sounds good to me, more helping hands are always welcome :-)
No objection here either. Note sysadmin-qa membership also grants admin rights to the openQA deployments, I believe; if anyone's interested in learning how to look after those, feel free to poke me.
qa-devel@lists.fedoraproject.org