Jeremiah wrote:
There are some folks who're will to mirror our PureOS distro which is very generous of them.
Alas, I fear this is a bigger question that just rsync daemon settings. :) Whilst extremely kind of them, how will this work for our users? Ask them to alter their sources.list? Are we going to commit to providing a CDN of some description? Even a round-robin DNS solution has issues in that we have no immediate, insight or control over whether any "non-official" mirror is up-to-date, something obviously important from a user point of view. Thoughts? Best wishes, -- Chris Lamb https://puri.sm
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Wed, 2019-01-30 at 23:13 +0100, Chris Lamb wrote:
Jeremiah wrote:
There are some folks who're will to mirror our PureOS distro which is very generous of them.
Alas, I fear this is a bigger question that just rsync daemon settings. :)
Whilst extremely kind of them, how will this work for our users?
Do you mean how do we enable our users to easily take advantage of the mirrors? E.g. not having to edit source.list.d/ by hand?
Ask them to alter their sources.list? Are we going to commit to providing a CDN of some description?
Is a CDN necessary?
Even a round-robin DNS solution has issues in that we have no immediate, insight or control over whether any "non-official" mirror is up-to-date, something obviously important from a user point of view.
Thoughts?
On balance I feel the benefits of a mirror outweigh the risks, at least if we are clear with how we handle the mirrors. I'll follow-up on Jonas' suggestion and look into the CDN. In researching this a little it seems quite common to provide a mirror list, like Kali does: https://http.kali.org/README.mirrorlist If only to enable "power users" who likely download a fair amount I think this would be a benefit. There have been comments in the forum and other places that downloads can be slow. I'll propose some documentation based on what the community best practices seem to be and come back to this list for review and comment. Regards, Jeremiah -----BEGIN PGP SIGNATURE----- iQGzBAEBCgAdFiEEBkkHqXr+u7OUqMKseFgrT+6RsjkFAlxUgMwACgkQeFgrT+6R sjmXUwv/ZRIJG7OrCbVat7qKE8RQulAMokvT3XmNFPjFTef6U5dPXW1s12H1EVwA MxhN7OsZAoYw35uZ3yChKHAnz8tzLiBa93CFWCxEGpM2iRlN6sBLVrC8Zpeb0WG3 5mWvgkz4AqkoGFjE3f/fILXTTHFwL7PDm8hrWW8WdH3HwQN8Uey1f4gxwWdiJDX2 ffMnBujLBPD7lXgW+gRYltiUYAe2CtXtY7HbwDyoooNizGevpJXHULAF1U8yzFfe xjRbrzCgYCgUhLNviwa8pjMCfco9vyaEElZiztTtPsi0KEVLHKnIYogPmo4q13+4 C9kjlZRcM5iGTTv8nfGIKowbzt0hPDPRbnSEFdj/5LUv1TL8JQcRauhncvpLapfx wvdWxYCcjEcUnhTPmxHAe81L/SU0SBmWnGQREaPmTc7bPuO2v36n1b/90/3vfKl+ W02JJh0RuLoJbUN1CHm1akNiFgaheeM7BH1dl4W7/swXNkRIuMavkjcNw8XwXgCI Fl4I5yWz =xpf/ -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Fri, 2019-02-01 at 12:24 -0500, Jeremiah C. Foster wrote:
On Wed, 2019-01-30 at 23:13 +0100, Chris Lamb wrote:
Jeremiah wrote:
There are some folks who're will to mirror our PureOS distro which is very generous of them.
Alas, I fear this is a bigger question that just rsync daemon settings. :)
Whilst extremely kind of them, how will this work for our users?
For power users we can simply post information in the forums, wiki, and other documentation. That might reduce considerably the bandwidth issues we are seeing now since a sizable portion of our users appear to be fairly technical and messing with /etc/apt/sources.list.d/ oughtn't be too difficult.
Do you mean how do we enable our users to easily take advantage of the mirrors? E.g. not having to edit source.list.d/ by hand?
Ideally the 'Software' tool from GNOME might be a good candidate to enable switching mirrors. I realize that may be a more long term goal but there are other tools that appear useful in Debian that we might use as well, like apt-mirror.
Ask them to alter their sources.list? Are we going to commit to providing a CDN of some description?
I intend to speak to Fastly: https://www.fastly.com/open-source They may be able to help. Work also has begun on a policy document in the internal PureOS wiki. Regards, Jeremiah -----BEGIN PGP SIGNATURE----- iQGzBAEBCgAdFiEEBkkHqXr+u7OUqMKseFgrT+6RsjkFAlxt+7YACgkQeFgrT+6R sjlTWAwAhjq2pC61s00tn+GM2m11MurCK+QHGbx0+f8JVnP097ZVJn+JMaux+ct1 CDlHzp7OZHeZwQ+8hd4hgJOlqz/rTniRaQ/Cx3KUAlAhhD1MnYS+mBoqDzcOahUJ kMw2qiPokQbx06WBRGbllIFJ8LDAOBrNaNs4W+m/5z5cihP4t2T1yuJR1dT+W/KC 3978DMAwK6KoN54rgG+Ypc0bPIBOWmKEtbJwlmp1M03MWTnxFUd0M0xiAqKK4Q5+ wJ8WBHZf1/R5Kvwe4oyqdJ1HyrWTAQVqcJghe6RAC3HC9mNWIEshed50yz5lnITQ ppAsJgDP0D7Rn7QPJmzxPeiPla77yrH60NsxjHe+fMX15vJr7utRjjlM7fxJBDmD r2P2y/LoDA0UHz5jhWJbkbzoGMv6cUkKKNrLLM+zH4Xk5qZ9yU6O3KcpsMtvCNG2 F2uX33lQNt74LPBJiSJOGu3EG2ztABvYsyVBbrZzpDs2Rln+QFd9n77ww13ccH1k Hz25LAWY =6F40 -----END PGP SIGNATURE-----
participants (2)
-
Chris Lamb -
Jeremiah C. Foster