FYI
Begin forwarded message:
> From: "Zen - Technical Support" <support(a)zen.co.uk>
> Subject: RE: IPv6 support [5405065:4109486]
> Date: 10 December 2012 12:17:28 GMT
> To: "Dave Pigott" <dave.pigott(a)linaro.org>
>
> Hello,
>
> The Zen core network has not yet had IPv6 turned on which would give you a native IPv6 connection as yet. Although our network could handle IPv6 Our admin systems are not yet fully compliant.
>
> You can however set up a 6in4 tunnel using a provider such as sixxs or hurricane electric which would give two-way IPv6 connectivity.
>
>
> David Flint
> Service Support Consultant
> Zen Internet
> T: 0845 058 9009
> F: 0845 058 9005
> W: http://www.zen.co.uk
>
>
>> -----Original Message-----
>> From: "Dave Pigott" <dave.pigott(a)linaro.org>
>> Received: 10/12/2012 10:12
>> To: support(a)zen.co.uk
>> Subject: RE: IPv6 support
>>
>> Hi,
>>
>> Just wondering if our leased line supports IPv6 or not? We would like to support both v4 and v6 if at all possible.
>>
>> Kind regards
>>
>> Dave Pigott
>
> ------------------
> Take a look inside and explore our new state of the art, award-winning Data Centre -http://www.zen.co.uk/business/default.aspx?page=11592
>
> Please consider your environmental responsibility before printing this email.
>
> This message is private and confidential. If you have received this message in error please notify us and remove it from your system.
>
> Zen Internet Limited may monitor email traffic data to manage billing, to handle customer enquiries and for the prevention and detection of fraud. We may also monitor the content of emails sent to and/or from Zen Internet Limited for the purposes of security, staff training and to monitor quality of service.
>
> Zen Internet Limited is registered in England and Wales
> Sandbrook Park, Sandbrook Way, Rochdale OL11 1RY
> Company No. 03101568
> VAT Reg No. 686 0495 01
Hi all,
Just so I'm belt and braces on this, I'm working up the dhcpd.conf and dnsmasq.conf files ready for Monday. I'll send these out so that you can all peruse, approve/check my working.
Thanks
Dave
Hello everyone,
during the last month, and also during this one, the Infrastructure
team has been working on a new feature for
linaro-android-media-create.
We are introducing an "Android hardwarepack", similar to the normal
hardwarepack of linaro-media-create, with the difference that the
Android one is just a configuration file, that will store all the
board parameters (instead of having them hard-coded inside the code).
Blueprint, more details and initial code can be found here:
https://blueprints.launchpad.net/linaro-image-tools/+spec/android-media-cre…
We wanted to know what kind of impact these new features might have on
your side and on LAVA.
The old linaro-android-media-create behavior will be maintained (at
least for a while), meaning that it will be possible to run l-a-m-c
without the hwpack file passed on the command line, but in the future
using hwpack will be the default approach.
On the LAVA side, do jobs need to be reconfigured or will this be
transparent for you? Any other things that might broke or change due
to the new features?
Thanks!
--
Milo Casagrande
Infrastructure Engineer
Linaro.org <www.linaro.org> │ Open source software for ARM SoCs
Hello Team,
big.LITTLE MP test execution summary is:
High Lights:
* sched_tests test suite has been executed on mphackbox with latest Android
Image.
On Android:
-----------------
Total Tests = 22
Tests Passed = 16
Tests Failed = 6
Bugs have been created for failed test cases.
Pre-built images are downloaded from
https://android-build.linaro.org/builds/~linaro-android/vexpress-jb-gcc47-a…
Summary of the results can be found in attachments.
Best regards
Naresh Kamboju
Hello,
(please keep me in Cc: on replies as I'm not subscribed to
linaro-android)
I'm working on adding Galaxy Nexus support to LAVA using fastboot. This
is work in progress, but I can already get a full boot test to run on
the Nexus. :-)
I have one question for you.
I noticed that the builds for all other devices are made with tarballs,
and the LAVA jobs for them are also invoked passing tarballs.
The Galaxy Nexus builds, on the other hand, are released as .img files.
May I assume that the LAVA jobs you guys will be submitting for the
Galaxy Nexus will also use .img files (so that I don't need to handle
file format conversion etc), or is it useful for you to submitt tarballs
and have them converted into .img by LAVA? If so, please give me a
pointer with instructions on how to create those .img files.
Best regards,
--
Antonio Terceiro
Software Engineer - Linaro
http://www.linaro.org
Hello Validation team,
Proceeding further with CBuild/LAVA integration work, it's time to
think how to publish gcc, etc. binary tarballs as produced by the
builds. Initially it seemed like an easy step, but the more I think
about it, the more it seems like complicated to do "right".
The tarballs in question are ~100Mb, so I guess there cannot be talk
about publishing them as attachment to a result bundle. Let me know if
that's ok though, because it would resolve all complexities below.
Otherwise, is there a way to set some custom data per user, which would
be available to all jobs submitted by that user - in a secure manner?
The idea, that would be an access credential to use for publishing (so
far we usually use SSH privkey to auth to publishing host).
If not, is there a way to pass such information during job submission,
but again in a secure manner (i.e. it shouldn't be part of job
definition, as that's dumped in plain text).
Any other infrastructure in LAVA (like, pre-authed publishing host) or
suggestions how to solve this?
Thanks,
Paul
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
Hi all,
I've now added 3 routers supporting b, g and n. They are:
LAVA-WiFi-B
Fixed IP address: 192.168.1.17
SSID: LAVA-WiFi-B ChangeHuntDevise
LAVA-WiFi-G
Fixed IP address: 192.168.1.24
SSID: LAVA-WiFi-G DoubleSuezBun
LAVA-WiFi-N
Fixed IP address: 192.168.1.9
SSID: LAVA-Wife-N GeneralWaveFlight
Thanks
Dave