1 |
This week has gone pretty well and I'm hoping to get a testing server |
2 |
up soon, though it looks like it will be running the backend in a |
3 |
virtual machine due to the root privileges requirement. I've added |
4 |
support for several more output formats: ext2 image, jffs2, and two |
5 |
different styles of bootable ISO - one that's just a standard weekly |
6 |
Gentoo minimal CD with a tarball of the system, and one that replaces |
7 |
the minimal CD's environment with the generated system (the CDs are at |
8 |
a fairly primitive stage, but I did succeed in booting both of them |
9 |
with qemu). I also changed around the frontend so that rather than |
10 |
configuring each build individually, configuration is done on reusable |
11 |
configurations, which can then be used any number of times to request |
12 |
actual builds. I also added an invitations system to allow a more |
13 |
closed environment, especially for testing before it's ready for |
14 |
release. |
15 |
Both the frontend and backend are now set up to use modules (presently |
16 |
I'm only worrying about modules for Gentoo/portage) so that in the |
17 |
future, support can be added for other distributions or package |
18 |
managers. I also did some work to provide more high-level functions |
19 |
for these modules so they will be easy to write and modify. The |
20 |
portage backend now caches the generated image after the base system |
21 |
has been installed, providing a huge reduction in the time it takes to |
22 |
generate an image for large profiles once the cache exists. |
23 |
Lastly, the backend can now upload completed images to the frontend |
24 |
for a case when they are on separate machines and it is not desirable |
25 |
to have users download their finished images directly from the backend |
26 |
machines on which they were compiled. |
27 |
|
28 |
To do: |
29 |
-Make the frontend more user-friendly (particularly the selection of |
30 |
packages to install) |
31 |
-Allow editing of configurations after they are initially completed |
32 |
-Wrinkle out the rest of the issues with separating frontend and backend |
33 |
-Make sure no race conditions exist when using more than one backend |
34 |
to serve one frontend |
35 |
-Figure out a (safe) system for updating the package repositories, |
36 |
particularly with backend and frontend split and with multiple |
37 |
backends |
38 |
-Perhaps more important of all, provide more options to configure the |
39 |
image produced (see http://etherpad.com/BJkgXcMkwJ for current list of |
40 |
options, http://forums.gentoo.org/viewtopic-p-5830406.html if you have |
41 |
suggestions) |
42 |
|
43 |
Thanks to those who have been giving support and offering suggestions so far. |
44 |
|
45 |
Eudyptula |