Amit Saha | 4 May 06:56 2015
Picon

Simplify inventorying systems in Beaker

Hi all,

As part of implementing https://bugzilla.redhat.com/show_bug.cgi?id=846185 and 
https://bugzilla.redhat.com/show_bug.cgi?id=1121462, I was thinking that the best
user experience would be if we ask nothing of the user. They need to just click
on a system's "Update Inventory" button or run the "bkr update-inventory <fqdn>" command
to update the inventory data for the system.

So, the key step is to figure out which distro to use. RHEL6/CentOS6 would cover most
of the hardware, but there may be exceptions for older/newer hardware archs. So, here is
what I am thinking:

1. Start with RHEL6/CentOS6, and check if the system is compatible with it. If yes, go to step 4, 
else go to step 2.

2. Is the system compatible with RHEL7/CentOS7? If yes, go to step 4, else go to step 3.

3. Is the system compatible with RHEL5/CentOS5? If yes, go to step 4, else error out.

4. Submit a job with the chosen distro and /distribution/install and /distribution/inventory tasks.
(The job will use the <hostRequires force = .. /> element so that all non-removed systems can be inventoried
as long as the job owner has the sufficient rights on the system)

One immediate drawback of this is using hard coded distro names above. 

Another idea I can think of is have a system level ksmeta variable defined such as "inventory_distro=MyOSMajor"
and use that. But that is asking of system owners/beaker admins to have to do that explicitly. 
It would also vastly simplify the implementation.

Thoughts?
(Continue reading)

Dan Callaghan | 24 Apr 05:10 2015
Picon

Changing status ordering in Beaker 21

In the next Beaker major release (21.0) we are planning to make a change 
to the way Beaker computes the overall status for jobs, recipe sets, and 
recipes.

Currently if some tasks in a recipe are Completed but others are Aborted 
or Cancelled, the overall recipe status will be Completed. This is 
surprising and (arguably) less useful because it obscures the fact that 
the whole recipe did not really complete.

Similarly, if some recipes in a recipe set or job are Completed but 
others are Aborted or Cancelled, the overall status will be Completed 
right now.

In Beaker 21 we will change the status calculation so that if any task 
is Aborted or Cancelled, the entire recipe is Aborted or Cancelled, and 
thus the recipe set and job is Aborted or Cancelled too.

If you see any issues with this change in behaviour please bring it up 
here and we can discuss.

--

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

Dan Callaghan | 21 Apr 03:22 2015
Picon

Beaker 20.0 released

On behalf of the Beaker development team, I'm pleased to announce that 
Beaker 20.0 is now available from the Beaker web site [1]. Thanks to 
everyone who contributed patches and bug reports for this release.

In Beaker 20 we have implemented the "system pools" feature. On top of 
that, it is now also possible to set a system to use the access policy 
defined on a pool. The aim is to make it easy to apply the same access 
policy across a large number of systems.

The other significant feature in Beaker 20 is support for configuring 
the network boot loader on a per-recipe basis. This lets Beaker 
automatically select a supported boot loader depending on the distro 
being provisioned, and for users to select a different boot loader in 
their recipes.

There are also plenty of other minor enhancements and fixes. As usual, 
the release notes [2] have all the details.

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

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

--

-- 
Dan Callaghan <dcallagh <at> redhat.com>
Software Engineer, Products & Technologies Operations
Red Hat, Inc.
(Continue reading)

Amit Saha | 27 Mar 05:43 2015
Picon

bkr client docker image

Just something which may  be useful:
https://github.com/amitsaha/docker_files/tree/master/dev_workflow/beaker-client

Everytime you run the image, it will always try to install the latest beaker client
from the nightlies repository.

Example:

$ docker run -ti amitsaha/bkr job-list --hub=https://beaker.server.com --username asaha

....

--> Running transaction check
---> Package beaker-client.noarch 0:19.4-0.git.109.fc3396d.fc19 will be updated
---> Package beaker-client.noarch 0:19.4-0.git.112.ed6b232.fc19 will be an update
--> Processing Dependency: beaker-common = 19.4-0.git.112.ed6b232.fc19 for package: beaker-client-19.4-0.git.112.ed6b232.fc19.noarch
--> Running transaction check
---> Package beaker-common.noarch 0:19.4-0.git.109.fc3396d.fc19 will be updated
---> Package beaker-common.noarch 0:19.4-0.git.112.ed6b232.fc19 will be an update
--> Finished Dependency Resolution

Dependencies Resolved
..
..
Updated:
  beaker-client.noarch 0:19.4-0.git.112.ed6b232.fc19
Enter your password:

  ["J:7637", "J:7636"

(Continue reading)

Alexander Todorov | 19 Mar 13:23 2015
Picon

Which restraint repo to use ?

Hi guys,
I've found two repos for restraint:

https://bpeck.fedorapeople.org/restraint/el7/

https://amitksaha.fedorapeople.org/restraint/centos7/

It looks like the 1st one is more up-to-date. Which one is recommended for use?

Thanks,
Alex
_______________________________________________
Beaker-devel mailing list
Beaker-devel <at> lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
Jaroslav Kortus | 27 Feb 22:00 2015
Picon

Integration Tests results

Hi there,

I've just executed full integration tests run with the following result (patched develop 
branch):
Ran 1345 tests in 6731.735s

FAILED (SKIP=3, errors=70, failures=55)

real	112m14.756s
user	101m11.856s
sys	7m42.248s

Quite some errors then. Much more than I expected :). Looking at the results I have mixed 
feelings.

Some selenium tests were failing (almost all in my case). When I ran the same test alone 
it passed with no problems.

To get more data I ran the suite with "-sv" switch. Looking at the output there are some 
things that I'm not sure are errors or not.

For instance:
bkr.server.mail: ERROR: Exception thrown when trying to send mail
[...]
error: [Errno 111] Connection refused
bkr.server.tests.data_setup: DEBUG: Marked R:706 as complete with result Pass

or:
FAIL: test_all_tables_use_innodb (bkr.inttest.server.test_model.SchemaSanityTest)
----------------------------------------------------------------------
(Continue reading)

Nick Coghlan | 27 Feb 03:02 2015
Picon

Fedora COPR now supports package signing

We've previously discussed the idea of allowing Beaker to depend on EPEL
when running on RHEL/CentOS, thus allowing the use of Fedora's COPR
system for package builds.

The COPR team recently switched COPR over to signing packages by
default, so it may be worth revisiting that idea at some point in the
coming weeks/months.

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
Andrej Manduch | 26 Feb 21:20 2015
Picon

[PATCH] bkr-client-autocompletion: grep -> /usr/bin/grep

From: Andrej Manduch <amanduch <at> gmail.com>

When you have strange things in your ~/.basrc (like grep --color=always)
then beaker autocompletion can produce wrong output.
example:
burlak <at> borg /e/bash_completion.d $ bkr
-h
^[[m^[[Kpolicy-revoke^[[01;31m^[[K
--help
^[[m^[[Kremove-account^[[01;31m^[[K
^[[m^[[Kdistros-edit-version^[[01;31m^[[K
^[[m^[[Ksystem-delete^[[01;31m^[[K
^[[m^[[Kdistros-list^[[01;31m^[[K
^[[m^[[Ksystem-details^[[01;31m^[[K
^[[m^[[Kdistros-tag^[[01;31m^[[K

This patch will ensure that bkr autocompletion will
always use original `grep`.

Signed-off-by: Andrej Manduch <amanduch <at> gmail.com>
---
 Client/bash-completion/bkr | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/Client/bash-completion/bkr b/Client/bash-completion/bkr
index 76d6b9e..f64e1c0 100644
--- a/Client/bash-completion/bkr
+++ b/Client/bash-completion/bkr
 <at>  <at>  -7,9 +7,10  <at>  <at> 
 # Function expands options from main option (like workflow-tcms)
(Continue reading)

Andrej Manduch | 26 Feb 21:38 2015
Picon

[PATCH] bkr-client-autocompletion: grep -> /usr/bin/grep

When you have strange things in your ~/.basrc (like grep --color=always)
then beaker autocompletion can produce wrong output.
example:
burlak <at> borg /e/bash_completion.d $ bkr
-h
^[[m^[[Kpolicy-revoke^[[01;31m^[[K
--help
^[[m^[[Kremove-account^[[01;31m^[[K
^[[m^[[Kdistros-edit-version^[[01;31m^[[K
^[[m^[[Ksystem-delete^[[01;31m^[[K
^[[m^[[Kdistros-list^[[01;31m^[[K
^[[m^[[Ksystem-details^[[01;31m^[[K
^[[m^[[Kdistros-tag^[[01;31m^[[K

This patch will ensure that bkr autocompletion will
always use original `grep`.

Signed-off-by: Andrej Manduch <amanduch <at> gmail.com>
---
 Client/bash-completion/bkr | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/Client/bash-completion/bkr b/Client/bash-completion/bkr
index 76d6b9e..f64e1c0 100644
--- a/Client/bash-completion/bkr
+++ b/Client/bash-completion/bkr
 <at>  <at>  -7,9 +7,10  <at>  <at> 
 # Function expands options from main option (like workflow-tcms)
 _bkr_complete()
 {
(Continue reading)

Nick Coghlan | 19 Feb 03:46 2015
Picon

Receiving HTML rather than JSON despite Accept header

Hi folks,

I'm trying to use the HTTP APIs documented in
https://beaker-project.org/docs-release-19/server-api/http.html as follows:

    curl --negotiate -H 'Accept: application/json' https://<Beaker server domain>

I have a valid Kerberos ticket, but the main page just returns the HTML list of systems, while the
subcollections for available, free and my systems return a login page redirect.

So it appears either something is broken or the API documentation has omitted a required setup step.

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
Jaroslav Kortus | 13 Feb 23:36 2015
Picon

Building beaker from sources

Hi there,

I've recently come to a need of building beaker from git.

Unfortunately there's couple of obstacles I'd like your advice on.

First: no tito anymore. Last time I was doing the rebuilds from upstream devel branch it 
was using tito which was quite handy for generating srpms which I then had rebuilt. Is 
there anything helpful in the same way today?

I found it quite difficult compared to my previous experience. Even the deps listed in the 
spec file are hard to download (wget downloads it as a different name from what's expected 
in the spec file).

Second: beaker-transfer does not start "green" any more without archive server config 
options present. So the question is: do I need that daemon for anything really?

I've ran the jobs in my current combo setup (LC+server on one machine) and it seemed to me 
to transfer the logs just as before with the daemon (beaker-transfer) down.

Third: I would like to have some step-by-step howto on building the packages from sources. 
I could not find it on the website. Something similar to kickstarts for custom-deployment 
of beaker. With all necessary repos linked as well as commands that you use to build the 
final packages.

Thanks for any pointers that could resolve my issues :).

Cheers,
Jaroslav.
_______________________________________________
(Continue reading)


Gmane