[Fedora QA] #436: SSH access to systems in Beaker lab
by fedora-badges
#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
7 years, 1 month
[CANCELLED] 2016-01-30 Fedora QA Devel Meeting
by Tim Flink
Most if not all the regular suspects for the qadevel meeting are going
to be otherwise occupied at a conference Monday and Tuesday so I don't
see much point in holding the regular meeting.
If someone wants to hold and chair a meeting at the regular time, you
are welcome to do so but I won't be available to chair.
Tim
7 years, 4 months
Temporary Disposable Client Image Process
by Tim Flink
As far as I know, the plan for handling the disposable client images
for the immediate future is to build and distribute them manually until
the real system is in place.
To that end, I figure that it'll work best to just put the compressed
images somewhere that's easy to access. I'm planning to just put them
here for now:
https://tflink.fedorapeople.org/taskotron/taskotron-cloud/images/
I'd recommend against anyone else relying on a single image too heavily
right now - this is very unlikely to be the final place we put images
if it ends up making sense to make them easily grab-able.
Tim
7 years, 4 months
Deploying Disposable Clients to stg
by Tim Flink
I realize that this is pretty short notice but I don't think that
anyone is watching stg but us, so I can't imagine this affecting anyone.
I'm going to re-deploy stg with f23 and libtaskotron 0.4 so we can get
that into production soon.
I'll send out another email when it's all done.
Tim
7 years, 4 months
Example Suggestions for Automation Workshop
by Tim Flink
I'm preparing for an automation workshop at DevConf in February and I'm
trying to think of good example cases to show off what Taskotron can do.
At the moment, I figure that I'll do at least 1 easy task and 1 not so
easy but not crazy task.
Rpmlint is usually my go-to for a trivial/example task but I was hoping
to use something that's a bit more package specific. The things I've
thought of so far are:
- Put together some package specific stuff for a package that we have
some control over (testcloud, yourls etc.)
- Find some other guinea pig package that just works well for
package-specific tasks since the triggering will be artificial for
the demos
- See if there are any existing test cases which would automate easily.
Any other thoughts or suggestions?
Tim
7 years, 4 months
2016-01-18 @ 15:00 UTC - Fedora QA Devel Meeting
by Tim Flink
# Fedora QA Devel Meeting
# Date: 2016-01-18
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting-1 on irc.freenode.net
The agenda looks much like last week for some reason. I'd like to
get the process of having disposable clients in production started
by the end of the week, though.
Please put announcements and information under the "Announcements and
Information" section of the wiki page for this meeting:
https://phab.qadevel.cloud.fedoraproject.org/w/meetings/20160118-fedoraqa...
Tim
Proposed Agenda
===============
Announcements and Information
-----------------------------
- Please list announcements or significant information items below so
the meeting goes faster
Tasking
-------
- Does anyone need tasks to do?
Potential other topics
----------------------
- disposable clients release status
- image building
- docker and fedora atomic
- examples for automation workshop?
Open Floor
----------
- TBD
7 years, 4 months
openQA packaging update: os-autoinst reviewed, 4.3 update and
staging COPR
by Adam Williamson
Hey folks! Just wanted to share a quick update on the status of openQA
packaging.
Zbigniew Jędrzejewski-Szmek did a really good review of os-autoinst,
and approved it today. I'm just waiting on the dist-git repo then we
can get it into the official repos.
os-autoinst and openQA both got 4.3 releases in the last couple of
days. I set up a new openQA-stg COPR -
https://copr.fedoraproject.org/coprs/adamwill/openQA-stg/ - and did 4.3
builds of both packages there. I've pushed a change to the infra
ansible repo which enables the openQA-stg COPR for the staging hosts.
So 4.3 is now on https://openqa.stg.fedoraproject.org/ . I figure to
leave it there over the weekend to give it a bit of a workout, then if
all goes well, I'll do the 4.3 builds in the regular COPR so the prod
instance moves to 4.3.
Long term, once the packages are all in the official repos, my thought
is that we'll configure ansible such that stg picks up openQA / os-
autoinst updates from updates-testing, and then we can send new
versions there and then push them stable after a few days if stg looks
OK. Perhaps I'll keep a COPR for 'devel' builds - git snapshots, for
e.g. - which I could test on happyassassin.net.
We could set up a similar arrangement with git branches if we want to
have some form of staging for the tools and tests; perhaps have staging
use 'develop' and prod use 'master', and push from develop to master
periodically. But so far I'm not sure this is really necessary, as
testing changes to those bits is fairly easy and non-complex, and
fixing bugs is usually not difficult either.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 4 months