On Thu, 31 Oct 2013 09:14:47 +0200 Ayman Hendawy ayman.hendawy@gmail.com wrote:
Dear Neil,
Do not reply to individuals. Keep replies only to the list.
Actually I wonder why it's not more open, why I can't get a real time access to the kit serial console, why debugger is not available, suppose I have an application over OS, I need to debug my code using a debugger, to get know the certain line causing the problem, why I don't have an access to some of the kit peripherals like USB port by some how.
What I mean, such great effort of LAVA, what limit it to give there users more deeply access to there kits? why it's limited to posting jobs?
The simple answer is that this is to protect the use of the boards by other users. Submitting a job puts the device into a test image where the bugs in the test image are restricted to that test image. When the test ends (for better or for worse), the board returns to a known, working, state.
To do otherwise would make the admin burden unsustainable.
These are not general purpose debugging boards. These are test devices. The hands-on debugging needs to be done in emulators or local boards - preferably before the commits. LAVA is checking for side-effects of developer changes, especially performance changes over time.
Access to the serial console of any LAVA device is restricted to the lab admins. The devices do not belong to the developers, it isn't about developers having access to "their" devices. The devices belong to LAVA and are maintained as a service for all developers. Doing that requires that LAVA imposes restrictions on what individual developers can do to avoid individuals leaving the device in an unstable or unbootable state.
Many LAVA test jobs involve interim kernel builds - it is all too easy to make a commit which gets turned into a LAVA job which leads to a kernel panic in the test. If that was the main kernel for the device, *someone* (i.e. the LAVA lab admins) would have to fix it. Restricting tests to submitted jobs is that fix.
On 31 Oct 2013, at 08:42, Neil Williams codehelp@debian.org wrote:
On Thu, 31 Oct 2013 09:14:47 +0200 Ayman Hendawy ayman.hendawy@gmail.com wrote:
Dear Neil,
Do not reply to individuals. Keep replies only to the list.
Actually I wonder why it's not more open, why I can't get a real time access to the kit serial console, why debugger is not available, suppose I have an application over OS, I need to debug my code using a debugger, to get know the certain line causing the problem, why I don't have an access to some of the kit peripherals like USB port by some how.
What I mean, such great effort of LAVA, what limit it to give there users more deeply access to there kits? why it's limited to posting jobs?
To add to what Neil said:
The LAVA lab farm, which is what validation.linaro.org gives access to, is an automated test environment. The point of Linaro is to provide constantly improving Linux distributions, and part of this effort is to test changes automatically in LAVA - the Linaro Automated Validation Architecture. So the lab is all about automation, not about free access to hardware. It is a service that is only available to members and Linaro engineers. You have to understand that we are a not-for-profit organisation that is funded by its members. If we granted open access to the world, we would be giving the potential for commercial competitors to gain access to advanced and restricted hardware.
Linaro is an Open Source Software company - and indeed every line of code we generate is available freely and openly. We are not an Open Access Hardware Service.
If you are a Linaro assignee, or have a reason why you would need access that our Technical Steering Committee (TSC) agree to, then we can grant you access to be able to submit jobs into the Automated Validation framework, to a subset of devices in the validation farm - some devices are restricted because they are advanced hardware or emulations of silicon that have not yet been made commercially available and our members would not be very pleased if open access was granted.
So, in summary, the action that you must take is to provide us with information on why you need access to the LAVA farm and we will forward this onto the Linaro TSC.
Kind regards
Dave Pigott LAVA Lab Lead
Hi,
Thanks for your detailed reply, I'm asking this question, because I was thinking about creating an open source Remote Embedded Lab, where developers have access to many open source kits(e.g, Panda, Beagle, Ethernut, etc.) remotely, plus remote access to the measurement tools in this lab (e.g, oscilloscope, Logic analyzer, etc.) connected to this kits, I think something like that will have a great impact on embedded system world especially open source software developers, every developer like to have his own lab, buying new kits& measurement tools is expensive.
My preliminary thought is to give the user a full access to there remote kits, through Ethernet JTAG and other tools, where the user is responsible for every thing, burn the bootloader, program SD Card, the connection between the measurement tools and the kits can be done by many ways (like multiplexer) and to be configured through web interface.
So I searched the web for a similar solution, providing H.W remote access, and I found your team, doing it but in a different way of may thought, so I need to understand the limitations and possibilities to doing so, if we give the user access to a full access via JTAGs is this may cause a problem to the kits.
Now I hope you understand my full idea, kindly I would like to hear you suggestions to do so.
Thanks
On Thu, Oct 31, 2013 at 7:37 PM, Dave Pigott dave.pigott@linaro.org wrote:
On 31 Oct 2013, at 08:42, Neil Williams codehelp@debian.org wrote:
On Thu, 31 Oct 2013 09:14:47 +0200 Ayman Hendawy ayman.hendawy@gmail.com wrote:
Dear Neil,
Do not reply to individuals. Keep replies only to the list.
Actually I wonder why it's not more open, why I can't get a real time access to the kit serial console, why debugger is not available, suppose I have an application over OS, I need to debug my code using a debugger, to get know the certain line causing the problem, why I don't have an access to some of the kit peripherals like USB port by some how.
What I mean, such great effort of LAVA, what limit it to give there users more deeply access to there kits? why it's limited to posting jobs?
To add to what Neil said:
The LAVA lab farm, which is what validation.linaro.org gives access to, is an automated test environment. The point of Linaro is to provide constantly improving Linux distributions, and part of this effort is to test changes automatically in LAVA - the Linaro Automated Validation Architecture. So the lab is all about automation, not about free access to hardware. It is a service that is only available to members and Linaro engineers. You have to understand that we are a not-for-profit organisation that is funded by its members. If we granted open access to the world, we would be giving the potential for commercial competitors to gain access to advanced and restricted hardware.
Linaro is an Open Source Software company - and indeed every line of code we generate is available freely and openly. We are not an Open Access Hardware Service.
If you are a Linaro assignee, or have a reason why you would need access that our Technical Steering Committee (TSC) agree to, then we can grant you access to be able to submit jobs into the Automated Validation framework, to a subset of devices in the validation farm - some devices are restricted because they are advanced hardware or emulations of silicon that have not yet been made commercially available and our members would not be very pleased if open access was granted.
So, in summary, the action that you must take is to provide us with information on why you need access to the LAVA farm and we will forward this onto the Linaro TSC.
Kind regards
Dave Pigott LAVA Lab Lead
Hi,
Kindly, could I get your reply on my previous e-mail.
Thanks
On Fri, Nov 1, 2013 at 9:57 AM, Ayman Hendawy ayman.hendawy@gmail.comwrote:
Hi,
Thanks for your detailed reply, I'm asking this question, because I was thinking about creating an open source Remote Embedded Lab, where developers have access to many open source kits(e.g, Panda, Beagle, Ethernut, etc.) remotely, plus remote access to the measurement tools in this lab (e.g, oscilloscope, Logic analyzer, etc.) connected to this kits, I think something like that will have a great impact on embedded system world especially open source software developers, every developer like to have his own lab, buying new kits& measurement tools is expensive.
My preliminary thought is to give the user a full access to there remote kits, through Ethernet JTAG and other tools, where the user is responsible for every thing, burn the bootloader, program SD Card, the connection between the measurement tools and the kits can be done by many ways (like multiplexer) and to be configured through web interface.
So I searched the web for a similar solution, providing H.W remote access, and I found your team, doing it but in a different way of may thought, so I need to understand the limitations and possibilities to doing so, if we give the user access to a full access via JTAGs is this may cause a problem to the kits.
Now I hope you understand my full idea, kindly I would like to hear you suggestions to do so.
Thanks
On Thu, Oct 31, 2013 at 7:37 PM, Dave Pigott dave.pigott@linaro.orgwrote:
On 31 Oct 2013, at 08:42, Neil Williams codehelp@debian.org wrote:
On Thu, 31 Oct 2013 09:14:47 +0200 Ayman Hendawy ayman.hendawy@gmail.com wrote:
Dear Neil,
Do not reply to individuals. Keep replies only to the list.
Actually I wonder why it's not more open, why I can't get a real time access to the kit serial console, why debugger is not available, suppose I have an application over OS, I need to debug my code using a debugger, to get know the certain line causing the problem, why I don't have an access to some of the kit peripherals like USB port by some how.
What I mean, such great effort of LAVA, what limit it to give there users more deeply access to there kits? why it's limited to posting jobs?
To add to what Neil said:
The LAVA lab farm, which is what validation.linaro.org gives access to, is an automated test environment. The point of Linaro is to provide constantly improving Linux distributions, and part of this effort is to test changes automatically in LAVA - the Linaro Automated Validation Architecture. So the lab is all about automation, not about free access to hardware. It is a service that is only available to members and Linaro engineers. You have to understand that we are a not-for-profit organisation that is funded by its members. If we granted open access to the world, we would be giving the potential for commercial competitors to gain access to advanced and restricted hardware.
Linaro is an Open Source Software company - and indeed every line of code we generate is available freely and openly. We are not an Open Access Hardware Service.
If you are a Linaro assignee, or have a reason why you would need access that our Technical Steering Committee (TSC) agree to, then we can grant you access to be able to submit jobs into the Automated Validation framework, to a subset of devices in the validation farm - some devices are restricted because they are advanced hardware or emulations of silicon that have not yet been made commercially available and our members would not be very pleased if open access was granted.
So, in summary, the action that you must take is to provide us with information on why you need access to the LAVA farm and we will forward this onto the Linaro TSC.
Kind regards
Dave Pigott LAVA Lab Lead
-- Best regards
Ayman Hendawy Embedded system engineer http://www.linkedin.com/pub/ayman-hendawy/28/375/b5
Cairo,Egypt
Phone: +201110406659
Hi Ayman,
We've all been at a very busy Linaro Connect event in San Francisco, as Neil told you in a previous email, and I only just got back home an hour ago. I think you might be being a little unreasonable expecting a coherent response at this time. I'm back in the office on tuesday, and will deal with your response then.
Regards
Dave
Sent from my Aldis Lamp
On 3 Nov 2013, at 09:10, Ayman Hendawy ayman.hendawy@gmail.com wrote:
Hi,
Kindly, could I get your reply on my previous e-mail.
Thanks
On Fri, Nov 1, 2013 at 9:57 AM, Ayman Hendawy ayman.hendawy@gmail.com wrote: Hi,
Thanks for your detailed reply, I'm asking this question, because I was thinking about creating an open source Remote Embedded Lab, where developers have access to many open source kits(e.g, Panda, Beagle, Ethernut, etc.) remotely, plus remote access to the measurement tools in this lab (e.g, oscilloscope, Logic analyzer, etc.) connected to this kits, I think something like that will have a great impact on embedded system world especially open source software developers, every developer like to have his own lab, buying new kits& measurement tools is expensive.
My preliminary thought is to give the user a full access to there remote kits, through Ethernet JTAG and other tools, where the user is responsible for every thing, burn the bootloader, program SD Card, the connection between the measurement tools and the kits can be done by many ways (like multiplexer) and to be configured through web interface.
So I searched the web for a similar solution, providing H.W remote access, and I found your team, doing it but in a different way of may thought, so I need to understand the limitations and possibilities to doing so, if we give the user access to a full access via JTAGs is this may cause a problem to the kits.
Now I hope you understand my full idea, kindly I would like to hear you suggestions to do so.
Thanks
On Thu, Oct 31, 2013 at 7:37 PM, Dave Pigott dave.pigott@linaro.org wrote:
On 31 Oct 2013, at 08:42, Neil Williams codehelp@debian.org wrote:
On Thu, 31 Oct 2013 09:14:47 +0200 Ayman Hendawy ayman.hendawy@gmail.com wrote:
Dear Neil,
Do not reply to individuals. Keep replies only to the list.
Actually I wonder why it's not more open, why I can't get a real time access to the kit serial console, why debugger is not available, suppose I have an application over OS, I need to debug my code using a debugger, to get know the certain line causing the problem, why I don't have an access to some of the kit peripherals like USB port by some how.
What I mean, such great effort of LAVA, what limit it to give there users more deeply access to there kits? why it's limited to posting jobs?
To add to what Neil said:
The LAVA lab farm, which is what validation.linaro.org gives access to, is an automated test environment. The point of Linaro is to provide constantly improving Linux distributions, and part of this effort is to test changes automatically in LAVA - the Linaro Automated Validation Architecture. So the lab is all about automation, not about free access to hardware. It is a service that is only available to members and Linaro engineers. You have to understand that we are a not-for-profit organisation that is funded by its members. If we granted open access to the world, we would be giving the potential for commercial competitors to gain access to advanced and restricted hardware.
Linaro is an Open Source Software company - and indeed every line of code we generate is available freely and openly. We are not an Open Access Hardware Service.
If you are a Linaro assignee, or have a reason why you would need access that our Technical Steering Committee (TSC) agree to, then we can grant you access to be able to submit jobs into the Automated Validation framework, to a subset of devices in the validation farm - some devices are restricted because they are advanced hardware or emulations of silicon that have not yet been made commercially available and our members would not be very pleased if open access was granted.
So, in summary, the action that you must take is to provide us with information on why you need access to the LAVA farm and we will forward this onto the Linaro TSC.
Kind regards
Dave Pigott LAVA Lab Lead
-- Best regards
Ayman Hendawy Embedded system engineer http://www.linkedin.com/pub/ayman-hendawy/28/375/b5
Cairo,Egypt
Phone: +201110406659
-- Best regards
Ayman Hendawy Embedded system engineer http://www.linkedin.com/pub/ayman-hendawy/28/375/b5
Cairo,Egypt
Phone: +201110406659
Hi Ayman,
Basically, you just need to set up a LAVA lab, and allow users to submit "hacking session" jobs. The LAVA scheduler then sets up the required image and sets up an ssh session and gives the user information on how to ssh into the board. You'd also need to set up a server for people to ssh into - they could then use ssh forwarding to get onto the board. To provide serial access, you'd need to set up a serial console server. Then the user could ssh onto the server and use the "lava connect" command to get serial access.
This is all detailed in our documentation, currently on playground.validation.linaro.org, although that is still a work in progress - in fact it was the main focus of our work in San Francisco last week.
Hope this helps
Dave
On 1 Nov 2013, at 07:57, Ayman Hendawy ayman.hendawy@gmail.com wrote:
Hi,
Thanks for your detailed reply, I'm asking this question, because I was thinking about creating an open source Remote Embedded Lab, where developers have access to many open source kits(e.g, Panda, Beagle, Ethernut, etc.) remotely, plus remote access to the measurement tools in this lab (e.g, oscilloscope, Logic analyzer, etc.) connected to this kits, I think something like that will have a great impact on embedded system world especially open source software developers, every developer like to have his own lab, buying new kits& measurement tools is expensive.
My preliminary thought is to give the user a full access to there remote kits, through Ethernet JTAG and other tools, where the user is responsible for every thing, burn the bootloader, program SD Card, the connection between the measurement tools and the kits can be done by many ways (like multiplexer) and to be configured through web interface.
So I searched the web for a similar solution, providing H.W remote access, and I found your team, doing it but in a different way of may thought, so I need to understand the limitations and possibilities to doing so, if we give the user access to a full access via JTAGs is this may cause a problem to the kits.
Now I hope you understand my full idea, kindly I would like to hear you suggestions to do so.
Thanks
On Thu, Oct 31, 2013 at 7:37 PM, Dave Pigott dave.pigott@linaro.org wrote:
On 31 Oct 2013, at 08:42, Neil Williams codehelp@debian.org wrote:
On Thu, 31 Oct 2013 09:14:47 +0200 Ayman Hendawy ayman.hendawy@gmail.com wrote:
Dear Neil,
Do not reply to individuals. Keep replies only to the list.
Actually I wonder why it's not more open, why I can't get a real time access to the kit serial console, why debugger is not available, suppose I have an application over OS, I need to debug my code using a debugger, to get know the certain line causing the problem, why I don't have an access to some of the kit peripherals like USB port by some how.
What I mean, such great effort of LAVA, what limit it to give there users more deeply access to there kits? why it's limited to posting jobs?
To add to what Neil said:
The LAVA lab farm, which is what validation.linaro.org gives access to, is an automated test environment. The point of Linaro is to provide constantly improving Linux distributions, and part of this effort is to test changes automatically in LAVA - the Linaro Automated Validation Architecture. So the lab is all about automation, not about free access to hardware. It is a service that is only available to members and Linaro engineers. You have to understand that we are a not-for-profit organisation that is funded by its members. If we granted open access to the world, we would be giving the potential for commercial competitors to gain access to advanced and restricted hardware.
Linaro is an Open Source Software company - and indeed every line of code we generate is available freely and openly. We are not an Open Access Hardware Service.
If you are a Linaro assignee, or have a reason why you would need access that our Technical Steering Committee (TSC) agree to, then we can grant you access to be able to submit jobs into the Automated Validation framework, to a subset of devices in the validation farm - some devices are restricted because they are advanced hardware or emulations of silicon that have not yet been made commercially available and our members would not be very pleased if open access was granted.
So, in summary, the action that you must take is to provide us with information on why you need access to the LAVA farm and we will forward this onto the Linaro TSC.
Kind regards
Dave Pigott LAVA Lab Lead
-- Best regards
Ayman Hendawy Embedded system engineer http://www.linkedin.com/pub/ayman-hendawy/28/375/b5
Cairo,Egypt
Phone: +201110406659
Hi,
Thanks Dave for your reply, But what if I give to the users a more deeply access via JTAG, could it be unsafe for the board to get damaged, what cautions we have to consider when we are doing that?
Thanks
On Mon, Nov 4, 2013 at 11:59 AM, Dave Pigott dave.pigott@linaro.org wrote:
Hi Ayman,
Basically, you just need to set up a LAVA lab, and allow users to submit "hacking session" jobs. The LAVA scheduler then sets up the required image and sets up an ssh session and gives the user information on how to ssh into the board. You'd also need to set up a server for people to ssh into - they could then use ssh forwarding to get onto the board. To provide serial access, you'd need to set up a serial console server. Then the user could ssh onto the server and use the "lava connect" command to get serial access.
This is all detailed in our documentation, currently on playground.validation.linaro.org, although that is still a work in progress - in fact it was the main focus of our work in San Francisco last week.
Hope this helps
Dave
On 1 Nov 2013, at 07:57, Ayman Hendawy ayman.hendawy@gmail.com wrote:
Hi,
Thanks for your detailed reply, I'm asking this question, because I was thinking about creating an open source Remote Embedded Lab, where developers have access to many open source kits(e.g, Panda, Beagle, Ethernut, etc.) remotely, plus remote access to the measurement tools in this lab (e.g, oscilloscope, Logic analyzer, etc.) connected to this kits, I think something like that will have a great impact on embedded system world especially open source software developers, every developer like to have his own lab, buying new kits& measurement tools is expensive.
My preliminary thought is to give the user a full access to there remote kits, through Ethernet JTAG and other tools, where the user is responsible for every thing, burn the bootloader, program SD Card, the connection between the measurement tools and the kits can be done by many ways (like multiplexer) and to be configured through web interface.
So I searched the web for a similar solution, providing H.W remote access, and I found your team, doing it but in a different way of may thought, so I need to understand the limitations and possibilities to doing so, if we give the user access to a full access via JTAGs is this may cause a problem to the kits.
Now I hope you understand my full idea, kindly I would like to hear you suggestions to do so.
Thanks
On Thu, Oct 31, 2013 at 7:37 PM, Dave Pigott dave.pigott@linaro.orgwrote:
On 31 Oct 2013, at 08:42, Neil Williams codehelp@debian.org wrote:
On Thu, 31 Oct 2013 09:14:47 +0200 Ayman Hendawy ayman.hendawy@gmail.com wrote:
Dear Neil,
Do not reply to individuals. Keep replies only to the list.
Actually I wonder why it's not more open, why I can't get a real time access to the kit serial console, why debugger is not available, suppose I have an application over OS, I need to debug my code using a debugger, to get know the certain line causing the problem, why I don't have an access to some of the kit peripherals like USB port by some how.
What I mean, such great effort of LAVA, what limit it to give there users more deeply access to there kits? why it's limited to posting jobs?
To add to what Neil said:
The LAVA lab farm, which is what validation.linaro.org gives access to, is an automated test environment. The point of Linaro is to provide constantly improving Linux distributions, and part of this effort is to test changes automatically in LAVA - the Linaro Automated Validation Architecture. So the lab is all about automation, not about free access to hardware. It is a service that is only available to members and Linaro engineers. You have to understand that we are a not-for-profit organisation that is funded by its members. If we granted open access to the world, we would be giving the potential for commercial competitors to gain access to advanced and restricted hardware.
Linaro is an Open Source Software company - and indeed every line of code we generate is available freely and openly. We are not an Open Access Hardware Service.
If you are a Linaro assignee, or have a reason why you would need access that our Technical Steering Committee (TSC) agree to, then we can grant you access to be able to submit jobs into the Automated Validation framework, to a subset of devices in the validation farm - some devices are restricted because they are advanced hardware or emulations of silicon that have not yet been made commercially available and our members would not be very pleased if open access was granted.
So, in summary, the action that you must take is to provide us with information on why you need access to the LAVA farm and we will forward this onto the Linaro TSC.
Kind regards
Dave Pigott LAVA Lab Lead
-- Best regards
Ayman Hendawy Embedded system engineer http://www.linkedin.com/pub/ayman-hendawy/28/375/b5
Cairo,Egypt
Phone: +201110406659
Hi Ayman,
Sorry it's taking so long to reply. We are unbelievably busy, so spare cycles are few and far between.
A general comment, and a lesson we learned in setting up and maintaining the LAVA Lab, is that if you enable people to do things that could disrupt a board, or your infrastructure, then they will do that. You have to design your lab to be incredibly tolerant to things like:
(a) a machine getting bricked - always have a way to recover it without manual intervention (b) your network doesn't fall over if a rival dhcp or dns service suddenly appears
There are many such lessons we've learned over the years, and I'm happy to occasionally provide guidance, but that isn't really my day job, so my attention will be limited.
Thanks
Dave
On 5 Nov 2013, at 06:45, Ayman Hendawy ayman.hendawy@gmail.com wrote:
Hi,
Thanks Dave for your reply, But what if I give to the users a more deeply access via JTAG, could it be unsafe for the board to get damaged, what cautions we have to consider when we are doing that?
Thanks
On Mon, Nov 4, 2013 at 11:59 AM, Dave Pigott dave.pigott@linaro.org wrote: Hi Ayman,
Basically, you just need to set up a LAVA lab, and allow users to submit "hacking session" jobs. The LAVA scheduler then sets up the required image and sets up an ssh session and gives the user information on how to ssh into the board. You'd also need to set up a server for people to ssh into - they could then use ssh forwarding to get onto the board. To provide serial access, you'd need to set up a serial console server. Then the user could ssh onto the server and use the "lava connect" command to get serial access.
This is all detailed in our documentation, currently on playground.validation.linaro.org, although that is still a work in progress - in fact it was the main focus of our work in San Francisco last week.
Hope this helps
Dave
On 1 Nov 2013, at 07:57, Ayman Hendawy ayman.hendawy@gmail.com wrote:
Hi,
Thanks for your detailed reply, I'm asking this question, because I was thinking about creating an open source Remote Embedded Lab, where developers have access to many open source kits(e.g, Panda, Beagle, Ethernut, etc.) remotely, plus remote access to the measurement tools in this lab (e.g, oscilloscope, Logic analyzer, etc.) connected to this kits, I think something like that will have a great impact on embedded system world especially open source software developers, every developer like to have his own lab, buying new kits& measurement tools is expensive.
My preliminary thought is to give the user a full access to there remote kits, through Ethernet JTAG and other tools, where the user is responsible for every thing, burn the bootloader, program SD Card, the connection between the measurement tools and the kits can be done by many ways (like multiplexer) and to be configured through web interface.
So I searched the web for a similar solution, providing H.W remote access, and I found your team, doing it but in a different way of may thought, so I need to understand the limitations and possibilities to doing so, if we give the user access to a full access via JTAGs is this may cause a problem to the kits.
Now I hope you understand my full idea, kindly I would like to hear you suggestions to do so.
Thanks
On Thu, Oct 31, 2013 at 7:37 PM, Dave Pigott dave.pigott@linaro.org wrote:
On 31 Oct 2013, at 08:42, Neil Williams codehelp@debian.org wrote:
On Thu, 31 Oct 2013 09:14:47 +0200 Ayman Hendawy ayman.hendawy@gmail.com wrote:
Dear Neil,
Do not reply to individuals. Keep replies only to the list.
Actually I wonder why it's not more open, why I can't get a real time access to the kit serial console, why debugger is not available, suppose I have an application over OS, I need to debug my code using a debugger, to get know the certain line causing the problem, why I don't have an access to some of the kit peripherals like USB port by some how.
What I mean, such great effort of LAVA, what limit it to give there users more deeply access to there kits? why it's limited to posting jobs?
To add to what Neil said:
The LAVA lab farm, which is what validation.linaro.org gives access to, is an automated test environment. The point of Linaro is to provide constantly improving Linux distributions, and part of this effort is to test changes automatically in LAVA - the Linaro Automated Validation Architecture. So the lab is all about automation, not about free access to hardware. It is a service that is only available to members and Linaro engineers. You have to understand that we are a not-for-profit organisation that is funded by its members. If we granted open access to the world, we would be giving the potential for commercial competitors to gain access to advanced and restricted hardware.
Linaro is an Open Source Software company - and indeed every line of code we generate is available freely and openly. We are not an Open Access Hardware Service.
If you are a Linaro assignee, or have a reason why you would need access that our Technical Steering Committee (TSC) agree to, then we can grant you access to be able to submit jobs into the Automated Validation framework, to a subset of devices in the validation farm - some devices are restricted because they are advanced hardware or emulations of silicon that have not yet been made commercially available and our members would not be very pleased if open access was granted.
So, in summary, the action that you must take is to provide us with information on why you need access to the LAVA farm and we will forward this onto the Linaro TSC.
Kind regards
Dave Pigott LAVA Lab Lead
-- Best regards
Ayman Hendawy Embedded system engineer http://www.linkedin.com/pub/ayman-hendawy/28/375/b5
Cairo,Egypt
Phone: +201110406659
-- Best regards
Ayman Hendawy Embedded system engineer http://www.linkedin.com/pub/ayman-hendawy/28/375/b5
Cairo,Egypt
Phone: +201110406659
linaro-validation@lists.linaro.org
-
Ayman Hendawy -
Dave Pigott -
Neil Williams