On Thu, 2020-01-23 at 09:59 -0500, Jean-Marie LEMETAYER wrote: > On Jan 23, 2020, at 3:37 PM, Richard Purdie > [email protected] 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'm guessing those wouldn't resolve so it should be pretty fast? Maybe we make the configuration more obvious in local.conf? > I am still thinking that the OE subdomain with CDN could be the best > option. Sure, but who is going to pay for and maintain a CDN setup? Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
