From: Jean-Marie LEMETAYER <jean-marie.lemetayer@savoirfairelinux.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Connectivity check uris
Date: Thu, 23 Jan 2020 09:59:06 -0500 (EST) [thread overview]
Message-ID: <1908740460.2169186.1579791546237.JavaMail.zimbra@savoirfairelinux.com> (raw)
In-Reply-To: <b1cbeea067af1e54e596425c87b55b36062bb49f.camel@linuxfoundation.org>
On Jan 23, 2020, at 3:37 PM, Richard Purdie richard.purdie@linuxfoundation.org wrote:
> On Thu, 2020-01-23 at 09:22 -0500, Jean-Marie LEMETAYER wrote:
>> I understand the issue with blocked domains this is why I suggest the
>> custom domain "connectivitycheck.openembedded.org".
>>
>> But I dont know if it could be an option. Can OE have a sub-domain
>> like that? maybe using some cdn to handle the load?
>
> We can certainly setup domains but we can't easily get a cdn. I'd be
> worried about OE's response time too.
>
>> Another option will be to provide multiple URIs:
>> CONNECTIVITY_CHECK_URIS ?= " \
>> https://google.com \
>> https://www.bing.com \
>> https://www.baidu.com \
>> "
>
> Looking at the code, I wonder if a CONNECTIVITY_CHECK_MIRRORS, injected
> into MIRRORS internally with google as the default and baidu as the
> mirror would work?
It should work but it will not be efficient as the tries are serially executed.
So someone in China should have to wait that the former domains failed
to be able to start the build.
I am still thinking that the OE subdomain with CDN could be the best option.
Regards,
Jean-Marie
next prev parent reply other threads:[~2020-01-23 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 13:14 Connectivity check uris Jean-Marie LEMETAYER
2020-01-23 13:22 ` Andrey Zhizhikin
2020-01-23 13:26 ` Richard Purdie
2020-01-23 14:22 ` Jean-Marie LEMETAYER
2020-01-23 14:37 ` Richard Purdie
2020-01-23 14:59 ` Jean-Marie LEMETAYER [this message]
2020-01-23 15:23 ` Richard Purdie
2020-01-23 19:25 ` Andre McCurdy
2020-01-24 11:37 ` Jean-Marie LEMETAYER
2020-01-23 13:56 ` Ross Burton
2020-01-23 14:31 ` Jean-Marie LEMETAYER
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=1908740460.2169186.1579791546237.JavaMail.zimbra@savoirfairelinux.com \
--to=jean-marie.lemetayer@savoirfairelinux.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.