As a separate thing/issue, I will try and write up a coherent design of
what we currently have in mind, since the discussion took place over
multiple places and some timespan. That way we can see what we have in one
place, and discuss parts of the system that are still unclear, etc.
___
Hi,
forgot to reply to this email earlier on..
On Tue, Jun 11, 2013 at 6:02 PM, Damian Johnson wrote:
> > I can try experimenting with this later on (when we have the full /
> needed
> > importer working, e.g.), but it might be difficult to scale indeed (not
> > sure, of course). Do you have any
> I can try experimenting with this later on (when we have the full / needed
> importer working, e.g.), but it might be difficult to scale indeed (not
> sure, of course). Do you have any specific use cases in mind? (actually
> curious, could be interesting to hear.)
The advantages of being able to
Ah, forgot to add my footnote to the dirspec - we all know the link, but in
any case:
[1]: https://gitweb.torproject.org/torspec.git/blob/HEAD:/dir-spec.txt
This was in the context of discussing which fields from 2.1 to include.
On Tue, Jun 11, 2013 at 12:34 AM, Kostas Jakeliunas
wrote:
> > Her
>
> > Here, I think it is realistic to try and use and import all the fields
> available from metrics-db-*.
> > My PoC is overly simplistic in this regard: only relay descriptors, and
> only a limited subset of data fields is used in the schema, for the import.
>
> I'm not entirely sure what fields
Hi!
>>> Maybe we should focus on a 'grand unified backend' rather than
> >>> splitting Kostas' summer between both a backend and frontend? If he
> >>> could replace the backends of the majority of our metrics services
> >>> then that would greatly simplify the metrics ecosystem.
> >>
> >> I'm most
> Here, I think it is realistic to try and use and import all the fields
> available from metrics-db-*.
> My PoC is overly simplistic in this regard: only relay descriptors, and only
> a limited subset of data fields is used in the schema, for the import.
I'm not entirely sure what fields that w
On 5/29/13 4:05 AM, Kostas Jakeliunas wrote:
> Hello!
> (@tor-dev: will also write a separate email, introducing the GSoC project
> at hand.)
>
>> This GSoc idea started a year back as a searchable descriptor search
>> application, totally unrelated to Onionoo. It was when I read Kostas'
>> propo
Hello!
(@tor-dev: will also write a separate email, introducing the GSoC project
at hand.)
This GSoc idea started a year back as a searchable descriptor search
> application, totally unrelated to Onionoo. It was when I read Kostas'
> proposal that I started thinking about an integration with Onio
Hi Kostas. Now that we no longer need to worry about accidentally
leaking GSoC selection we can talk more openly about your project.
Below is an interchange between me and Karsten - thoughts?
-- Forwarded message --
From: Karsten Loesing
Date: Thu, May 23, 2013 at 11:37 AM
Subject
10 matches
Mail list logo
