Beaker-devel March 2018

beaker-devel@lists.fedorahosted.org

3 participants
3 discussions

beaker-project.org yum repos no longer contain signed RPMs
by Dan Callaghan 16 Jul '18

16 Jul '18

Back in September 2016, we began publishing GPG-signed RPM packages in our server and client yum repos here: https://beaker-project.org/yum/ Due to some rearrangements in how we are handling our builds, starting tonight these repos will no longer contain signed packages. If you have gpgcheck=1 in /etc/yum.repos.d/ you will need to change this back to gpgcheck=0. Sorry for the inconvenience. In future we want to get this signing process going again and we will be looking at ways to enable that. -- Dan Callaghan <dcallagh(a)redhat.com> Senior Software Engineer, Products & Technologies Operations Red Hat

1 1

Beaker 25.0 released
by Róman Joost 23 Mar '18

23 Mar '18

On behalf of the Beaker development team, I'm pleased to announce that Beaker 25.0 is now available from the Beaker web site [1]. Thanks to everyone who contributed patches and bug reports for this release. I'd like to advise to *not* upgrade to this release. As you may notice, the release was made on the 9th of March 2018. Due to a mistake in the release process, the release was created before our release candidate and therefore any acceptance testing was missing. We decided to not announce, but to carry out the acceptance testing which found a few blocking regressions. We've started working on these important fixes which will be released with Beaker 25.1. Beaker 25 adds support for provisioning arbitrary distro trees, Anaconda’s liveimg command, collecting device firmware versions, and many other new capabilities. Full details are available in the release notes [2]. The complete log of all commits since Beaker 24.5 is also available [3]. [1] https://beaker-project.org/releases/ [2] https://beaker-project.org/docs/whats-new/release-25.html#beaker-25-0 [3] https://git.beaker-project.org/cgit/beaker/log/?qt=range&q=beaker-24.5..bea… Kind Regards, -- Róman Joost Senior Software Engineer, Products & Technologies Operations (Brisbane) Red Hat

1 0

Future directions for the Beaker test harness
by Nick Coghlan 12 Mar '18

12 Mar '18

A few weeks back, Amit put together a proof of concept for running the test harness in a container, rather than directly on the host (http://gerrit.beaker-project.org/#/c/3199) That proof of concept relies on restraint, the new reference harness, that is intended to eventually replace beah (https://beaker-project.org/dev/proposals/reference-harness.html) At the same time, I don't think restraint is currently getting the level of review and testing that it needs to mature into a plausible replacement for beah as the default harness. I think Amit's proposed patch provides a possible way forward: 1. Accept the initial approach where restraint is the *only* supported harness when running inside a container. Specifying both "contained_harness" and "harness" as ks_meta variables should be an error at this point (side note: 'harness' should also be documented along with all the other ks_meta variables, with a link to https://beaker-project.org/docs/alternative-harnesses/) 2. Recommend publishing both beah *and* restraint in the harness repos for Beaker installations. This will not only make restraint available for container based testing, but also make it readily available via "harness=restraint" for normal testing, without needing to add a custom repo definition. 3. Once we have container based testing working reliably with restraint, drop the restriction against using alternative harnesses in containers. The priority at the moment though is to get something working that can run on an Atomic Host, and still provide a relatively normal execution environment for the executed tasks. Supporting alternative harnesses *inside* containers is a nice-to-have that can wait until later - by flatly disallowing it, we ensure we don't have to spend any time working on container related issues that don't impact restraint. For the initial iteration, we can also ignore the question of choosing the base image used to run the harness, as well as being able to start and stop other containers on the host. I've filed an RFE for 0.18 on that basis: https://bugzilla.redhat.com/show_bug.cgi?id=1131388 As part of this, we may also want to move restraint from Bill's personal account on GitHub to the main Beaker project account, but I don't think that's particularly urgent at this point. Regards, Nick. -- Nick Coghlan Red Hat Hosted & Shared Services Software Engineering & Development, Brisbane HSS Provisioning Architect

5 10

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Beaker-devel March 2018