1 |
Hi Antanas, |
2 |
|
3 |
First of all, thanks to showing your interest in this project. I'll be |
4 |
the assigned mentor for the project if you're going to be working on |
5 |
it. |
6 |
|
7 |
To answer your concerns (in quite an unsorted fashion, I apologize), I |
8 |
would start with saying that what we're looking for with this project |
9 |
is to have not just an average log collector, but one that is |
10 |
integrated explicitly with components such as Portage and Bugzilla; |
11 |
the target of this project, for me, is to be able to use it for the |
12 |
tinderboxes I've been running (which are currently on-hold because I'm |
13 |
too busy with training at a new job). |
14 |
|
15 |
While I'm not discounting *any* particular technology right away, |
16 |
we're looking for something that works quickly and relatively |
17 |
easily... sometimes while technology is already out there that could |
18 |
work, it doesn't suit the workflow as it is right now. At the same |
19 |
time, for what I'm concerned you can start by keeping the use of |
20 |
Amazon's AWS services, if it helps you. The end goal is to avoid using |
21 |
it, but there is no hurry with that, as the costs associated with it |
22 |
are very marginal right now. The only important part here is that the |
23 |
data you store on AWS is not persistent when using the final |
24 |
collector. |
25 |
|
26 |
I don't have any problem with "wasting" the 10 days — but this does |
27 |
not give any "get out of trouble free" card for the evaluation, so |
28 |
keep it in mind, you might have to do some harder work in the first |
29 |
few days. But that does not say much, some people actually performs |
30 |
better under pressure, so it's up to you if you want to go for it or |
31 |
not :) |
32 |
|
33 |
If there is anything else you want to know, feel free to ask on the |
34 |
mailing list and I'll answer ASAP. |
35 |
|
36 |
Thanks, |
37 |
Diego |
38 |
|
39 |
Diego Elio Pettenò — Flameeyes |
40 |
flameeyes@×××××××××.eu — http://blog.flameeyes.eu/ |
41 |
|
42 |
|
43 |
On Mon, Apr 22, 2013 at 2:19 AM, Antanas Uršulis |
44 |
<antanas.ursulis@×××××.com> wrote: |
45 |
> Hello, |
46 |
> |
47 |
> I'm a final year Computer Science undergraduate at the University of |
48 |
> Cambridge (UK). My main languages are C and C++, but my bachelor's project |
49 |
> involves working with and modifying the CIEL task-parallel execution system |
50 |
> written in Python, and I have also been using Python for my scripting needs. |
51 |
> I have been a Gentoo user since 2009 (switched from *buntu), if I can |
52 |
> remember correctly. |
53 |
> |
54 |
> I am interested in the "Log collector/analyzer for tinderbox" GSoC project, |
55 |
> not only because I would like to help the developers of my favourite Linux |
56 |
> distribution, but I could also see myself using an extension of the tool to |
57 |
> oversee my own systems (for example, computers at the Lithuanian National |
58 |
> Olympiad in Informatics, where I am a member of the technical staff). |
59 |
> |
60 |
> Of course, there are some things I would like to discuss. Firstly, are there |
61 |
> already any thoughts on a replacement for Amazon's SimpleDB storage? I would |
62 |
> see that as a major part of the project. Second, if I were to think of this |
63 |
> as a more general tool, with the possibility to support various log |
64 |
> providers (portage, apache, etc.) and analyzers in the future, what would |
65 |
> your opinion be on that? I think it would be possible to implement this |
66 |
> without any external dependencies, so that Portage remains light. Third, |
67 |
> after a quick search, I came upon the question: is there a reason not to |
68 |
> hook into systems such as Apache Flume + Elastic Search, or logstash, or |
69 |
> Scribe? |
70 |
> |
71 |
> Lastly, I would like to know up-front whether you would be OK with me only |
72 |
> being to able to fully focus on the project from the 7th June - I have exams |
73 |
> until then and cannot devote my time to this. That is 10 calendar days lost |
74 |
> from the "Students get to know mentors, read documentation, get up to speed |
75 |
> to begin working on their projects." phase. |
76 |
> |
77 |
> I'm happy to provide more background about myself and hope to hear from you! |
78 |
> |
79 |
> Regards, |
80 |
> Antanas Uršulis |