[Meego-qa] On OTS and ots.meego.com
may.xie at intel.com
Thu Dec 23 17:22:33 PST 2010
Some issues have been already discussed on IRC. For sure, we will continue discussing them on IRC.
However, simply from process perspective, should QA tool team follow MeeGo bug triage process to start to triage QA tools feature/bugs? A few bugs for 2 months without any update? Would you start IRC bug triage for QA tools bugs, so we can participate in?
ville.p.ilvonen at nokia.com <mailto:ville.p.ilvonen at nokia.com> scribbled on Thursday, December 23, 2010 9:09 PM:
> I agree.
> We'd better let Jerry and Wang take care of those with other
> Take care,
> -----Original Message-----
> From: meego-qa-bounces at lists.meego.com
> [mailto:meego-qa-bounces at lists.meego.com] On Behalf Of ext Timo
> Mäkimattila Sent: 23. joulukuuta 2010 13:40
> To: Xie, May
> Cc: meego-qa at lists.meego.com
> Subject: Re: [Meego-qa] On OTS and ots.meego.com
> I'd like to invite also Intel people using or developing QA Tools to
> irc.freenode.net #meego-qa-tools channel. There's very active
> going on about the tools. I'm sure we'd find many common interests and
> possibilities to contribute to QA Tools if we just have direct and
> discussion between the developers.
> On Wed, 2010-12-22 at 16:34 +0200, Xie, May wrote:
>> MeeGo QA team would like to get OTS ready for daily testing for
>> trunk:testing and trunk on all the MeeGo devices. Let me repeat the
>> gaps/issues here: - 1) Daily image from release engineering cannot
>> run due to lacking of test pacakges and SSH key. Bug to track the
>> issue: http://bugs.meego.com/show_bug.cgi?id=11577. If release
>> engineering won't include them in daily TT and trunk image, should
>> OTS be enhanced to be able to test daily image?
>> 2) Only Raw Image Format can run on OTS, this is for sure not
>> problem for handset image, but IVI and Netbook daily image are
>> squashfs livecd from release engineering as a result, they cannot
>> run on OTS. We are trying to workaround the issue through Service OS
>> based flasher, but this is really not generic solution! Bug for this
>> issue: http://bugs.meego.com/show_bug.cgi?id=8778.
>> 3) OTS executed tests by ssh connection remotely, it relys on
>> netbook, so some network related tests cannot run on OTS.
>> Pls. help provide constructive solution for the issues above. Some
>> bugs are there for 2 months without any comments, would you like to
>> follow MeeGo bug triage process to triage QA tools bugs?
>> FYI - We are working on flasher for Netbook, IVI and iCDK.
>> -----Original Message-----
>> From: meego-qa-bounces at lists.meego.com
>> [mailto:meego-qa-bounces at lists.meego.com] On Behalf Of Ville Ilvonen
>> Sent: Wednesday, December 22, 2010 7:33 PM
>> To: meego-qa at lists.meego.com; Mosconi Stefano (Nokia-D/Helsinki);
>> Gretzinger, Adam R; ivanov.maxim at gmail.com
>> Subject: [Meego-qa] On OTS and ots.meego.com
>> Hi all,
>> There has been discussion around automated testing and OTS in
>> Dublin, in
>> Quality project meetings and I've received awful lot of queries in
>> and mail. I try to address open questions in this open info and won't
>> answer all your email, sorry.
>> == On OTS tool and support ==
>> OTS is software to run automated testing - this means unattended
>> release installation, test package execution and reporting. All of
>> is done in target device (like N900, netbook, etc.). OTS is available
>> (1) for anyone to setup. Why would we want to do such thing? Nightly
>> hourly testing of same tests becomes very easily time not well-spent
>> we want to allow testers to focus on something more fruitful.
>> We provide support at #meego-qa-tools with best effort - I want to
>> that and our QA tools related discussion open so I've instructed our
>> developers not to answer personal queries but use all public channels
>> available (irc, bugs.meego.com, meego-qa at lists.meego.com). So if your
>> personal emails to me or QA tools developers remain unanswered it's
>> personal, you're just not working the MeeGo way in open. We can also
>> already answered emails, irc logs and so on when people are asking
>> same questions again. That applies to all QA-tools though.
>> I don't want to promise any fast lanes or priviledge support for
>> anyone - nor our fellows at Intel, nor to distinguished community
>> people. I
>> must provide it to my employer though because my boss tells me so.
>> So if
>> you don't play it the MeeGo way I'm likely not going to help you.
>> == On ots.meego.com test cloud ==
>> ots.meego.com is _service_, test cloud, which at current state
>> of OTS server and OTS workers with N900s. It's public service and
>> supports public MeeGo reference devices. The idea of ots.meego.com
>> is best described at
>> I have set that up with great help from MeeGo IT (Stefano Mosconi,
>> Ivanov), Intel System Administration (Adam Gretzinger) and QA tools
>> developers (Teemu Vainio, Timo Härkönen). It's being hosted at the
>> premises as all the other MeeGo infrastructure - OSU. I really wish
>> can setup similar for community as well - those devices are reserved
>> MeeGo program test teams to use.
>> We plan to publish automated results directly to
>> That should happen during January.
>> I'm not planning to coordinate your plans to setup more HW there -
>> can do that directly with MeeGo IT. Not that I wouldn't want to help
>> you - I want to avoid becoming a request/email hub and further
>> for MeeGo.
>> Currently public OTS meego-autoinstaller supports Handset (N900) and
>> Netbook (ia32 generic, manufacturer-specific). Regarding general
>> please refer to mine and Timo's presentation at Dublin (2). If you
>> to use automated MeeGo release installation with your favorite device
>> your HW manufacturer must support the following three things:
>> 1. Option to boot-up automatically
>> - e.g. flasher flag /w N900
>> - Wake-up-on-LAN (WOL) with netbooks (or controlled power switch)
>> 2. Option to write OS (operating system) remotely
>> - this is done differently with different HW
>> - see meego-ai (3) to get the idea
>> 3. Option to control power supply
>> - this allows installation automation and reliable recovery in
>> case of problems
>> This has been tested with several different devices over time. I'd
>> to say those apply pretty universally. If you want your device to
>> support automated testing you must support those things so please
>> contact your favorite device manufacturer for that.
>> == On ots.meego.com openess ==
>> ots.meego.com is public but it's not accessible for all as in "you
>> log on to that server over SSH". We won't provide access to anyone -
>> also OTS remote API usage will be limited to MeeGo release
>> from build.meego.com. Exceptions are of course possible, use
>> bugs.meego.com to request those. Currently it looks like we will
>> ots.meego.com access the same way as build.meego.com. There's also
>> discussion to setup community OTS anyone could connect their test
>> environments to.
>> That should cover all the open questions and big picture. If not,
>> reply to this mailing list and ask.
>> (1) http://wiki.meego.com/Quality/QA-tools/OTS
>> slide 7
>> (3) http://gitorious.org/qa-tools/meego-ai
>> MeeGo-qa mailing list
>> MeeGo-qa at lists.meego.com
>> MeeGo-qa mailing list
>> MeeGo-qa at lists.meego.com
> MeeGo-qa mailing list
> MeeGo-qa at lists.meego.com
More information about the MeeGo-qa