.
>> Works for me! :-)
>>
>
> a dated option like 20150923 would be nice as well
>
> Colin
Colin, can you explain what is your use case here? Such naming only really
affects downloads via the web page / browser; when using the API one can
easily choose a suitable download
Dear All,
We'll carry out maintenance work on the core RIPE Atlas infrastructure
today, approximately between 10-11h Amsterdam time (8-9 UTC). This will also
affect the API/UI, most likely resulting in failed API calls or web page loads.
Excuses for the inconvenience.
Regards,
Robert Kisteleki
> So here’s the question:
>
> Of those of you who would find such a tool interesting/useful, how many of
> you *only* have access to a computer running Python 2.6?
>
> All of my environments support 2.7 so I'm happy yo see 2.6 go away.
>
>
ment-{{ id }}.json.
Works for me! :-)
a dated option like 20150923 would be nice as well
Colin
> On 23 Sep 2015, at 14:04, Iñigo Ortiz de Urbina
> wrote:
>
> On Wed, Sep 23, 2015 at 2:58 PM, Robert Kisteleki wrote:
>> FYI: this has just been deployed.
>
> RIPE-Atlas-measurement-{{ id }}.json.
> Works for me! :-)
>
a dated option like 20150923 would be nice as well
Colin
On Wed, Sep 23, 2015 at 2:58 PM, Robert Kisteleki wrote:
> FYI: this has just been deployed.
RIPE-Atlas-measurement-{{ id }}.json.
Works for me! :-)
--
"If you want to go fast, go alone. If you want to go far, go together."
On 2015-09-17 12:14, Vesna Manojlovic wrote:
> Hi,
>
> sounds like a good idea, we'll add it to the roadmap!
>
> Thanks,
> Vesna
FYI: this has just been deployed.
Cheers,
Robert
> On 17-sep.-15 12:11, Jonathan Brewer wrote:
>> Hi All,
>>
>> One of my current frustrations is that when download
oops, that was meant as an internal heads-up.
Sorry spamming the list.
-- Rene
On 9/23/15 2:44 PM, Rene Wilhelm wrote:
On 9/23/15 2:30 PM, Daniel Quinn wrote:
[...]
Of those of you who would find such a tool interesting/useful, how
many of you *only* have access to a computer runni
On 9/23/15 2:30 PM, Daniel Quinn wrote:
[...]
Of those of you who would find such a tool interesting/useful, how
many of you *only* have access to a computer running Python 2.6?
Such systems include CentOS distributions earlier than 7,
which apparently includes RIPE NCC machines:
Accord to python.org, Python 2.6 (final) was released on October 1st, 2008.
It has served well, but is time to retire in favour of new features/better code.
Rick
From: ripe-atlas [mailto:ripe-atlas-boun...@ripe.net] On Behalf Of Daniel Quinn
Sent: 23 September 2015 13:30
To: RIPE Atla
Hi all
On Wed, Sep 23, 2015 at 2:30 PM, Daniel Quinn wrote:
> So here’s the question:
>
> Of those of you who would find such a tool interesting/useful, how many of
> you only have access to a computer running Python 2.6?
I for one am happy to drop support for 2.6, the systems where I'm
likely t
As some of you may already know, we’ve been working on a new
command-line toolkit that will let you do nifty things like:
* List measurement and probe metadata
* Generate reports from measurement results
* Stream measurement results
It’s coming along quite nicely, but I’m running into just t
Hi all,
quick techie question
how much power is pulled via usb for the probev2 devices ?
Colin
On 2015-09-23 12:29, Colin Johnston wrote:
> maybe compress the data info on the probes before it is sent and save to
> backend storage with the data already compress’d ?
>
> just a thought
>
> Colin
It may be interesting to know, although not at all surprising: compressing
individual results a
maybe compress the data info on the probes before it is sent and save to
backend storage with the data already compress’d ?
just a thought
Colin
On 23/09/2015 09:22, Gert Doering wrote:
> Document the process and criteria better? Maybe.
+ learn lessons + move on + definitely don't stop doing interesting and
exciting stuff just because there was a blip.
Nick
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2015/09/23 10:22 , Gert Doering wrote:
> I have always understood that if you need "more resources than
> your credits allowed", you could talk to the atlas team, explain
> your needs, and find a solution - so it seems this is what was
> done, as
Hi,
On Wed, Sep 23, 2015 at 12:09:03PM +0500, Roman Mamedov wrote:
> You mean not productive trying to place the blame, or not productive to have
> shady anonymous "power users" being arbitrarily and behind-the-scenes granted
> the whole atlas infrastructure as their personal toy to play with? ^^
who is a power user?
>>> i don't think it is productive to go down this path
>> randy, you read my mind
>
> You mean not productive trying to place the blame, or not productive
> to have shady anonymous "power users" being arbitrarily and
> behind-the-scenes granted the whole atlas infrastruc
On Wed, Sep 23, 2015 at 9:00 AM, Randy Bush wrote:
>o disk is cheap; don't compress
You need to update your cliches :-)
Disk might be cheap, but I/O certainly isn't.
On Wed, 23 Sep 2015 09:05:24 +0200
Antonio Prado wrote:
> On 9/23/15 9:01 AM, Randy Bush wrote:
> >> who is a power user?
> >
> > i don't think it is productive to go down this path
>
> randy, you read my mind
You mean not productive trying to place the blame, or not productive to have
shady a
On 9/23/15 9:01 AM, Randy Bush wrote:
>> who is a power user?
>
> i don't think it is productive to go down this path
randy, you read my mind
--
antonio
> who is a power user?
i don't think it is productive to go down this path
randy
a great post mortem, thanks! my uneducated thoughts
o disk is cheap; don't compress
o occasionally, large scale measurements in narrow time windows
will be useful
randy
24 matches
Mail list logo
