[gentoo-soc] Online Image builder Proposal - gentoo-soc

From:	"ethankhall@×××××.com" <ethankhall@×××××.com>
To:	gentoo-soc@l.g.o
Subject:	[gentoo-soc] Online Image builder Proposal
Date:	Thu, 02 Apr 2009 20:32:24
Message-Id:	`0015175cb07e44f6ca046698541d@google.com`

1

I've shared a document with you called "Online Image builder":  

2

http://docs.google.com/Doc?id=dh224f9_13d9btp4c2&invite=1199440422 It's not  

3

an attachment -- it's stored online at Google Docs. To open this document,  

4

just click the link above. --- Here is my proposal for the Online Image  

5

Builder. Any comments or though would be greatly appreciated. A copy of the  

6

document is included along with an invitation on Google Doc's for any  

7

changes that you see are necessary.

8

Online Image Builder

9

10

Objective: To provide the ability for the Gentoo users to have installable  

11

images built by a web server that would contact them when it was ready to  

12

be downloaded.

13

14

Abstract:  Using example front ends create a way to deliver a generic  

15

Gentoo system without having to have a user there to do the installation.   

16

The delivery would then be provided in several formats (zip, tar.bz,  

17

bootable iso).  The user would be expected to install their own kernel, a  

18

genkernel will be shipped with the installation image but will not be  

19

suitable for every user so they *should* go and recompile it with their own  

20

options.

21

22

Deliverable's:

23

A website (in PHP or Python) with the ability to take orders from users,  

24

que them, and notify users when their build is ready to be downloaded.

25

User documentation in an easy to understand format.

26

A modular design so new things can be put into place with ease.

27

A generic base system for x86 and amd64 (server and desktop of each).

28

29

Timeline:

30

May 10th - 24th:

31

Get a standard set of use flags that will be applied to every package (will  

32

be different for each system).

33

Get a standard set of packages that will be installed on each system.

34

Decide on standard CFLAGS to be used, most likly CFLAGS="-O2 -march=i686  

35

-pipe"

36

Begin work on Python script to do the install.

37

Decide what platform will do the building.

38

May 24th - June 8th:

39

Have Python script done and work on debugging it.

40

Have the finalized set of packages that will be available to be installed  

41

though the online tool.

42

Begin work on the que system.

43

Begin front end mock up/decide what mock up to use.

44

June 8th - June 22nd:

45

Do a build via the online (protected) front end and debug w/ que utility.

46

Decide what to include with each delivery.

47

Prepare a bootable iso template.

48

Have everything that is build saved in a binary form (to save time for each  

49

build).

50

June 22nd - 29th:

51

Flex time for unanticipated problems.

52

June 29th - July 20th:

53

Have multiple people build systems concurrently(while website still  

54

protected).  Test system tax's.

55

Work out any bugs on the delivery system's.

56

Find and fix system bottlenecks.

57

July 20th - August 10th:

58

Have the site open to the gentoo population with a request for error's that  

59

happen on build.

60

Fix error's.

61

Generate a time from request to delivery time sample.

62

Be able to predict (withing an hour or two) when a user's build will be  

63

ready.

64

Find and fix system bottlenecks.

65

August 10th - Onward:

66

Improve delivery system.

67

Find and fix system bottlenecks.

68

Fix error's.

69

Make build system portable (so it can be taken to different location ie.  

70

university, and have builds done by there servers with even more  

71

customizability).

72

73

About me:

74

My name is Ethan Hall, I am currently a sophomore in the college of  

75

Computer and Electrical Engineering at Purdue University. I am 20 years old  

76

My  parents are currently located in VA, my mom has just started an alpaca  

77

farm, we will see how well that goes. In my free time I like to swing  

78

dance,  mostly. I am currently the designer for Night Train swing dance  

79

club. I love it, it gives me a way to relax, and mingle with people after a  

80

hard day of engineering homework. One of my goals every semester is to try  

81

to bring my friends into the swing club so they can experience it too. Lets  

82

face it, there is a reason that the stereotypical engineer is a nerd who  

83

plays video games all the time. I also like to ride motorcycles but as of  

84

yet to own one, this is one of my summer goals. I am in a call at Purdue  

85

called EPICS and it has been a great way for me to get my feet wet with  

86

actual applications of of products. My team works for a museum called  

87

Imagination Station, and I personal am a co-team leader. The project I work  

88

on is called the LASER maze, it teaches kids about LASER's reflection and  

89

reflection. It has shown me some really cool things and make me realize why  

90

there are "warranty void if opened" stickers on everything. When one thing  

91

starts to work anther stops working. AHH agrivating.

Gentoo Archives: gentoo-soc

Replies

1	I've shared a document with you called "Online Image builder":
2	http://docs.google.com/Doc?id=dh224f9_13d9btp4c2&invite=1199440422 It's not
3	an attachment -- it's stored online at Google Docs. To open this document,
4	just click the link above. --- Here is my proposal for the Online Image
5	Builder. Any comments or though would be greatly appreciated. A copy of the
6	document is included along with an invitation on Google Doc's for any
7	changes that you see are necessary.
8	Online Image Builder
9
10	Objective: To provide the ability for the Gentoo users to have installable
11	images built by a web server that would contact them when it was ready to
12	be downloaded.
13
14	Abstract: Using example front ends create a way to deliver a generic
15	Gentoo system without having to have a user there to do the installation.
16	The delivery would then be provided in several formats (zip, tar.bz,
17	bootable iso). The user would be expected to install their own kernel, a
18	genkernel will be shipped with the installation image but will not be
19	suitable for every user so they should go and recompile it with their own
20	options.
21
22	Deliverable's:
23	A website (in PHP or Python) with the ability to take orders from users,
24	que them, and notify users when their build is ready to be downloaded.
25	User documentation in an easy to understand format.
26	A modular design so new things can be put into place with ease.
27	A generic base system for x86 and amd64 (server and desktop of each).
28
29	Timeline:
30	May 10th - 24th:
31	Get a standard set of use flags that will be applied to every package (will
32	be different for each system).
33	Get a standard set of packages that will be installed on each system.
34	Decide on standard CFLAGS to be used, most likly CFLAGS="-O2 -march=i686
35	-pipe"
36	Begin work on Python script to do the install.
37	Decide what platform will do the building.
38	May 24th - June 8th:
39	Have Python script done and work on debugging it.
40	Have the finalized set of packages that will be available to be installed
41	though the online tool.
42	Begin work on the que system.
43	Begin front end mock up/decide what mock up to use.
44	June 8th - June 22nd:
45	Do a build via the online (protected) front end and debug w/ que utility.
46	Decide what to include with each delivery.
47	Prepare a bootable iso template.
48	Have everything that is build saved in a binary form (to save time for each
49	build).
50	June 22nd - 29th:
51	Flex time for unanticipated problems.
52	June 29th - July 20th:
53	Have multiple people build systems concurrently(while website still
54	protected). Test system tax's.
55	Work out any bugs on the delivery system's.
56	Find and fix system bottlenecks.
57	July 20th - August 10th:
58	Have the site open to the gentoo population with a request for error's that
59	happen on build.
60	Fix error's.
61	Generate a time from request to delivery time sample.
62	Be able to predict (withing an hour or two) when a user's build will be
63	ready.
64	Find and fix system bottlenecks.
65	August 10th - Onward:
66	Improve delivery system.
67	Find and fix system bottlenecks.
68	Fix error's.
69	Make build system portable (so it can be taken to different location ie.
70	university, and have builds done by there servers with even more
71	customizability).
72
73	About me:
74	My name is Ethan Hall, I am currently a sophomore in the college of
75	Computer and Electrical Engineering at Purdue University. I am 20 years old
76	My parents are currently located in VA, my mom has just started an alpaca
77	farm, we will see how well that goes. In my free time I like to swing
78	dance, mostly. I am currently the designer for Night Train swing dance
79	club. I love it, it gives me a way to relax, and mingle with people after a
80	hard day of engineering homework. One of my goals every semester is to try
81	to bring my friends into the swing club so they can experience it too. Lets
82	face it, there is a reason that the stereotypical engineer is a nerd who
83	plays video games all the time. I also like to ride motorcycles but as of
84	yet to own one, this is one of my summer goals. I am in a call at Purdue
85	called EPICS and it has been a great way for me to get my feet wet with
86	actual applications of of products. My team works for a museum called
87	Imagination Station, and I personal am a co-team leader. The project I work
88	on is called the LASER maze, it teaches kids about LASER's reflection and
89	reflection. It has shown me some really cool things and make me realize why
90	there are "warranty void if opened" stickers on everything. When one thing
91	starts to work anther stops working. AHH agrivating.