infrastructure December 2007

infrastructure@lists.fedoraproject.org

36 participants
27 discussions

Search domains in our environment (Proposal)
by Mike McGrath 20 Dec '07

20 Dec '07

Note: I'm treading into an area which I've always deemed bad practice so poke, prod and question where required. Right now we are using /etc/hosts relatively heavily in our environment. This is to help us clean up our apache configs and further blur the line of our servers and where they live. The suggestion in the past has been to host our own DNS server in PHX that provides a common view to fedoraproject.org but inside PHX. (You'll not that you cannot get to fedoraproject.org from inside PHX). Now that we have a vpn.fedoraproject.org domain, this allows us to do some dns trickery that we could not do before. So, for example, on bastion you can see this in action. The current search location set to: search fedora.phx.redhat.com vpn.fedoraproject.org fedoraproject.org So on bastion you can ping app1 which will use 10.8.34.59. However if I ping proxy3 (which is not in phx) I'll get address 192.168.1.7. and if I ping torrent (which is not in phx and not on the vpn) I'll get address 152.3.220.165. In theory, this will allow us to do interesting things in our german colo (they have the server now BTW, we are just waiting on IP info, it just got there yesterday). The trick here is having each group of servers have a preference for the local address. There's no reason for proxy1 to contact app1 over the vpn as they're on the same LAN. And there could, in theory, be instances where we'd want the serverbeach servers to have preference for other serverbeach servers. In cases of geographically separated servers this actually does add a tiny amount of redundancy. In that if a link goes down or dns goes down but the box does have connectivity to the internet still somehow, it might be able to get to the vpn instead of its direct connection. Again, tiny but there especially true when we get our redundant VPN server installed. So what does this mean? * You'll be able to get to any vpn host in our environment without having to know where it is. * We'll have to change any reference to fqdn's where our servers are contacting other servers. This will allow us to move servers around, even to other data centers, without having to change the configs. * The proxy servers are in a slightly special situation right now. We're using hosts entries on the proxy servers mostly because our DNS server in PHX flaked out on us once. We can re-examine this setup even still, to be consistent I'd like to switch to using non-fqdn access to our application servers. * We will have to be diligent in making sure all of our hosts have unique names as we've basically made the domain names negligent. * This will allow us to have a preference for vpn, remote or local traffic on a per machine basis should the need arise. (so for example, We get part of a DR site up and PHX goes down. We could very easily login to proxy3, change the search from vpn being first to local as both app5 and proxy3 are in tummy.com and we can be more efficient that way) Comments? +1's? -1's? I'm basically going for ease of use among the admins and since most people "ssh puppet1" instead of "ssh puppet1.fedora.phx.redhat.com" I think in our diverse environment it will be worth it and is easier then hosting a separate DNS server in each of our locations. -Mike

5 15

FUDCon / Hackfest
by Mike McGrath 18 Dec '07

18 Dec '07

I've added a couple of topics to the http://barcamp.org/FUDConRaleigh2008 site. One of which is all about Fedora Infrastructure. I'd like it is those of you on the team can make it to this meeting to talk with others about Infrastructure, what we're doing, where we're going and our general philosophies. Not at all mandatory, as with any barcamp, there's bound to be lots of good topics going on at once. I've also got a FAS2 topic on there (Hopefully ricky will co-talk that one with me). Also during the hackfest its important for the infrastructure team members to be alert at the needs of whats going on. At the last hackfest I ended up spending most of my time accomplishing tasks that the other teams / people needed to get their work done. So mostly this is just a heads up, those of you on the teams will likely be asked to do stuff during the hack fest, make sure to set a little time aside for it :) Also if anyone else out there has anything they think is worth talking about don't hesitate to add it to the list. -Mike

1 0

python-fedora: fas1 API addition
by Toshio Kuratomi 17 Dec '07

17 Dec '07

This is mostly for the people developing python/TG apps that need to talk to the Account System. If you are querying fas1 using the fedora.accounts.fas module you may want to look into porting to a new method I added and deployed over the weekend. The method is get_users() and it returns public information about all the users in the FAS. This is useful when you have to hit the FAS for a lot of information about people -- for instance, querying the FAS to map userid's to human_name for every person in your db. In that scenario you would have to spend a large amount of time waiting for the db to respond to your queries if you had to send them as individual requests via get_user_info(). This has recently become more of an issue since we're starting to create app servers outside of the phx colo. Those servers take more time to contact the db server inside of phx which means every round trip to the db server is more expensive. Example usage[*]: >>> from fedora.accounts.fas import AccountSystem >>> fas = AccountSystem() >>> userList = fas.get_users() >>> print userList[100068]['username'] toshio >>> userListByName = fas.get_users(keyField='username') >>> print userListByName['toshio']['id'] 100068 Refer to the docstring for more information: $ pydoc fedora.accounts.fas.AccountSystem.get_users [*] You'll need to be able to access the fedora-db-access file to actually use this code. Your TG app running under supervisor has that permission but your regular user may not. -Toshio

1 0

Jigdo - A Professional Letter to Mike McGrath
by Jonathan Steffan 17 Dec '07

17 Dec '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ah, what a wonderful scholastic assignment. It's also great that Mike is going to have to open the letter once it actually makes to him. Dear Mr. McGrath, As long time Fedora developers, we both have watched and lived through the growing pains of Fedora releases. With the onset of the merging between core and extras, we have successfully created the needed infrastructure on which even basic Linux users can create their own Fedora-based derivative distribution. Along with this achievement comes the task of providing hosting infrastructure for an average user/developer to be able to share his/her creation with the world. An additional benefit in being directly involved in the sharing of the "Spins" is the ability to data mine what packages people are including in custom spins as to give our developer base more focus. To be able to fulfill this task, please consider requesting additional resources to archive signed updates so that they can be publicly accessed for the duration of a release life-cycle. The long road of Fedora development has been bumpy and even not enjoyable at times. Throughout the duration of the Fedora 7 release, we have made some very amazing changes that helped to open Fedora up to the masses. One of the most community-based features is the ability to Re-Mix and Re-Spin the distribution as the end-user sees fit. Being the server team lead for Fedora Unity, I've had to come up with unique ways to share the Re-Spins we compose. After trying many approaches with different technologies, we have settled on using Jigdo, the jigsaw downloader. Debian has used Jigdo for some time now and after poking their system for a while I've seen they keep every update they push. I do understand that Debian is considered a stable distribution much in the way RHEL is considered stable. This makes the updates tree not as active and it is easier to find mirrors to carry the full data set for an extended period of time. We, however, need to find a way to offer this same extended life for signed packages that have hit the Fedora updates tree. The amount of storage and bandwidth able to be saved can be illustrated by a simple comparison between the efficiency of chopping up a 3.4GB iso9660 file system arbitrarily (by a static chunk size) and the same file system based on contents (file by file.) For a BitTorrent, Fedora's current choice for sharing Spins, the hosted data is only valid for a given chunk on a single ISO. This data's footprint (equal to the combined chunk sizes of the entire torrent) can be used for nothing but this Spin. To be able to host 5 Spins composed from similar trees via BitTorrent, we now have a footprint of 17GB, not to mention "seeders" have to run BitTorrent software to be able to contribute to the swarm. Alternatively, Jigdo can be used to reduce the footprint of these 5 Spins to about 4GB. The amount of additional data needing to be hosted for each Spin, in addition to what data is already pushed to the mirrors, is about 150MB per ISO with anaconda and about 200KB for ISOs without the installer bits. To help illustrate the efficiency of using Jigdo vs BitTorrent, the footprint for 250 Spins is 850GB for BitTorrent and about 40GB for Jigdo. Additionally, a reduction in overhead can be achieved by removing the need for the BitTorrent tracker and all related network traffic without requiring any additional work on the part of mirror administrators. The current updates system is getting better each release, but I think we should adjust our policies to also have an “updates-archive” repository. This repository will include all signed updates that had once lived in the updates repo, for the duration of the releases life-cycle. I don't expect all mirrors would want to carry this extra data so making the new repo optional will be a must. With the new MirrorManager, we will be able to effectively point users at mirrors that have been willing to take on the extra footprint. These requests to MirrorManager could be used to compose reports on what packages the community is utilizing most, allowing us to better focus our efforts. By providing an unified point of entry for data, we will be able to also log requests for package data found on in-house and non-official spins. By utilizing the abilities of MirrorManager to return specific mirrors for pre-defined IP blocks, we will enable end-users and companies to download from on-site mirrors while maintaining complete transparency. I hope that with advancements in Jigdo client software we will be able to look at using Jigdo to host our official images. Please let me know your thoughts on this matter. As always, thanks, - -- Jonathan Steffan daMaestro GPG Fingerprint: 93A2 3E2F DC26 5570 3472 5B16 AD12 6CE7 0D86 AF59 - -- Jonathan Steffan daMaestro GPG Fingerprint: 93A2 3E2F DC26 5570 3472 5B16 AD12 6CE7 0D86 AF59 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHWGltrRJs5w2Gr1kRAinaAKCSRaTWjuCtsGQKWsvuhCXKm0qSdQCfbj/N 52VVTOYXSQn4qLlfXThEpMg= =ciP1 -----END PGP SIGNATURE-----

10 28

Notice: puppet on the boxes
by Mike McGrath 16 Dec '07

16 Dec '07

During an update of the builders last night we also did a puppet update and some incompatibilities between the old and new puppet versions exist. I plan on updating the rest of the servers tomorrow morning but in the meantime if you make a change it might not end up on the servers immediately. If I find any issues we may have to roll back the builders. -Mike

1 0

fedorahosted.org is ready for testing
by Mike McGrath 15 Dec '07

15 Dec '07

I'd like to move all the services and things from their current location to the serverbeach hardware tomorrow around noon. In the mean time I'd like some help testing. We've changed the domain name to fedorahosted.org so we can avoid any namespace issues in the future regarding email addresses or server addresses. I've requested an SSL cert but it could be a bit before we get it (https on that site will hit the hosted.fedoraproject.org cert and throw a warning). Feel free to test by checking out and committing to your repo, those changes (if using fedorahoste.org addresses below) will be wiped out when we do the final move. Git users: git://git.fedorahosted.org/git/$PROJECT (anon, ro) http://git.fedorahosted.org/git/$PROJECT (anon, ro) ssh://git.fedorahosted.org/git/$PROJECT (auth, rw) rsync://git.fedorahosted.org/git/$PROJECT (anon, ro) HG users: http://hg.fedorahosted.org/hg/$PROJECT (anon, ro) ssh://hg.fedorahosted.org/hg/$PROJECT (auth, rw) rsync://hg.fedorahosted.org/hg/$PROJECT (anon, ro) BZR users: http://bzr.fedorahosted.org/bzr/$PROJECT (anon, ro) ssh://bzr.fedorahosted.org/bzr/$PROJECT (auth, rw) rsync://bzr.fedorahosted.org/bzr/$PROJECT (anon, ro) SVN users: http://svn.fedorahosted.org/svn/$PROJECT (anon, ro) ssh://svn.fedorahosted.org/svn/$PROJECT (auth, rw) rsync://svn.fedorahosted.org/svn/$PROJECT (anon, ro) I'm also working on putting a little website together with content about what it is, how to ask for it and move that content off of the wiki. -Mike

6 11

New member introduction
by Lee Lorentz 15 Dec '07

15 Dec '07

Sorry; my subscription to the list was using the wrong email address. Should be fixed now. -----Original Message----- From: Lee Lorentz [mailto:lee@wb0tra.no-ip.org] Sent: Saturday, December 15, 2007 16:23 To: 'fedora-infrastructure-list(a)redhat.com' Subject: New member introduction I'm still working through the "Getting Started" instructions for Infrastructure and the web page says it is time to introduce myself. Lee Lorentz in Annandale, Minnesota, USA. Email <lee(a)wb0tra.no-ip.org> I've been a PC database developer and programmer since the dBASE II days (early 1980's?). I'm currently migrating from Visual FoxPro over to the LAMP stack for development work. I manage a database (MySQL on CentOS v4) at work with over 75 million records in a single table, so database performance is a big deal for me. My official bachelors degree is in "Elective Studies" (nice generic title) but the course concentration was in networking and systems analysis. My first Linux exposure was to Mandrake for which I can't remember the version and I've been a Fedora user since FC2. I now have boxes at home running FC6, F7, and CentOS v4, and I hope to soon have a new laptop running F8. I've been working with MySQL for 2-3 years now and about the same with php. I don't claim to be an expert with either but I've already been able to make some small contributions in optimizing queries for smolt. I hope to be able to make further contributions along this line, but am open to requests to help out anywhere someone thinks I can help. I put in a lot of hours at work so I'm uncertain how much I can contribute but given the benefits I've gained from using Fedora I want to try to give something back. My nics on irc are wb0tra_home and wb0tra_work. "WB0TRA" is my ham radio license which I've held since 1975. I try to maintain connections to the fedora-admin, mysql, smolt, fedora-unity, scalug, and scalug-hams channels. You can see more info on me at my home page http://wb0tra.no-ip.org/ and at http://www.qrz.com/callsign/WB0TRA

1 0

Request for monotone
by Mike McGrath 13 Dec '07

13 Dec '07

we've had a request to support monotone on hosted. Instead of having this conversation in private I thought it best to put it on the list. So thoughts? This is part "do we want to support monotone" and part "do we want hosted to be more then svn, hg, git, bzr". In general I'm happy supporting only those 4, we can't be everything for everyone and AFAIK we're the only OSS project with a hosted offering that supports 4 SCM's. Thoughts? -Mike

11 16

Meeting Log - 2007-12-13
by Ricky Zhou 13 Dec '07

13 Dec '07

15:01 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Who's here 15:01 * ricky 15:01 * lmacken 15:01 * f13 15:01 * mmcgrath 15:01 * jeremy 15:01 < jeremy> (although I might disappear in a few) 15:02 * jima 15:02 * jima may disappear at any time, for any or no reason 15:03 -!- bpepple [n=bpepple(a)adsl-75-60-198-211.dsl.wotnoh.sbcglobal.net] has quit "Ex-Chat" 15:03 < mmcgrath> dgilmore: ping 15:03 < mmcgrath> skvidal: ping 15:03 < mmcgrath> abadger1999: ping 15:03 < mmcgrath> lmacken: ping 15:03 < skvidal> pong 15:03 < mmcgrath> ivazquez: ping 15:03 < paulobanon> pong 15:03 < mmcgrath> iWolf: ping 15:03 -!- notting [i=notting@redhat/notting] has joined #fedora-meeting 15:03 < dgilmore> sup mmcgrath 15:03 < skvidal> -1 15:03 < abadger1999> pong 15:03 < dgilmore> -1 15:03 < ricky> That was fast :) 15:03 < skvidal> oh, wait, sorry, no one asked for a vote on anything, yet 15:03 < paulobanon> yay, in the office working and meeting here so i might split soonish 15:03 < mmcgrath> hehe not voting quite yet. 15:03 < skvidal> -1 anyway 15:03 < mmcgrath> warren: ping 15:03 * warren here 15:03 < mmcgrath> ping anyone else I forgot to ping: ping! 15:04 < dgilmore> skvidal: the answer is always no 15:04 < skvidal> damn right 15:04 < dgilmore> oh wait its 42 15:04 -!- stahnma [n=stahnma(a)c-76-18-178-254.hsd1.tn.comcast.net] has joined #fedora-meeting 15:04 < jima> dgilmore: 42 "no"s 15:04 < skvidal> dgilmore: or "Run Away" 15:04 < skvidal> which is also a good answer 15:04 < mmcgrath> k, lets get started. 15:04 < mmcgrath> First up is meeting items 15:04 < skvidal> and "I don't care what the machine says, I NEVER TOUCHED THE MAN" 15:04 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Meeting Items 15:04 < mmcgrath> .tiny https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… 15:04 < mmcgrathbot> mmcgrath: http://tinyurl.com/2hyyz6 15:05 -!- giarc [n=cwt(a)ool-435124e0.dyn.optonline.net] has joined #fedora-meeting 15:05 < mmcgrath> .ticket 192 15:05 < mmcgrathbot> mmcgrath: #192 (Netapp low on free space) - Fedora Infrastructure - Trac - https://hosted.fedoraproject.org/projects/fedora-infrastructure/ticket/192 15:05 < mmcgrath> f13: how's the GC stuff going? 15:07 < f13> mmcgrath: a question for mikem, on how close we are to automation. 15:07 < f13> mmcgrath: I think he said we needed some server changes before we could fully automate, but those should be rolled into the new upstream koji release we're doing before the refresh 15:07 < f13> we've got a ton of packages that could be flushed soon. 15:07 -!- MrBawb [i=abob(a)guppy.drown.org] has joined #fedora-meeting 15:07 < f13> so if we get critical we can flush the trash and recover a lot of space 15:08 -!- mikem23 [i=iimike@nat/redhat/x-b06c3d5d18f5e9d0] has joined #fedora-meeting 15:08 -!- loupgaroublond [n=yankee(a)pool-72-95-243-109.pitbpa.east.verizon.net] has joined #fedora-meeting 15:08 < mmcgrath> mikem23: yo, we're talking about GC and were wondering how all of that is going. 15:08 < mmcgrath> how close are we to automation on it? 15:09 < jima> i asked the other day if it was feasible to put a control for maintainers to flag (scratch?) builds for deletion sooner rather than later 15:09 < mikem23> mmcgrath, well, I have the cronjobs in place (granted I need to move them to the new host). 15:09 < jima> not sure who the best person to talk to that about is, though. 15:09 < mikem23> mmcgrath, there are some issues I need to smooth out. 15:10 < mmcgrath> jima: your best bet is to file a ticket in the koji queue. 15:10 < mmcgrath> mikem23: solid, but you don't see any blockers or anything that would prevent us from doing automation in the near future? 15:10 < mikem23> 1 - there are some issues that tend to cause some of the nightly gc scripts to fail 15:10 < jima> mmcgrath: *nod* 15:11 < mikem23> 2 - I need to get a few small updates to the koji hub to reduce memory/network usage and fix a silly bug. 15:11 < mikem23> 3 - I need to play with frequency. 15:12 < mikem23> mmcgrath, in principle it's automated now. 15:12 -!- G__ [n=njones@wikipedia/NigelJ] has joined #fedora-meeting 15:12 < warren> Is GC alone going to keep us running through the holidays without more storage 15:12 < mikem23> being run through cron sounds automated to me 15:12 < mmcgrath> just needs some tweaking then? 15:12 < warren> ? 15:12 < mikem23> ok, so about space... 15:12 < mikem23> basically /mnt/koji is too small 15:13 < dgilmore> mikem23: we are working on making it bigger 15:13 < mikem23> now, there are a healthy number of builds headed for deletion in about two weeks 15:13 < mikem23> see, the gc has these grace periods 15:14 < mikem23> if we get desperate, we flush the trashcan by overriding the grace period 15:14 < mikem23> right now the grace period is set to two weeks 15:14 < mmcgrath> <nod> Its good to know what our options are. 15:15 < mikem23> http://fedoraproject.org/wiki/Koji/GarbageCollection explains the gc lifecycle 15:15 < f13> I'm farily confident that with what we have queued up to flush, we should be able to make it through the holidays 15:15 < mmcgrath> f13: excellent. 15:15 < mmcgrath> anyone have anything else regarding GC or ticket 192? 15:16 < paulobanon> any plans yet for more storage ? 15:16 < paulobanon> or only after the results of the gc 15:16 < mmcgrath> paulobanon: the plans are in motion but these things always take time. 15:16 < mmcgrath> I should send a followup and see how far along we are. 15:17 < paulobanon> sounds good 15:17 < mmcgrath> anything else? 15:17 < mmcgrath> allrighty, we'll move on. 15:17 < mmcgrath> .ticket 270 15:17 < mmcgrathbot> mmcgrath: #270 (Fedora Wiki allows editing raw HTML) - Fedora Infrastructure - Trac - https://hosted.fedoraproject.org/projects/fedora-infrastructure/ticket/270 15:17 < mmcgrath> This is an issue discovered recently and I think it warrents some discussion. 15:17 < mmcgrath> ricky: care to explain further? 15:17 < jima> is there anything on the wiki that genuinely needs raw html? 15:18 < ricky> jima: I think some of the group banners use it, don't remember if the front page uses it right now. 15:18 < mikem23> I don't think the main wiki page would look quite as nice without raw html, but maybe I'm wrong. 15:18 * mikem23 checks 15:18 * jima would have clicked the search link, but didn't want to abuse the poor wiki 15:18 < ricky> Basically, it's possible to put javascript, etc. on the wiki that could access cookies, etc 15:19 < mikem23> ok, I think I'm wrong about that 15:19 < f13> some of the irc logs page use html 15:19 < f13> and I think some of the fever stuff used html 15:19 < ricky> With this version of Moin's auth, the only cookie should be a MOIN_ID (which would just give full control over the wiki account), but that's pretty much the full extent of it. 15:20 < dgilmore> ricky: that could be bad 15:20 < mikem23> we should probably look at how raw html is used and see is we can replace it with macros instead 15:20 < abadger1999> dgilmore: Moin's cookie is already subject to sniffing.... 15:20 < mmcgrath> So the options here are A) Acknowledge the security issue and try to negate it as much as possible or B) disable html editing. 15:21 < lmacken> 416 pages are using raw html 15:21 < dgilmore> mmcgrath: i vote to disable it 15:21 < mmcgrath> Anyone interested in keeping it? 15:21 < lmacken> err.. maybe not pages, but "matches" 15:22 < mmcgrath> ricky: what would happen to the current pages if we did disable it? 15:22 < paulobanon> we will have to announce it prior to the disable to make sure that the other teams fix their stuff 15:22 * ricky tests something. 15:22 < mmcgrath> paulobanon: yeah 15:22 < abadger1999> If upstream moin implements a "safe html" which doesn't accept scripts we could reenable. 15:22 < mmcgrath> its possible they already have that and we just don't know it. 15:23 < paulobanon> abadger1999: im sure they wont implement anything new until 1.6 is out, until we do it our selfs and offer the patch to them 15:23 < paulobanon> mmcgrath: last time i checked we were using the latest Moin-stable 15:23 < paulobanon> havent checked for the last 1 or 2 months though 15:23 -!- G [n=njones@wikipedia/NigelJ] has quit Connection timed out 15:24 < mmcgrath> ricky: what are you testing and how long will it take? :) 15:24 < ricky> Looks like it'll just show the HTML source. 15:24 < abadger1999> paulobanon: I checked ~1 week ago and we're still on the latest stable. 15:24 < mmcgrath> k 15:24 < ricky> (just looking at what {{{#!fake test}}} does) 15:24 < mmcgrath> I also say we disable it until such a time comes that we can make sure scripts won't be allowed. 15:24 < lmacken> we would probably lose stuff like the spiffy sidebar in http://fedoraproject.org/wiki/Artwork 15:25 < mmcgrath> ricky: paulobanon: will one of you guys put together a one or two week plan to notify everyone about what we're going to do, why and then do it? 15:25 < loupgaroublond> is it possible to make a template that provides sidebar like capabilities in moin? 15:26 < paulobanon> loupgaroublond: i think that there is a theme with some sidebars, not sure though 15:26 < ricky> loupgaroublond: Yeah, I think we can create macros that output certain HTML. 15:27 < loupgaroublond> that answers lmacken's question then :) 15:27 < paulobanon> mmcgrath: sounds good. Is there any "general" ML that can be used to inform everyone related ? 15:27 < warren> "safe html" in other sites has proven to be ... unsafe 15:27 < warren> everyone reinvents the wheel and gets it wrong 15:28 < paulobanon> warren: sad, but true 15:28 < mmcgrath> paulobanon: send an email to fedora-announce-list, I don't think enough of the right people are on fedora-devel-announce 15:28 -!- cwt_ [n=cwt(a)ool-435124e0.dyn.optonline.net] has joined #fedora-meeting 15:28 * ricky sees http://moinmo.in/HelpOnMacros#head-7c57db7e2451458a42840f17268344df06492a2e, I'll start looking at create macros for common uses. 15:28 < warren> "Sorry, your your new trapezoidal wheel isn't working out for us." 15:30 < mmcgrath> Solid, anyone have anything else to comment on that ticket? 15:30 < MrBawb> speaking of safe html, I'm looking at an exploit that gets in via an activex exploit 15:30 < MrBawb> and uploads a keylogger to windows machines 15:31 < mmcgrath> ok, moving on. To the vote! 15:31 < mmcgrath> .ticket 283 15:31 < mmcgrathbot> mmcgrath: #283 (Vote: Support Monotone?) - Fedora Infrastructure - Trac - https://hosted.fedoraproject.org/projects/fedora-infrastructure/ticket/283 15:31 < mmcgrath> Little background. 15:31 < dgilmore> mmcgrath: there website lists "Monotone is slow, doesn't scale well to large codebases and historeis." 15:31 < mmcgrath> We've had a request from Roland McGrath to support monotone because he wants to host elfutils on fedora hosted. 15:31 -!- llaumgui [n=llaumgui(a)cro34-2-82-226-153-125.fbx.proxad.net] has quit Remote closed the connection 15:31 < dgilmore> eww 15:31 < mmcgrath> I've not heard back whether or not it can even be integrated with FAS but assuming it can, lets take the vote. 15:32 < mmcgrath> ============= Vote Start 2 minutes =========== 15:32 < dgilmore> -1 15:32 -!- llaumgui [n=llaumgui(a)cro34-2-82-226-153-125.fbx.proxad.net] has joined #fedora-meeting 15:32 < f13> I won't vote until the questions I asked on list are answered. 15:32 < abadger1999> +0 I'm not against monotone. I am against monotone without some monotone-familiar admins joining infra. 15:32 < loupgaroublond> who is eligible to vote? 15:32 < f13> or rather, I won't vote /for/ monotone 15:32 -!- llaumgui [n=llaumgui(a)cro34-2-82-226-153-125.fbx.proxad.net] has quit Remote closed the connection 15:32 < mmcgrath> f13: would you like us to vote next week? 15:33 < dgilmore> mmcgrath: id like to see us support elfutils but i dont see what we gain by monotone 15:33 < f13> mmcgrath: well, if we don't have anybody who can answer the questions I posed, I"ll just vote -1 15:33 -!- bpepple [n=bpepple(a)adsl-75-60-198-211.dsl.wotnoh.sbcglobal.net] has joined #fedora-meeting 15:33 < lmacken> I'm all for turning elfutils into an open source project (finally).. but unless roland or someone else steps up to help us with monotone, I'm a bit weary towards it 15:34 < mmcgrath> lmacken: I'm not even sure I like the sound of that. 15:34 < mmcgrath> I worry about people showing up to work on just one thing. 15:34 < lmacken> yeah, true 15:34 < mmcgrath> they tend not to be around when you need them. 15:35 < mmcgrath> Ok, I think monotone is a bit unclear to all of us here, let me see if we can get Roland to answer these questions by next week and we'll vote then. In the meantime we can all do a little research. 15:35 < mmcgrath> I guess we're not in a hurry to say yes or no to it. 15:35 * ricky sees http://monotone.ca/docs/Other-Transports.html. 15:35 < mmcgrath> ================ Vote End =============== 15:35 < loupgaroublond> is there any chance that one project can be moved over to another scm? 15:35 -!- llaumgui [n=llaumgui(a)cro34-2-82-226-153-125.fbx.proxad.net] has joined #fedora-meeting 15:35 < mmcgrath> we'll do it next week. 15:35 < mmcgrath> loupgaroublond: what do you mean? 15:36 < loupgaroublond> have him switch over to git or hg, or does it have to be monotone? 15:36 < warren> I've used monotone myself, it is very capable, the pidgin project uses it. 15:36 < warren> loupgaroublond, or bzr 15:36 < loupgaroublond> or bzr, sure :) 15:36 < mmcgrath> loupgaroublond: I haven't specifically asked that but I will. 15:37 < loupgaroublond> i'm not asking if monotone is good or not, i'm jsut asking if we can ask roland to switch to something else, because i feel like this debate could get very hairy otherwise 15:38 -!- jcollie [n=jcollie(a)161.210.6.204] has joined #fedora-meeting 15:38 < abadger1999> ricky: That's a good doc. That seems like half the battle. Still have to find out about anonymous access. 15:38 < warren> It does add risk to our server to add more and more different systems 15:38 * mmcgrath really wants to leave it at 4 systems. 15:38 < warren> we might justify adding monotone only if several other projects want it 15:38 < mmcgrath> err scms. 15:39 < loupgaroublond> does trac support monotone? 15:39 < ricky> loupgaroublond: I saw a plugin mentioned, but pidgin's trac doesn't seem to have support enabled. 15:39 -!- giarc [n=cwt(a)ool-435124e0.dyn.optonline.net] has quit Read error: 110 (Connection timed out) 15:39 * mmcgrath just sent jesse's questions and some others to Roland McGrath, we should know more next week. 15:39 * ricky recalls the "fun" that we've already had with the git plugin. 15:40 * mmcgrath blames the git plugin for all the zombie git processes we see on hosted1. 15:40 < mmcgrath> anywho. 15:40 * abadger1999 notes that gna has support four three SCMs so we're not the only project with multiple SCMs for hosting. 15:40 < mmcgrath> anyone have anything else to discuss on this topic? 15:40 < abadger1999> s/four/for/ 15:40 < mmcgrath> abadger1999: excellent, which scms are they? 15:40 < abadger1999> cvs, svn, and tla 15:41 < warren> we're in way better shape 15:41 < warren> those suck =) 15:41 < abadger1999> Well... way more modern :-) 15:41 < mmcgrath> :) 15:41 * paulobanon wants to do an off-time vote -1 15:41 < mmcgrath> Alrighty, moving on.... 15:42 -!- J5 [i=quintice@nat/redhat/x-6905b79a0881d913] has quit "Ex-Chat" 15:42 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Schedule 15:42 < mmcgrath> http://fedoraproject.org/wiki/Infrastructure/Schedule 15:42 < mmcgrath> Nothing much new going on there. 15:42 -!- J5 [i=quintice@nat/redhat/x-85cfe85621f1df08] has joined #fedora-meeting 15:42 < mmcgrath> The coporate sponsorship is still the same though we need to get pier1 or serverbeach's logo on the hosted site (I'm still waiting for them to send it) 15:43 < mmcgrath> no new documentation or SOP's that I can think of from this week. 15:43 < mmcgrath> And no new sponsors that I can think of. 15:43 < mmcgrath> so, nothing there. 15:43 < mmcgrath> and with that... 15:43 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Open Floor 15:43 < mmcgrath> does anyone have anything they'd like to discuss? 15:43 < paulobanon> anything new with the bladecenter or the german server ? 15:43 < mmcgrath> Nothing new with the blade center. 15:44 < mmcgrath> the german server got shipped to a RH office and is now being shipped to the colo. 15:44 < skvidal> are we going to have a meeting next week? 15:44 * mmcgrath not sure what happened there but is trying to find out so it doesn't happen in the future. 15:44 < skvidal> I ask b/c I'm sure a lot of people are traveling or planning travel 15:44 < mmcgrath> skvidal: on the 20th? 15:44 < dgilmore> skvidal: hope not ill be on a train i think 15:44 < paulobanon> its my birthday! 15:44 < paulobanon> :D 15:44 < mmcgrath> skvidal: I'll go ahead and try to schedule one but if no one shows up it will likely be very very short. 15:45 < skvidal> okie doke 15:45 < skvidal> I'll be around 15:45 < skvidal> I just thought I'd ask 15:45 < abadger1999> I wrote an initial patch to get moin to handle subscriptions better. MrBawb has been doing an excellent job of enhancing that. 15:45 < mmcgrath> yeah if you guys haven't seen MrBawb's benchmarking you should, he's done a good job. 15:45 < paulobanon> mmcgrath: where can i read it ? 15:46 < dgilmore> mmcgrath: my train gets to union station at 12:15pm next thurs 15:46 < mmcgrath> dgilmore: you've got a busy day ahead of you :) 15:46 < dgilmore> mmcgrath: that i do 15:46 < mmcgrath> MrBawb: where are your benchmarks? 15:46 < abadger1999> MrBawb is working on getting it to the place that upstream will accept it. 15:47 < abadger1999> I think we should start thinking about whether/when we want to apply it to our installation. 15:47 < ricky> Curious - what's the ACL patch that we're currently using? 15:47 < MrBawb> mmcgrath: http://dan.drown.org/fedora/compare-storage.html 15:48 < MrBawb> right now I'm working on getting the code to the standards that the MoinMoin people want 15:48 < MrBawb> naming, and using their locking,e tc 15:48 < mmcgrath> ricky: it allows us to set an acl on say /InfrastructurePrivate/ and having it automatically apply to /InfrastructurePrivate/CreditCards 15:49 < ricky> Aha. 15:49 < mmcgrath> Alrighty, anyone have anything else? If not I'll close the meeting in 30. 15:51 < mmcgrath> 15 15:51 < mmcgrath> 5 15:51 < paulobanon> go go go 15:51 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Meeting Closed!

1 0

Welcome new Mirror Wranglers!
by Matt Domsch 12 Dec '07

12 Dec '07

Thank you each for volunteering to help with managing Fedora's list of mirror servers. You have all been added to the email alias 'mirror-admin(a)fedoraproject.org', which is how you are getting this email. First, please send me your Fedora Account System username, as presumably the email address stored in the FAS for you is where you want these mails to go. Second, I recommend you subscribe to the relatively low volume fedora-infrastructure-list(a)redhat.com , which is where all the interesting Infrastructure discussion happens. (http://www.redhat.com/mailman/listinfo/fedora-infrastructure-list) This includes outage notices, freeze changes, and the like. Third, we are always happy to have more mirrors, provided they have sufficient capacity to really be of benefit. In the US and Europe, we don't really need more mirrors. Rest of the world, we definitely do. Requests will come to the mirror-admin(a)fedoraproject.org address, and will need a response. Be sure to "reply to all". I'll append my template. Be sure to copy ftp+fedora(a)redhat.com and mirror-admin on your reply, so everyone sees it, and so the rsync ACL on the master download servers will get updated. Rule of thumb: new mirrors with >= 1Gbit pipes, or in countries not already well-served (such as India, China, or anything in South America or South Africa) should be approved. Mirrors on DSL/Cable modem lines in the US or Europe, thanks, but no. Private mirrors should be directed to pull from a listed public mirror. When approved, you should then approve their subscriptions to mirror-list and mirror-list-d. There's a password required to moderate that list. Not sure how best to handle that aspect... Fourth, the MirrorManager code itself. https://fedorahosted.org/mirrormanager/wiki/WikiStart has instructions, and a list of items known needing love is at https://fedorahosted.org/mirrormanager/wiki/HelpWanted. I cut my python teeth writing this code, and it's had a few reviews, but there are probably ways to make it better. The TG controller pieces are really pretty hokey - nothing as nice as the bodhi code is. If you've got other ideas, by all means, please let us know. Thanks, Matt -- Matt Domsch Linux Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux Public Mirror Acceptance Template We would be pleased to have you as a public mirror. Thank you for your contribution to Fedora! Please see http://fedoraproject.org/wiki/Infrastructure/Mirroring for guidance, and register your mirror in Mirrormanager at https://admin.fedoraproject.org/mirrormanager. By doing so, you will appear on the mirror list for Fedora 7 and future automatically. Most mirrors should rsync from one of the Tier 1 mirrors listed at http://fedoraproject.org/wiki/Infrastructure/Mirroring or from another mirror close network-wise listed on http://mirrors.fedoraproject.org/publiclist/. Thanks again, Matt Fedora Mirror Wrangler

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure December 2007