#436: SSH access to systems in Beaker lab
--------------------------------------+---------------------
Reporter: atodorov | Owner: tflink
Type: defect | Status: new
Priority: major | Milestone:
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+---------------------
= bug description =
Currently systems in Beaker lab can be accessed only through bastion.fp.o
which is not as convenient as direct SSH into the system.
There's also the question whether or not to open the systems directly to
the Internet.
This needs to be discussed with infra. Filing here so it doesn't get lost.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/436>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance

# Fedora QA Devel Meeting
# Date: 2015-07-27
# Time: 14:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net
Last week's meeting was longer so this should be a shorter one.
If you have any topics to add, respond to this email or bring them up
during open floor.
Tim
Proposed agenda
===============
Status Updates
--------------
- Please have #info statements ready so we can get through this as
quickly as possible
Possible Topics To Cover
------------------------
- feedback on qadevel migration
- Flock preparations
These are optional and may be covered - group discretion after status
updates.
Open Floor
----------
- TBD

# Fedora QA Devel Meeting
# Date: 2015-07-22
# Time: 21:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Length: Approximately 4 hours
There is an outage scheduled for tomorrow, so all of the Taskotron
deployments will be down during that time.
I'm also planning to migrate qadevel to a new home - there will be no
user-facing changes at this time. We're planning to make some
significant changes to qadevel in the near future but are waiting on
some backend changes before we actually do so.
Tim

# Fedora QA Devel Meeting
# Date: 2015-07-20
# Time: 14:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net
Last week's meeting was longer so this should be a shorter one.
If you have any topics to add, respond to this email or bring them up
during open floor.
Tim
Proposed agenda
===============
Status Updates
--------------
- Please have #info statements ready so we can get through this as
quickly as possible
Possible Topics To Cover
------------------------
- quick update on qadevel migration plans
These are optional and may be covered - group discretion after status
updates.
Open Floor
----------
- TBD

I've been working towards migrating qadevel out of the current cloud
setup for a while now and I'd like to finish that migration before we
get too far into F23 testing.
The current plan is to do the migration on Friday so that I have enough
time to fix any issues before folks start using it more again on
Monday.
To enable this, I've updated phabricator on qadevel.cloud so that I'm
not trying to triage issues which could be attributed to multiple,
significant changes.
If you have any concerns about the migration plan or see any problems
with the updated phabricator install, please let me know.
Tim

One of the things on my longer-term todo list has been to get our
canonical git repos out of bitbucket and on to something running free
software (preferably something that we or infra controls). Now that
we're getting closer to migrating off of our current phabricator
instance, I think it's time to consider making this move for at least
the repos that are currently hosted on bitbucket.
As I see it, we have two obvious choices: using phabricator or using
pagure [1]. They both have advantages and disadvantages (that I've
listed at the end of this email) but both are 100% open source and
hosted by Fedora infra.
Thoughts?
Tim
[1] https://pagure.io/
Hosting git repos in phabricator
--------------------------------
Phabricator has been capable of hosting git repos for a while now, the
holdup has been me getting everything ready to migrate on to a new
setup that's capable of doing it
* we have more control over the repo hosting
* we have more responsibility for making sure things stay up, are
recovered in the event of a system failure etc.
* would likely be easier to use some of phab's automation features if
it controls the repos
* ACLs for repos would be controlled in one place
* would require users to upload ssh keys - I don't think we can (not
even sure about should, if it's possible) get ssh pubkey data from
fas @ account creation time
* any extra load from clients cloning task repos would be on our infra
and not causing issues for others
A note that could be worth making is the permissions/policy structure
on phabricator. It can be configured to allow users to create repos but
in order to make that work well enough to justify doing, we'd need to
allow all users to edit all repos as well - I don't see a more
granular way of making this happen ATM. It's not something that isn't
fixable long term if we're not happy with the "request repo for XXX
from admins" process but figured I would mention it.
pagure
------
pagure is a project started in infra. pingou is the main dev and it's
gained quite a few new features lately. Despite the non-fp.o domain, it
is infra hosted.
* We don't have to worry about hosting our own repos
* doing similar things to other groups - I don't think there's any
interest by any other fedora groups in using phabricator unless
something goes horribly wrong with pagure (I also suspect the odds
of that happening are pretty low).
* would require users to upload ssh keys but that's once for all the
things that are (and eventually will be) hosted in pagure
* we'd have to figure out how to handle the eventual pull requests
that are out of process for us - the same thing kinda exists with
bitbucket but I suspect it'll get more common as things progress.

# Fedora QA Devel Meeting
# Date: 2015-07-13
# Time: 14:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net
We'll be holding a QA devel meeting on Monday. We didn't meet last week
so this week may be a longer-ish meeting
If you have any topics to add, respond to this email or bring them up
during open floor.
Tim
Proposed agenda
===============
Status Updates
--------------
- Please have #info statements ready so we can get through this as
quickly as possible
Possible Topics To Cover
------------------------
- wrapping up artifacts deployment
- preparations for F23 branch and alpha
These are optional and may be covered - group discretion after status
updates.
Open Floor
----------
- TBD

Hey, folks. Just to let everyone know, I started looking into why
openQA tests are failing in Rawhide yesterday but got sidetracked
trying to get rid of a bunch of rice weevils in my kitchen. (seriously,
those little buggers are a pain in the rear end).
I'm not sure what's going on with the 'Begin Installation' button
apparently not becoming available in boot.iso , but I know
approximately what's wrong with the live install: the fonts have
somehow changed on some (all?) pages. On the root and user creation
screens at least, the text it's trying to match now looks sufficiently
different (a pixel taller, for one thing) that the match fails. I've
written a new needle for the root screen, but I wanted to try and see
if I could find out what actually happened to cause the text to look
different before we go and create new needles for every text match in
the installer...
also I think the Boston box is on git master branch (of openqa_fedora
and openqa_fedora_tools), not develop, and I think is missing some of
the latest commits. I'm using openqa.happyassassin.net for my testing,
you can see my jobs there.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net