From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: "Luke (Lucas) Starrett" <lstarret@broadcom.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: multi-user shared state
Date: Wed, 10 Jun 2015 14:56:51 -0500 [thread overview]
Message-ID: <55789683.2040704@linux.intel.com> (raw)
In-Reply-To: <DB59870584238C45879465F0A2E5C3F17B01E6@IRVEXCHMB14.corp.ad.broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
Hi Luke,
Comments below,
Best regards,
alimon
[1] https://autobuilder.yoctoproject.org/
[2] http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/
On 10/06/15 14:25, Luke (Lucas) Starrett wrote:
> Hi,
>
> I'm trying to understand the feasibility of shared-state across multiple users in a development environment. Does anyone have first-hand experience with this? Am I asking for trouble?
It is feasible some the sstates can be generated using Yocto Autobuilder
[1] [2] that support setup of various builder machines one as
controller/worker and workers, things to
consider are:
* Network bandwidth: Shared states works good on LAN environments.
* Yocto Autobuilder and Developers Distro's: Shared states generates
packages that are dependent on the distro like native ones, for use
100% of shared state is needed to use the same distro.
>
> If this is expected to work, a secondary question would be whether or not shared-state on a NFS mounted path works. Any thoughts?
The common setup consist in a one machine that acts as a
controller/worker and shared the sstate and downloads to the workers
using NFS for Developer usage it's better to share with
HTTP to avoid problems with the filesystem permissions.
>
> Thanks,
>
> Luke Starrett
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2567 bytes --]
next prev parent reply other threads:[~2015-06-10 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 19:25 multi-user shared state Luke (Lucas) Starrett
2015-06-10 19:56 ` Aníbal Limón [this message]
2015-06-11 14:28 ` Robert Berger
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=55789683.2040704@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=lstarret@broadcom.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.