From: "Ross Burton" <ross.burton@intel.com>
To: yocto@lists.yoctoproject.org
Subject: Re: [yocto] SSTATE_MIRRORS with ssh/sftp fetchers #yocto
Date: Thu, 19 Dec 2019 11:29:45 +0000 [thread overview]
Message-ID: <78ef180e-e66b-07e6-6c57-b106561560ec@intel.com> (raw)
In-Reply-To: <9cb0a929b4b74c114156ad5fd1731b4bd16e8e5d.camel@linuxfoundation.org>
On 19/12/2019 11:16, Richard Purdie wrote:
>> Do you have any idea on how to use these fetchers (or other SSH keys-
>> based secure fetcher) to share sstate cache ?
>
> I think this is a "not implemented" problem.
>
> If you look at bitbake/lib/bb/fetch2/ssh.py or sftp.py, they don't have
> a checkstatus() method that local.py or wget.py has.
>
> I think the sstate code relies on the checkstatus method working to
> know know if an sstate artefact is present.
>
> Performance of that function is key and creating a new ssh connection
> to check for each sstate artefact may make the build prohibitively
> slow. There are some connection caching mechanisms present which may
> help with that.
I actually started implementing this a while ago:
http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=ross/mut2&id=42bdcd8181d2826a5a5dff6803958a900c0c4a2d
I *think* that worked but I can't be sure, it was a while ago and
typically I forgot to put notes to my future self in the commit message.
As RP says, you'll want to use connection sharing: this is configured
using ControlMaster and friends in the ssh configuration. That should
make the performance reasonable.
Ross
next prev parent reply other threads:[~2019-12-19 11:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 10:37 SSTATE_MIRRORS with ssh/sftp fetchers #yocto angeal1105
2019-12-19 11:16 ` [yocto] " Richard Purdie
2019-12-19 11:29 ` Ross Burton [this message]
2019-12-20 9:37 ` angeal1105
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=78ef180e-e66b-07e6-6c57-b106561560ec@intel.com \
--to=ross.burton@intel.com \
--cc=yocto@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox