1 |
Hello everyone! |
2 |
This list has been mighty silent in a while, and I thought I'd juice |
3 |
it up a bit with a 0.0.1 release of AutotuA (for testers only) :) |
4 |
|
5 |
Go ahead, break your head on the code! Test it, hack it, pirate it, |
6 |
whatever! (please? pretty please?) |
7 |
|
8 |
This code is pretty much the same as it was when the code was |
9 |
submitted to Google, but it has a few changes made around it. |
10 |
|
11 |
|
12 |
DEPENDENCIES |
13 |
------------------------ |
14 |
|
15 |
autotua-slave 0.0.1 |
16 |
|
17 |
* dev-lang/python-2.5 |
18 |
* net-misc/connect |
19 |
|
20 |
autotua-master 0.0.1 |
21 |
|
22 |
* dev-lang/python-2.5 |
23 |
* dev-python/django-1.0 |
24 |
|
25 |
WHERE |
26 |
------------ |
27 |
|
28 |
There's an overlay with an ebuild for autotua-slave inside the git repository: |
29 |
http://ur1.ca/60a |
30 |
|
31 |
You can get the tarballs (for the master, and if you don't want to use |
32 |
the ebuild) at: |
33 |
http://ur1.ca/60b |
34 |
|
35 |
STATUS |
36 |
------------- |
37 |
The current status of the project is as follows: |
38 |
|
39 |
The slave infrastructure is 80% complete on the python side. The |
40 |
things left are: |
41 |
- Proper jobuild dependency resolution (doesn't even handle circular |
42 |
deps right now) |
43 |
- The jobuild API (function list etc) is practically non-existant. |
44 |
This is on purpose; I wanted the infrastructure to be ready before I |
45 |
started working on the functions available to jobuilds. IMO this makes |
46 |
sense because the common USE cases for jobuilds need to be polled from |
47 |
developers. |
48 |
- The user-interface for selecting and running jobs is non-existant. |
49 |
This should be quite easy to solve since it just involves importing of |
50 |
modules and using the (excessively simple) API |
51 |
|
52 |
The basic foundation of the master is set; |
53 |
- The django db models are mostly done (I'm quite proud of them tbh =) |
54 |
- Basic integration with the slave exists (automatic dependency |
55 |
resolution given a list of root atoms) |
56 |
- The webinterface is entirely read-only at the moment, and is pretty |
57 |
much impossible to navigate :p |
58 |
- The slave REST API is in good shape, and will be extended for 0.0.2 |
59 |
(more on that below) |
60 |
- setup-master.py can be used to configure and install the django module. |
61 |
- The setup will also setup the database with some test/default values |
62 |
which can be used for testing the Slave |
63 |
|
64 |
HOW |
65 |
-------- |
66 |
|
67 |
- Install autotua-slave using the ebuild |
68 |
- run ./setup-master.py and follow the instructions |
69 |
- Once you have the server up and running, time to test the slave |
70 |
- python autotua/__init__.py will run all the tests, and check every |
71 |
part of the slave |
72 |
|
73 |
Details can be found in the READMEs included in the tarball |
74 |
|
75 |
FUTURE |
76 |
------------- |
77 |
|
78 |
Now then. Let's talk about 0.0.2 :) |
79 |
|
80 |
0.0.2 will consist almost entirely of improvements to the |
81 |
master-server to bring it to a minimal-usable state (volunteers for |
82 |
working on the webinterface needed for speedup ;p). Alongwith the |
83 |
0.0.2 release, the master server will be setup on a remote server so |
84 |
that testers do not have to run a local instance of the django master |
85 |
server to test the slave. At the same time as this, testing will be |
86 |
opened to a larger set of people (later rather than now to prevent a |
87 |
flood of bugs and feature requests ;) |
88 |
|
89 |
There is some preliminary work on the webinterface sitting around |
90 |
dirtying my local git tree, hopefully next month will see a |
91 |
culmination of these efforts :) |
92 |
|
93 |
Oh, and 0.1 will be a public release and will be announced far and |
94 |
wide; by the end of October, if all goes well. |
95 |
|
96 |
Everyone is welcome to contribute to this project (unlike certain |
97 |
closed-doors freedesktop projects :p) |
98 |
|
99 |
Thanks! |
100 |
|
101 |
-- |
102 |
~Nirbheek Chauhan |