Beaker-devel October 2017

beaker-devel@lists.fedorahosted.org

2 participants
3 discussions

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

Beaker 24.5 released
by Dan Callaghan 14 Dec '17

14 Dec '17

On behalf of the Beaker development team, I'm pleased to announce that Beaker 24.5 is now available from the Beaker web site [1]. Thanks to everyone who contributed patches and bug reports for this release! Beaker 24.5 is a maintenance release which fixes an annoying issue on the job page and the recipe page which made it impossible to select or copy system hostnames. A number of other minor bug fixes are also included in the release. As always, full details are available in the release notes [2]. The complete log of all commits since Beaker 24.4 is also available [3]. [1] https://beaker-project.org/releases/ [2] https://beaker-project.org/docs/whats-new/release-24.html#beaker-24-5 [3] https://git.beaker-project.org/cgit/beaker/log/?qt=range&q=beaker-24.4..bea… -- Dan Callaghan <dcallagh(a)redhat.com> Senior Software Engineer, Products & Technologies Operations Red Hat

3 5

returning system activity table information.
by Shawn Doherty 02 Oct '17

02 Oct '17

Hello. I was hoping someone had an idea on the best way to get activity information from a system in beaker. My situation is that I am trying to incorporate parts of the Beaker CLI in a bash script to automate Request Tracker work. Part of this would require getting the activity history from a requested system. I didn't find anything suitable when looking through the Beaker CLI. wget wasn't returning the information that I needed from a call to #history. I'm throwing this out there to see if anyone on the list had any suggestions. Looking specifically for getting the information on User and Action:Returned. Thanks, Shawn -- Shawn Doherty Software Engineer, Kernel-HW Red Hat <https://www.redhat.com> 314 Littleton Rd Westford, MA 01886 sdoherty(a)redhat.com T: 19785891080 INTERNAL:-8131080 IM: sdoherty <https://red.ht/sig>

4 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Beaker-devel October 2017