19:04:48 #startmeeting 19:04:48 Meeting started Sat Dec 5 19:04:48 2009 UTC. The chair is MerlinTHP. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:04:48 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:04:57 #topic MirrorManager 19:05:21 Presentation by Matt Domsch on Fedora's MirrorManager system 19:07:34 MirrorManager provides a an extensible content distribution system delivering Fedora and EPEL bits to users 19:07:52 All done with free and open source software 19:08:05 At least 2 million end users 19:08:12 At least 300 mirror server admins 19:09:07 Users want current content, fast inexpensive downloads 19:09:38 Mirror admins want to serve local users quickly and inexpensively, and only the content they want 19:10:05 Fedora Infrastructure Team users mirrors to reduce fedora data centre bandwidth 19:11:12 rsync from master mirrors to local mirrors 19:11:26 yum requests mirrors from a central director 19:12:19 ISO downloads from download.fedoraproject.org are automatically redirected to a mirror 19:12:42 yum uses the mirrorlist from mirrors.fedoraproject.org 19:13:24 Mirror selection algorithm: 19:13:27 Same network block 19:13:36 Same Autonomous System Number 19:13:47 Client on Internet2 gets Internet2 mirror 19:13:49 Same country 19:13:51 Same continent 19:13:57 Any global mirror 19:14:09 All lookups can be IPv4 or IPv6. 19:14:31 Country and continent info provided by MaMind GeoLite 19:14:37 MaxMind 19:16:20 ASN info grabbed from internet BGP tables 19:17:56 A fedora mirror needs: 19:18:02 200Gb to 1TB of disk space 19:18:18 You need to create a Fedora Account System account 19:18:38 Create a site in MirrorManager https://admin.fedoraproject.org/mirrormanager 19:18:52 Fill in netblocks / AS info 19:18:57 rsync from antoher mirror 19:19:53 Want to recruit mirrors in china, india, russia, brazil 19:20:11 Matt's presentation ends. 19:21:48 Presentation on CHASM by Robert Escriva 19:22:56 CHASM is a project designed to improve the software used for mirroring to make it possible for mirror maintainers to more easily manage advanced configs 19:23:19 CHASM will provide: 19:23:24 atomic updates 19:23:30 data integrity assuranaces 19:23:42 peer-to-peer network structure 19:23:44 easy admin tools 19:23:47 sane migration path 19:23:59 CHASM is not intended to provide: 19:24:10 some stuff that went by too quick, sorry 19:24:35 Normal tree-type mirror distribution 19:24:49 CHASM provides a more mesh-like structure 19:24:59 CHASM relies on filesystem atomic operations 19:27:26 Uses cryptographic hashing (SHA2 by default) of all content 19:28:32 CHASM tools automatically update signatures on content update 19:31:24 Uses a peer-to-peer network structure to cut down latency caused by tiered mirror structure 19:31:36 Mirrors ask for content from any mirror that has it 19:31:54 Can be configured with single-master, turning off peer-to-peer 19:32:55 Admin tools: fsck (use the signed manifest to verify the mirror), status (check which upstream version is mirrored), update (force a manual update of the mirror) 19:33:36 Sane migration path provided by not impacting end user and downstream rsync operation 19:35:56 Two parts: network daemon and staging tool 19:36:06 ( sorry, really bad wifi lag ) 19:36:49 Plan to have a beta quality release before the end of 2009 19:37:41 * nirik wonders what it's written in/packaged? ie, can it run on various mirrors that run different os/versions? 19:40:22 Currently prototyped in python 19:40:32 Not averse to writing in C++ if speed neded 19:41:34 cool. (Hopefully portable to pythons that might be on rhel4/rhel5 machines) 19:42:36 ototyped in C++ 19:42:59 No idea where that came from, sorry 19:45:29 Mirrors contact a central tracker to ask for peers 19:46:13 Private mirrors can request that the tracker not tell other peers about it 19:48:36 Intention is to make setup simple: install software, than grab a .chasm configuration seed file. 19:55:12 Supports exclusions 19:55:23 path-based exclusion specification 19:56:11 #endmeeting