From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Chris Larson <clarson@kergoth.com>
Cc: yocto <yocto@yoctoproject.org>
Subject: Re: Bitbake and task offloading onto multiple cloud-based servers
Date: Fri, 04 Jan 2013 21:17:43 +0000 [thread overview]
Message-ID: <50E746F7.6000306@dynamicdevices.co.uk> (raw)
In-Reply-To: <CABcZANndjkYoRecpoeUQcUzCevoVqCPWO-EpFCMKSaxh6QFoew@mail.gmail.com>
On 04/01/2013 21:08, Chris Larson wrote:
>
>
> On Fri, Jan 4, 2013 at 1:56 PM, Alex J Lennon
> <ajlennon@dynamicdevices.co.uk <mailto:ajlennon@dynamicdevices.co.uk>>
> wrote:
>
> Can anybody advise on whether bitbake currently supports offloading of
> build tasks onto multiple systems? Perhaps cloud based?
>
> I'm thinking that it would be more efficient for me if I could bring up
> a number of Amazon EC2 servers (or similar) then have bitbake
> parallelise the build onto those servers to significantly reduce my
> build times?
>
> I see bitbake supports a level of task parallelisation on a single box.
>
> Can parallelisation of build onto multiple systems be achieved?
>
> Is it something that should even be a goal?
>
>
> It's not supported today. It could be implemented, but nobody has made
> it a priority and done so.
Do you have any feeling for the level of difficulty of such an
implementation / what would have to change / how invasive it would be to
the codebase ?
I'm wondering if it could be along the lines of creating a "remote task"
class and then, say, having that class ssh into one of a pool of servers
(running a standard image with all tools preinstalled maybe) then
bitbaking the recipes for the particular and waiting on completion
before pulling back the output rpm/deb/ipkg ?
Things are usually more complex than expected when you get into the
nitty gritty though. What would the challenges be do you think?
Where would one start to look in the bitbake code to add this kind of
support in?
Thanks,
Alex
> --
> Christopher Larson
next prev parent reply other threads:[~2013-01-04 21:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 7:37 Fails to launch the hob Biao
2012-12-24 12:23 ` Mihai Lindner
2012-12-24 12:37 ` Mihai Lindner
2012-12-25 6:16 ` Biao
2013-01-03 16:47 ` Barros Pena, Belen
2013-01-03 23:11 ` Zhang, Jessica
2013-01-04 10:10 ` Barros Pena, Belen
2013-01-04 16:57 ` Barros Pena, Belen
2013-01-04 20:56 ` Bitbake and task offloading onto multiple cloud-based servers Alex J Lennon
2013-01-04 21:08 ` Chris Larson
2013-01-04 21:17 ` Alex J Lennon [this message]
2013-01-04 21:27 ` Chris Larson
2013-01-08 23:12 ` Tom Zanussi
2013-01-09 11:58 ` Alex J Lennon
2013-01-09 15:43 ` Tom Zanussi
2013-01-04 22:43 ` Mark Hatle
2013-01-04 22:47 ` Alex J Lennon
2013-01-04 23:14 ` Flanagan, Elizabeth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50E746F7.6000306@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=clarson@kergoth.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.