From: Michael Halstead <michael@yoctoproject.org>
To: yocto@yoctoproject.org
Subject: [Infra] Network home directories
Date: Tue, 15 May 2012 16:54:33 -0700 [thread overview]
Message-ID: <4FB2ECB9.2020200@yoctoproject.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
Problems:
Moving files between builders requires copying them to localhost and
back (slow) or forwarding your ssh-agent around (poor security).
Different amounts of free local storage mean pokybuild has different
size constraints on different builders which isn't helpful.
Solution:
Beth and I propose that we mount user home directories from the NAS on
the autobuilder stack so that user files are shared across the build
infrastructure. We will keep a copy of bare home directories with ssh
keys on the filesystem below the network mount so that logins will
continue to function even during a NAS outage.
Interruption:
Setting this up requires moving user home directories from /srv and
consolidating the data. This wouldn't interrupt the builders but would
keep some users from logging in for several minutes.
What we gain:
This offers the benefit of shared files across the builders as well as
keeping the local disk free for poky builds. It allows easy tear-down
and rebuilding of slave hosts because unique data is separated from
local storage.
Does this break anyone's existing workflow? Any other concerns?
Michael Halstead
Yocto Project / Sys Admin
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4464 bytes --]
reply other threads:[~2012-05-15 23:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FB2ECB9.2020200@yoctoproject.org \
--to=michael@yoctoproject.org \
--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.