Nick Coghlan | 19 Dec 09:54 2014
Picon

Updated road map & PTO

Hi folks,

I've published the updated release road map at
https://beaker-project.org/dev/release-roadmap.html, covering plans for
the 19.2 maintenance release, and the planned focus for the next two
major feature releases.

Beaker 20 will be aimed at implementing the remaining Predefined Access
Policy [1] component of the previously deferred access policies design
proposal.
Beaker 21 will focus on a new proposal Dan is working on to revamp the
job details page to be less noisy and easier to use effectively.

I'm also off on 3 weeks vacation, followed by a week at linux.conf.au
2015, so I'll catch y'all in 2015 :)

Cheers,
Nick.

[1]
https://beaker-project.org/dev/proposals/access-policies-for-systems.html#predefined-access-policies

Cheers,
Nick.

--

-- 
Nick Coghlan
Red Hat Hosted & Shared Services
Software Engineering & Development, Brisbane

(Continue reading)

Amit Saha | 19 Dec 00:40 2014
Picon

restraint: main.c used anymore?

Is the file src/main.c of any use anymore?

--

-- 
Amit Saha 
SED, Hosted & Shared Services
Red Hat, Inc.
_______________________________________________
Beaker-devel mailing list
Beaker-devel <at> lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
Nick Coghlan | 16 Dec 04:20 2014
Picon

Creating a "Beaker Release Roadmap"

When I started the "Handling Large Installations" design proposal [1],
it was intended to document a series of smaller steps towards the
specific goal of implementing more automated usage constraints and other
usability improvements in Beaker to reduce the level of training needed
to use a large installation appropriately.

Over time, it's usage morphed to become a running record of past Beaker
releases, and our current plans for future releases. I actually quite
like that usage style, so I'll be changing it to officially be that, and
dropping it as a "design proposal".

Cheers,
Nick.

[1]
https://beaker-project.org/dev/proposals/handling-large-installations.html

--

-- 
Nick Coghlan
Red Hat Hosted & Shared Services
Software Engineering & Development, Brisbane

HSS Provisioning Architect
_______________________________________________
Beaker-devel mailing list
Beaker-devel <at> lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
Amit Saha | 15 Dec 08:14 2014
Picon

Docker based workflow for working on restraint

In case you don't want a few additional packages on your system, here is a
script which will build a docker image installing all dependencies needed to run restraint's tests:

#!/bin/bash
# ./restraint.sh <image_name> <docker_base_image>
uid=`id -u`
user=`id -un`

cat <<EOF > Dockerfile

FROM $2

RUN yum -y install make glib2 glib2-devel glibc-devel libarchive-devel libsoup-devel gcc pkgconfig
gettext libselinux-devel openssl-devel perl-XML-Parser selinux-policy-devel zlib-devel git
git-daemon tar thttpd
RUN yum -y install emacs-nox
RUN useradd -u $uid $user
USER $uid

EOF

docker build -t $1 .
mv Dockerfile Dockerfile.$1
echo "$1 created. Entering: /home/$user"
docker run -v /home/$user:/home/$user -ti $1 bash

Assuming you have docker setup:
./restraint.sh fedora21_restraint fedora:21

Will build the docker image and also start the container:
(Continue reading)

Amit Saha | 15 Dec 03:13 2014
Picon

Setting up a new project in Beaker's git/gerrit infrastructure

Scenario: Create a fork of an upstream project whose source is on github

Steps:

1. Fork the project as beaker-project's upstream on GitHub
2. Login to beaker-project.org
3. Init a bare git repo on /srv/git/: git init --bare --shared <project_name>
4. chown -R <username>:beakerdevs /srv/git/≤project_name>
5. Setup the project on http://gerrit.beaker-project.org/#/admin/create-project/, inherit
permissions from beaker project 
6. Setup DENY permission for  Fedorahosted replication authgroup
7. Push the master branch of upstream fork to gerrit: git push restraint-gerrit master

--

-- 
Amit Saha 
SED, Hosted & Shared Services
Red Hat, Inc.
_______________________________________________
Beaker-devel mailing list
Beaker-devel <at> lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
Amit Saha | 11 Dec 09:03 2014
Picon

Hostname for the docker container

Hi all,

While investigating an issue with running the test harness in a container, I realized the if 
hostname is used anywhere in the harness, it really will be the container's hostname (container ID)
and not  the test system's. 

Should we stick to that? Or should we set it to the host's $HOSTNAME? 

Perhaps, we should keep it as it is, since we may move to multi-container testing, etc where
container ID would be how we address another container.

Best,
Amit.

--

-- 
Amit Saha 
SED, Hosted & Shared Services
Red Hat, Inc.
_______________________________________________
Beaker-devel mailing list
Beaker-devel <at> lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
Dan Callaghan | 25 Nov 07:54 2014
Picon

Beaker 19.0 released

On behalf of the Beaker development team, I'm pleased to announce that 
Beaker 19.0 is now available from the Beaker web site [1].

I'm particularly excited about this release because it includes the 
system page improvements which have been under development for quite 
a while. The other neat feature in this release is fully automatic 
database upgrades.

The release notes [2] have all the details, including a number of 
important notes for users who are familiar with the existing system 
page.

The detailed list of all changes made since Beaker 0.18.4 is also 
available [3].

[1] https://beaker-project.org/releases/
[2] https://beaker-project.org/docs/whats-new/release-19.html
[3] https://git.beaker-project.org/cgit/beaker/log/?qt=range&q=beaker-0.18.4..beaker-19.0&showmsg=1

--

-- 
Dan Callaghan <dcallagh <at> redhat.com>
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
_______________________________________________
Beaker-devel mailing list
Beaker-devel <at> lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
(Continue reading)

Jirka Hladky | 24 Nov 12:25 2014
Picon

Task /distribution/reservesys is broken on Fedora21

Hello,

extendtesttime.sh does not work on Fedora21 Server:

[root <at> karkulka-02 tests]# extendtesttime.sh 48
Extending reservation time 48
ERROR: 2 args provided

Usage:
     rhts-test-checkin <lab_server> <hostname> <jobid> <test> <killtime> 
<testid>

root: rhts-test-checkin  karkulka-02.lab.eng.brq.redhat.com   48h

How to reproduce?

Privison in Beaker server with "Fedora-Server-21_Beta Server x86_64". 
After installation, login on the server and try to run extendtesttime.sh

Bellow is an example XML generated by Beaker "Provision" command.

Thanks
Jirka

<job retention_tag="scratch">
     <whiteboard>
         Provision Fedora-Server-21_Beta Server x86_64
     </whiteboard>
     <recipeSet priority="High">
         <recipe kernel_options="console=tty0 console=ttyS1,115200n81 
(Continue reading)

Nick Coghlan | 19 Nov 01:48 2014
Picon

Group SSH keys on manually provisioned systems

Is there a way to get a whole group's SSH keys onto a system without
going through the scheduler? Or is manual provisioning currently
restricted to only added the SSH key of the user provisioning the system?

Cheers,
Nick.

--

-- 
Nick Coghlan
Red Hat Hosted & Shared Services
Software Engineering & Development, Brisbane

HSS Provisioning Architect
_______________________________________________
Beaker-devel mailing list
Beaker-devel <at> lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
Amit Saha | 17 Nov 03:17 2014
Picon

Beaker inventory: smolt & lshw comparison

Hi all,

As part of the migration to "lshw" for beaker's inventory task, I ran a comparison of the "smolt"
based tasks with the "lshw" based task. 

The "raw" data is available in the "comparison.html" file under each arch sub-directory at:
https://amitksaha.fedorapeople.org/beaker-inventory-comparison/comparison_data/

Here are the summarized differences:

** i686/AMD/athlon (32-bit system)

CPU flags
=========

* lshw categorises "fpu_exception" as a CPU flag, adds "wp" as cpu flag too.
  (This is because we assume all the stuff lshw lists as CPU capabilities,
  we consider them flags)

Others
======

* USBID retrieved by lshw with repetition, smolt didn't retrieve any
* Same PCIID retrieved by lshw, however there is repetition of a device (for PCIID as well)
* lshw is not able to detect the system model (same as smolt)
* lshw sets arch to i686 instead of i386 by smolt
* lshw fails to get the system vendor (same as smolt)
* lshw fails to get the FORMFACTOR
* CPUVENDOR obtained by smolt is  AuthenticAMD, lshw sets it to "Advanced Micro Devices [AMD]"

(Continue reading)

Nick Coghlan | 10 Nov 13:34 2014
Picon

Subtest support in unittest2!

Robert Collins has backported one of my favourite Python 3 features to
unittest2: subtests!

See the Python 3 docs [1] for details, but the basic idea is to let you
easily split up a data driven test such that:

1. All iterations execute, even if some of the checks fail
2. Each failure is reported separately, with relevant details you provide

For example:

===================
class NumbersTest(unittest.TestCase):

    def test_even(self):
        """
        Test that numbers between 0 and 5 are all even.
        """
        for i in range(0, 6):
            with self.subTest(i=i):
                self.assertEqual(i % 2, 0)
===================

Will check all values from 0 to 5, and report separate failures for 1, 3
and 5.

The only other particular notable new feature is the addition of the
"assertLogs" context manager to test cases, which makes it easier to
check logging within the current process is performed correctly as part
of unit tests.
(Continue reading)


Gmane