From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id A332820090F for ; Thu, 26 May 2011 02:20:19 -0700 (PDT) Received: from mail-qw0-f43.google.com (mail-qw0-f43.google.com [209.85.216.43]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id p4Q9YWdv013425 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Thu, 26 May 2011 11:34:33 +0200 Received: by qwf6 with SMTP id 6so394222qwf.16 for ; Thu, 26 May 2011 02:34:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.43.90 with SMTP id v26mr400084qce.169.1306402472158; Thu, 26 May 2011 02:34:32 -0700 (PDT) Received: by 10.229.88.66 with HTTP; Thu, 26 May 2011 02:34:32 -0700 (PDT) In-Reply-To: References: Date: Thu, 26 May 2011 11:34:32 +0200 Message-ID: From: Walter de Donato To: Nick Feamster Content-Type: multipart/alternative; boundary=00148536e7244964b504a42a871a Cc: bismark-devel@lists.bufferbloat.net Subject: Re: [Bismark-devel] Fwd: Bismark on M-Lab X-BeenThere: bismark-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: BISMark related software development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2011 09:20:20 -0000 --00148536e7244964b504a42a871a Content-Type: text/plain; charset=ISO-8859-1 Some comments about the following two points: > > 1. Whenever you're ready, I can put you in touch with the people who > run the data pipeline, which will result in your getting the BisMark data > off the M-Lab servers and in to Google Storage. You can work with them on > data structure, etc.. > 2. Here's a link > to > the Public Data Explorer blog post, announcing their new API for data > upload. This should give you a cursory idea of what would be involved in > getting the analyzed BisMark data properly structured and visualized. > > We don't currently store any kind of data no the measurement servers. Do we plan to change this? If that's the cast we won't need to transfer data from MLab Servers to Google Storage. Probably the upload will be necessary from the management servers to Google Storage. I agree with Dave about staying below the radars until we solve some of the cited issues. When we have some time to do some reasoning again, I'd like to talk to Dave about the VPN usage he has in mind. -Walter --00148536e7244964b504a42a871a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Some comments about the following two points:
<= blockquote type=3D"cite">
  1. Whenever you're ready, I can put you in touch with the people w= ho run the data pipeline, which will result in your getting the BisMark dat= a off the M-Lab servers and in to Google Storage. You can work with them on= data structure, etc..
  2. Here's a link to the Publ= ic Data Explorer blog post, announcing their new API for data upload. This = should give you a cursory idea of what would be involved in getting the ana= lyzed BisMark data properly structured and visualized.
We don't currentl= y store any kind of data no the measurement servers. Do we plan to change t= his?
If that's the cast we won't need to transfer data from MLab Se= rvers to Google Storage.
Probably the upload will be necessary fr= om the management servers to=A0Google Storage.

I agree with Dave about staying below the radars until we solve some of the= cited issues.

When we have some time to do some r= easoning again,=A0
I'd like to talk to Dave about the VPN usa= ge he has in mind.

-Walter
--00148536e7244964b504a42a871a--