As many of you know I have been hired on to work on Fedora Infrastructure full time. This will be a great thing for our group. Initially I'll be spending a lot of time getting our house in order and fixing a lot of those little things that we keep putting off. Many of the mid term goals we've already talked about and are on the Schedule page.
I'd like to hear the communities ideas now that we have a dedicated resource (me). I'm especially interested in things that will help other teams do what they need to do. Like how to not screw the doc's guys during the next release or better empowering sponsors. Encouraging new volunteers to come and volunteer management / coordination is also something we need to address soon, we're growing quite quickly. With these things in mind try not to think specifically about our infrastructure team but about the project as a whole and how we can aid the community to thrive.
I'll officially be starting the first week in Feburary and will be looking for ways to expand our infrastructure both in Red Hat and outside of Red Hat, perhaps by finding partnership in an additional University. As long as we're smart about what we commit to, I have no doubt that we'll be able to provide the community with everything they need.
-Mike
Hello Mike,
Congrats and a welcome to Red Hat. I'll look forward to have FI expand...
regards,
Florian La Roche
On Tue, Jan 09, 2007 at 10:34:43AM -0600, Mike McGrath wrote:
As many of you know I have been hired on to work on Fedora Infrastructure full time. This will be a great thing for our group. Initially I'll be spending a lot of time getting our house in order and fixing a lot of those little things that we keep putting off. Many of the mid term goals we've already talked about and are on the Schedule page.
I'd like to hear the communities ideas now that we have a dedicated resource (me). I'm especially interested in things that will help other teams do what they need to do. Like how to not screw the doc's guys during the next release or better empowering sponsors. Encouraging new volunteers to come and volunteer management / coordination is also something we need to address soon, we're growing quite quickly. With these things in mind try not to think specifically about our infrastructure team but about the project as a whole and how we can aid the community to thrive.
I'll officially be starting the first week in Feburary and will be looking for ways to expand our infrastructure both in Red Hat and outside of Red Hat, perhaps by finding partnership in an additional University. As long as we're smart about what we commit to, I have no doubt that we'll be able to provide the community with everything they need.
-Mike
Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
On Tue, 2007-01-09 at 10:34 -0600, Mike McGrath wrote:
I'd like to hear the communities ideas now that we have a dedicated resource (me). I'm especially interested in things that will help other teams do what they need to do. Like how to not screw the doc's guys during the next release or better empowering sponsors. Encouraging new volunteers to come and volunteer management / coordination is also something we need to address soon, we're growing quite quickly. With these things in mind try not to think specifically about our infrastructure team but about the project as a whole and how we can aid the community to thrive.
A couple of ideas that I've had floating around my mind for a while:
Having more Bittorrent seeds for the ISO downloads available on release day. This should make bittorrent a much more attractive download option for users and should relieve the strain on the regular mirrors. What I'd suggest is that some trusted members of the community be set up with early access to the bittorrent trackers so that they can get a local copy of the ISOs and can then be seeds for the general public. This wouldn't need to be a long-term commitment of resources - perhaps 2-3 days before the release day, and then a week or so after release.
A few more secondary DNS servers for fedoraproject.org. Again, I'm sure that trusted members of the community would step up to provide the secondary DNS servers. Perhaps DNSSEC should be investigated to make doubly sure that the DNS data isn't messed with. Of course, this would be a long-term committment but shouldn't be very resource-intensive.
Jeff
Having more Bittorrent seeds for the ISO downloads available on release day. This should make bittorrent a much more attractive download option for users and should relieve the strain on the regular mirrors. What I'd suggest is that some trusted members of the community be set up with early access to the bittorrent trackers so that they can get a local copy of the ISOs and can then be seeds for the general public. This wouldn't need to be a long-term commitment of resources - perhaps 2-3 days before the release day, and then a week or so after release.
A few more secondary DNS servers for fedoraproject.org. Again, I'm sure that trusted members of the community would step up to provide the secondary DNS servers. Perhaps DNSSEC should be investigated to make doubly sure that the DNS data isn't messed with. Of course, this would be a long-term committment but shouldn't be very resource-intensive.
i'm working for the french cctld registry,
maybe i can ask here if the two or only of these suggestions can be handle here mike ? what do you think ?
Rachid
On 1/9/07, Zarouali Rachid rzarouali@gmail.com wrote:
Having more Bittorrent seeds for the ISO downloads available on release day. This should make bittorrent a much more attractive download option for users and should relieve the strain on the regular mirrors. What I'd suggest is that some trusted members of the community be set up with early access to the bittorrent trackers so that they can get a local copy of the ISOs and can then be seeds for the general public. This wouldn't need to be a long-term commitment of resources - perhaps 2-3 days before the release day, and then a week or so after release.
This is doable but will require a partner seeder and some coordination. We have in the past had issues actually getting the initial media out to where it needs to go.
A few more secondary DNS servers for fedoraproject.org. Again, I'm sure that trusted members of the community would step up to provide the secondary DNS servers. Perhaps DNSSEC should be investigated to make doubly sure that the DNS data isn't messed with. Of course, this would be a long-term committment but shouldn't be very resource-intensive.
We do have a primary and slave DNS server, the issue will be security. Who do we trust to do this, right now the primary is at Duke and the backup is with Jesse Keating (f13).
i'm working for the french cctld registry, maybe i can ask here if the two or only of these suggestions can be handle here mike ? what do you think ?
We can certainly look into that. What would it take, what do we risk and what do we gain?
-Mike
On Tue, Jan 09, 2007 at 06:46:51PM +0100, Zarouali Rachid wrote:
Having more Bittorrent seeds for the ISO downloads available on release day. This should make bittorrent a much more attractive download option for users and should relieve the strain on the regular mirrors. What I'd suggest is that some trusted members of the community be set up with early access to the bittorrent trackers so that they can get a local copy of the ISOs and can then be seeds for the general public. This wouldn't need to be a long-term commitment of resources - perhaps 2-3 days before the release day, and then a week or so after release.
We can ask our normal mirrors if they would like to seed. Would need a little script they could run to hardlink the rsync trees into the bittorrent trees so we don't pull it twice.
Seth, can we have a "private" tracker that is later made "public" ? I'm not that familiar with bittorrent. I suspect that's security-through-obscurity though - anyone who finds the tracker could hop on.
We do have 55 formal mirrors, each serving some subset of {http,ftp,rsync}, and if have a sane embargo window of say 3 days, that's sufficient to get all of those synced. Any less time and we cap out the master servers' bandwidths and not everyone gets synced before the release.
If we're going to add early bittorrent seeders (e.g. not just the above mirrors), they would need to have fairly significant bandwidth at their disposal (e.g. larger than a DSL/Cable modem line). And we may need more embargo time to get them distributed. Would be interesting to try with say test2 and test3 rather than starting it only at the final release.
Thanks, Matt
On Tue, 2007-01-09 at 15:12 -0600, Matt Domsch wrote:
On Tue, Jan 09, 2007 at 06:46:51PM +0100, Zarouali Rachid wrote:
Having more Bittorrent seeds for the ISO downloads available on release day. This should make bittorrent a much more attractive download option for users and should relieve the strain on the regular mirrors. What I'd suggest is that some trusted members of the community be set up with early access to the bittorrent trackers so that they can get a local copy of the ISOs and can then be seeds for the general public. This wouldn't need to be a long-term commitment of resources - perhaps 2-3 days before the release day, and then a week or so after release.
We can ask our normal mirrors if they would like to seed. Would need a little script they could run to hardlink the rsync trees into the bittorrent trees so we don't pull it twice.
Seth, can we have a "private" tracker that is later made "public" ? I'm not that familiar with bittorrent. I suspect that's security-through-obscurity though - anyone who finds the tracker could hop on.
you'd be correct. We've talked about doing this before and it's been a nightmare.
it would be far better
We do have 55 formal mirrors, each serving some subset of {http,ftp,rsync}, and if have a sane embargo window of say 3 days, that's sufficient to get all of those synced. Any less time and we cap out the master servers' bandwidths and not everyone gets synced before the release.
and none of them have the isos in the layout we have them for the torrent. zero.
If we're going to add early bittorrent seeders (e.g. not just the above mirrors), they would need to have fairly significant bandwidth at their disposal (e.g. larger than a DSL/Cable modem line). And we may need more embargo time to get them distributed. Would be interesting to try with say test2 and test3 rather than starting it only at the final release.
If you want bittorrent seeders you'd be better off having them just be random mirrors who want to participate and can sync down the data in advance from the torrent.
However, I'd suggest that this is silly. If only b/c we've not gotten any reliable complaints about problems with performance in the torrent.
-sv
infrastructure@lists.fedoraproject.org