[meta-ti] Fw: OpenEmbbedded as a test suite next steps

[Denys Dmytriyenko]

All,

Early planning stages of what's going to be a meta-linaro toolchain layer for 
OE-Core/Yocto. Interesting stuff, we should probably pitch in for some of the 
items there, that we can help with - such as selection of the platforms with 
recent kernels and possibly cloud builds... Any thoughts?

-- 
Denys


----- Forwarded message from Michael Hope <michael.hope at linaro.org> -----

Date: Tue, 6 Mar 2012 13:26:42 +1300
From: Michael Hope <michael.hope at linaro.org>
To: Ken Werner <ken.werner at linaro.org>
Cc: linaro-toolchain at lists.linaro.org
Subject: OpenEmbbedded as a test suite next steps

Hi Ken.  In follow up to our 1-on-1 yesterday, here's what I'd like done next.

The goal is to use OE Core as a release test suite.  The releases are
tarballs so we can keep the current recipe format and punt bzr support
for later.  The first step is to be able to reliably build a release
in the cloud or validation lab.

In all cases keep the other teams in mind.  Much of this is related to
Validation.  Platform will be involved later.  Ping them early.

Kernel:
We're starting with GCC and need a kernel to supply headers and to
boot some type of ARMv7 image.  I don't want a linux-linaro recipe as
people will use it and it's too early for that.

Find a kernel, preferably from OE Core, that is recent, ARMv7, >= 512
MB RAM, and works well with qemu-linaro.  Prefer vexpress-a9, else
OMAP?

Talking:
Say Hi to Validation re: EC2 and plans
Say Hi to the ARM landing team re: vexpress upstream support
Say Hi to Beth Flanagan re: Yocto's existing auto builders and any hints

Cloud builds:
Find out who is already doing OE builds in the cloud and how
Run a build locally and time
Push ~/downloads into the cloud, build, and time[1]
Figure how much this build will cost in dollars

[1] c1.xlarge might be best.  Builds are normally I/O bound and the
cloud is I/O poor.  Put /tmp and other chunks in a tmpfs?  EC2 rounds
up to the nearest hour as well.

If the cloud is too expensive then we'll get a machine installed.

S3 for storage:
(only proceed if affordable)
Use S3 for storing the input tarballs
Use S3 either as a pre-mirror by serving over HTTP, or use s3cmd to
sync down the tarballs before starting the build

Scripting:
Re-use existing scripts if feasible.  Integrate with LAVA providing we
can run exactly the same scripts on a laptop for debugging.

Script the bitbake, OE meta layer, and Linaro meta layer setup.
Script the configuration including setting the release tarball URL and
GCC preferred version.
Script the build and result capture, especially the log, any ICEs, and
the final sizes

Future:
OE can grab a repository seed then update based on that.  Check if the
bzr backend supports this.  If so, play with seeding to do tip builds.

Let me know what you think then we'll spawn blueprints.  Let's keep an
eye on this as it's sounding expensive.

-- Michael

_______________________________________________
linaro-toolchain mailing list
linaro-toolchain at lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


----- End forwarded message -----