[Yocto-infrastructure] Infrastructure/shoeleather lab meeting.
Hudson, Sean
Sean_Hudson at mentor.com
Fri Nov 18 13:53:43 PST 2011
Everyone,
Thanks for all who managed to attend on such short notice. For reference and for those who couldn't make it, I have captured notes below from the call.
A couple of administrative things first, if you are interested in continuing to participate, please sign up for the shoeleather mail alias. You can sign up here: https://lists.yoctoproject.org/. The mailer daemon is complaining about too many addresses on the address line and it will help with keeping track of things.
I will be out for vacation next week, so let's try to get together the following week to pick up where we left off. The expectation is that Carlos Hernandez and Paul Larson will have a comparison of LAVA and the TI OpenTest approaches for consideration. Look for a meeting invite for 12/1. Unless there is a strong objection, I will move it an hour later so that the west coast folks won't complain as much. :) I will wait to send it out until I come back from vacation.
Meeting Notes:
Attendees:
Richard Purdie, Dave Stewart, Bill Mills, Jason Kridner, Carlos Hernandez, Paul Larson, Philip Balister, Sean Hudson, Bob Cochran
Action items:
- Sean
- Look at moving deployment to conn-mux
- Investigate the bandwidth available
- Suggestion from Paul was to consider getting a direct and potentially an outside connection
- Carlos/Paul - Work on a side by side7 comparison of Lava/TI connect
- Bill/Jason - Investigate if Beagle XM restarts
Proposal
- Bill pointed out that for the start, we might want to consider using boards that "behave nicely"
to keep things simple/straightforward
Usability challenges:
- resource reservation/allocation
- standing message board (IRC?)
- Web page link to the IRC (webchat.freenode.net)
- improve overall landing page with useful information
Technology challenges:
- USB power/USB serial - (potentially) Need to have a way to control these
- Maybe some sort of homegrown/commercial multiplexer
- serial device # after power cycle
- Visual look at the board
- webcams?
- Hardware probe points?
- e.g. audio input/output
- not thinking about including scope or anaylyzers
- performance on a usb disk
- not planning to tackle it now, but we are open to the prospect
- Ethernet connection for testing?
- bandwidth availability
- fair sharing of bandwidth across boards?
- Bill expressed that having a live ethernet connection is really a must
- question about pocket network inside the lab?
- packet generator, etc
- other option would be to allow an outside connection
- Initial approach proposed would be to dual-home eyelet and add an
ethernet switch to connect target boards together
- Potentially might be extended later
- Image Updates
- Bootloader
- Kernel updates
- root filesystem
Question:
- Scope for the lab?
- testing of hardware in scope or not?
- initially not, but maybe later
- Bandwidth into the lab
- Sean will investigate
- How are boards updated currently?
- Bootloader updates can be sticky
- Linaro working on a generic hardware solution that would help
- What about when the user bricks a board?
- On site (Mobile, AL) will provide some help here
- Currently, no SLA (best effort)
- In addition to having board access, what is the plan long term around submitting jobs?
- Boils down to a roadmap for short term and long term goals
Regards,
Sean
-----Original Appointment-----
From: Hudson, Sean
Sent: Thursday, November 17, 2011 4:42 PM
To: Hudson, Sean; yocto-infrastructure at yoctoproject.org<mailto:yocto-infrastructure at yoctoproject.org>; shoeleather at yoctoproject.org<mailto:shoeleather at yoctoproject.org>; Cherry, John; Darren Hart; Purdie, Richard (richard.purdie at intel.com<mailto:richard.purdie at intel.com>); Stewart, David C (david.c.stewart at intel.com<mailto:david.c.stewart at intel.com>); Bill Mills (wmills at ti.com<mailto:wmills at ti.com>); Jason Kridner (jdk at ti.com<mailto:jdk at ti.com>); Carlos Hernandez; Elizabeth Flanagan (elizabeth.flanagan at intel.com<mailto:elizabeth.flanagan at intel.com>); Ed Nash; Paul Larson; Zygmunt Krynicki (zygmunt.krynicki at linaro.org<mailto:zygmunt.krynicki at linaro.org>); Philip Balister; Osier-mixon, Jeffrey (jeffrey.osier-mixon at intel.com<mailto:jeffrey.osier-mixon at intel.com>); Sean Hudson (shudson at engineer.com<mailto:shudson at engineer.com>)
Subject: Infrastructure/shoeleather lab meeting.
When: Friday, November 18, 2011 9:00 AM-10:00 AM (UTC-06:00) Central Time (US & Canada).
Where: Webex meeting
All,
Sorry for the mass email, but if you are getting this invitation, you are: either on a mailing list, expressed an interest, or were volunteered. Please let me know if you would prefer not to be invited in the future by responding to my mentor.com email or my engineer.com email. Also, please feel free to forward this to anyone that might be interested in attending.
We are overdue for a discussion about the details of the neutral board lab hosted by Mentor Graphics, a.k.a. the shoeleather lab. To get things rolling, I have scheduled a webex session tomorrow to have the call.
Mentor Graphics is still adding to the deployment, but you can request access to the lab by going to this url: http://www.shoeleather-lab.com/
Planned time for the call: 9am US-CST
Meeting info: see below
Tentative agenda:
1) Quick review of the presentation and demo to the YAB
2) Q&A/discussion
Regards,
Sean
Sean Hudson | Embedded Linux Architect, Mentor Embedded Linux
Mentor Embedded<http://www.mentor.com/embedded>(tm)
P 512.539.0230
Nucleus<http://www.mentor.com/embedded-software/nucleus/>(r) | Linux<http://www.mentor.com/embedded-software/linux/>(r) | Android<http://www.mentor.com/embedded-software/android/>(tm) | Services<http://www.mentor.com/embedded-software/services/> | UI<http://www.mentor.com/embedded-software/inflexion/> | Multi-OS<http://www.mentor.com/embedded-software/multicore-multi-os>
Android(tm) is a trademark of Google Inc. Use of this trademark is subject to Google Permissions.
Linux(r) is the registered trademark of Linus Torvalds in the U.S. and other countries.
-+-----+-----+-----+-----+-----+-----+-----+-----+-
[Do not add or change anything below this line. The information in this section may be replaced with your meeting details after you click Send.]
You scheduled this meeting.
Meeting Number: 754 140 163
Meeting Password: yocto
-------------------------------------------------------
To start this meeting
-------------------------------------------------------
1. Go to https://mentor.webex.com/mentor/j.php?J=754140163&PW=NNjE2OThmOGUz
2. If you are not logged in, log in to your account.
-------------------------------------------------------
Audio conference information
-------------------------------------------------------
To receive a call back, provide your phone number when you join the meeting, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): 1-877-668-4490
Call-in toll number (US/Canada): 1-408-792-6300
Toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf
Access code:754 140 163
http://www.webex.com
We've got to start meeting like this(TM)
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. You should inform all meeting attendees prior to recording if you intend to record the meeting. Please note that any such recordings may be subject to discovery in the event of litigation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto-infrastructure/attachments/20111118/2270c02e/attachment.html>
More information about the yocto-infrastructure
mailing list