Gentoo Archives: gentoo-soc

From: Nirbheek Chauhan <nirbheek.chauhan@×××××.com>
To: gentoo-soc@l.g.o
Cc: steev@g.o, Patrick Lauer <bugs@××××××××××××××××××××××.org>, armin76@g.o, ford_prefect@g.o
Subject: [gentoo-soc] AutotuA 0.0.1 (testers' version) Released!
Date: Wed, 17 Sep 2008 18:48:53
Message-Id: 8b4c83ad0809171148w2b11bc39g1b385b4ef6129873@mail.gmail.com
Hello everyone!
This list has been mighty silent in a while, and I thought I'd juice
it up a bit with a 0.0.1 release of AutotuA (for testers only) :)

Go ahead, break your head on the code! Test it, hack it, pirate it,
whatever! (please? pretty please?)

This code is pretty much the same as it was when the code was
submitted to Google, but it has a few changes made around it.


DEPENDENCIES
------------------------

autotua-slave 0.0.1

 * dev-lang/python-2.5
 * net-misc/connect

autotua-master 0.0.1

 * dev-lang/python-2.5
 * dev-python/django-1.0

WHERE
------------

There's an overlay with an ebuild for autotua-slave inside the git repository:
http://ur1.ca/60a

You can get the tarballs (for the master, and if you don't want to use
the ebuild) at:
http://ur1.ca/60b

STATUS
-------------
The current status of the project is as follows:

The slave infrastructure is 80% complete on the python side. The
things left are:
- Proper jobuild dependency resolution (doesn't even handle circular
deps right now)
- The jobuild API (function list etc) is practically non-existant.
This is on purpose; I wanted the infrastructure to be ready before I
started working on the functions available to jobuilds. IMO this makes
sense because the common USE cases for jobuilds need to be polled from
developers.
- The user-interface for selecting and running jobs is non-existant.
This should be quite easy to solve since it just involves importing of
modules and using the (excessively simple) API

The basic foundation of the master is set;
- The django db models are mostly done (I'm quite proud of them tbh =)
- Basic integration with the slave exists (automatic dependency
resolution given a list of root atoms)
- The webinterface is entirely read-only at the moment, and is pretty
much impossible to navigate :p
- The slave REST API is in good shape, and will be extended for 0.0.2
(more on that below)
- setup-master.py can be used to configure and install the django module.
- The setup will also setup the database with some test/default values
which can be used for testing the Slave

HOW
--------

- Install autotua-slave using the ebuild
- run ./setup-master.py and follow the instructions
- Once you have the server up and running, time to test the slave
- python autotua/__init__.py will run all the tests, and check every
part of the slave

Details can be found in the READMEs included in the tarball

FUTURE
-------------

Now then. Let's talk about 0.0.2 :)

0.0.2 will consist almost entirely of improvements to the
master-server to bring it to a minimal-usable state (volunteers for
working on the webinterface needed for speedup ;p). Alongwith the
0.0.2 release, the master server will be setup on a remote server so
that testers do not have to run a local instance of the django master
server to test the slave. At the same time as this, testing will be
opened to a larger set of people (later rather than now to prevent a
flood of bugs and feature requests ;)

There is some preliminary work on the webinterface sitting around
dirtying my local git tree, hopefully next month will see a
culmination of these efforts :)

Oh, and 0.1 will be a public release and will be announced far and
wide; by the end of October, if all goes well.

Everyone is welcome to contribute to this project (unlike certain
closed-doors freedesktop projects :p)

Thanks!

-- 
~Nirbheek Chauhan