Re: Updates from the GNOME Sysadmin Team: New Mirroring service, Owncloud 6
2013/12/12 Dominique Leuenberger a.k.a. Dimstar dims...@opensuse.org There might be something not entirely setup yet. Looking at this I get 11 Mirrors as option, but all of them returned with the same Prio (100) looking at for example http://download.opensuse.org/distribution/13.1/iso/ openSUSE-13.1-Addon-NonOss-BiArch-i586-x86_64.iso.mirrorlist (also based on MirrorBrain) the provided mirrors are clearly differently prioritized. Might be worthy to have a look at this. Thanks for noticing Dominique, mirrors priorities (Prio) should be actually tweaked when, for example, a specific mirror (it being on the same country of the user requesting the file) has more bandwidth or reliability than another and we might want to prefer a redirect to that specific mirror which has more chances to serve the file in the fastest way as possible. That said given I didn't yet have time to investigate the provided bandwidth for each of the mirrors we use, keeping Prio at 100 for each of the mirrors will actually result in MirrorBrain randomly selecting one of the closest mirrors to your area even if that specific mirror has a lower bandwidth than another one close to you. We might want to tweak this parameter a bit as soon as I find the time to get more stats about what our mirrors are providing in terms of bandwidth speed. Thanks again for reporting and have an awesome day! (/me added a note accordingly) -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Updates from the GNOME Sysadmin Team: New Mirroring service, Owncloud 6
Howdy, it's time for yet another round of updates from the GNOME Sysadmin Team. This time it's not about future maintenances or outages but about our completely new mirroring service. As you may have been aware of GNOME has a lot of mirrors around the world but we never took advantage of them and kept using our main mirror kindly served by the Academic Computer Club of the Umea University. (ftp.acc.umu.sebeing a CNAME to ftp.gnome.org) Many mirrors contacted me and the team in the past asking if keeping their mirror around was worth the disk space they were using for our project given the very low amount of downloads they were receiving. (that was expected given download.gnome.org was a plain redirect to ftp.gnome.org, and thus to ftp.acc.umu.se) I personally always answered yes, it was worth keeping the GNOME code synced in as much places in the world as possible but at the same time I felt that we needed a proper mirroring infrastructure to properly serve the downloads through all the mirrors that decided to provide disk space and bandwitdh to support our project. Looking around and thanks to an Olav Vitter's review we decided to move forward and setup a Mirrorbrain [1] istance. You can read more about its features at [2]. After a few days spent making the EPEL packages (Thanks Patrick for the work you put on reviewing and accepting them!), configuring and tweaking, our istance is finally live at [3]. As you will see we have plenty of mirrors based in EU and just one in the US and Asia. I'll be contacting a few mirrors in those zones and eventually welcome them as new GNOME mirrors so we can have our downloads served in the fastest way possible even in remote regions like Australia, Asia and the US itself. (if anyone knows someone interested in mirroring GNOME sources, please redirect the request to supp...@gnome.org) Gving a look at a new indexing table we've introduced on the file indexes of our main mirror can be a good way to get started to how Mirrorbrain works behind the scenes. [4] Obviously all the links that existed before Mirrorbrain are still working just fine but the great difference are them now being served through Mirrorbrain (which then redirects the user to the closest mirror through mod_geoip) itself and SSL. Another good way of testing the whole setup out is by using curl, this way: 'curl -iS https://download.gnome.org/sources/gnome-terminal/3.11/gnome-terminal-3.11.0.tar.xz.mirrorlist ' --- Owncloud release 6 The other update I wanted to report is our Owncloud istance [5] being upgraded to the very latest release being Owncloud 6. As usual please redirect account requests to me or to supp...@gnome.org directly as explained at [6]. [1] http://mirrorbrain.org/ [2] http://mirrorbrain.org/features/ [3] https://download.gnome.org/ [4] https://download.gnome.org/sources/gnome-terminal/3.11/gnome-terminal-3.11.0.tar.xz.mirrorlist [5] http://cloud.gnome.org/ [6] https://wiki.gnome.org/Sysadmin/Owncloud -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Updates from the GNOME Sysadmin Team
On Thu, 2013-11-21 at 22:23 +0100, Andrea Veri wrote: 2013/11/21 Ekaterina Gerasimova kittykat3...@gmail.com [...] When you document how to lock down individual pages to prevent random people from from editing them, please send the link to the mailing lists as it is moderately complicated if one has not done it before. Sure, that can be done this way: 1. Create a page with the following syntax: 'SysadminGroup' 2. add a list of wiki usernames like https://wiki.gnome.org/SysadminGroup 3. add the ACL at the beginning of the wiki page you want to lock down: #acl WikiPageName/SysadminGroup:read,write,delete,admin,revert All:read Beware that the group wiki page name *must* end in 'Group'. Otherwise, you can get an immutable wiki page that nobody can edit [1] (only a sysadmin, Andrea: it would be great if you could delete it :-). Tip from someone who learned that in the hard way (of course, I followed the standard procedure of reading the documentation [2,3] afterwards :-) [1] https://wiki.gnome.org/Travel/CurrentCommittee [2] http://moinmo.in/HelpOnAccessControlLists [3] http://moinmo.in/HelpOnGroups -- Germán Poo-Caamaño http://calcifer.org/ signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Updates from the GNOME Sysadmin Team
On 21 November 2013 15:48, Andrea Veri a...@gnome.org wrote: 2. projects.gnome.org's migration to wiki.gnome.org. The projects.gnome.org website is currently being migrated to the following places: GNOME Apps: https://wiki.gnome.org/Apps GNOME Projects: https://wiki.gnome.org/Projects Both pages are currently under construction. Maintainers and developers will now be able to modify their app / project page without the need of a git account Don't all maintainers have to have a git account anyway? :) and most of all without the need to clone an huge repo like gnomeweb-wml. All these without losing some of the benefits of Git like the history of previous changes and a diff between the various page changes themselves. When you document how to lock down individual pages to prevent random people from from editing them, please send the link to the mailing lists as it is moderately complicated if one has not done it before. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Updates from the GNOME Sysadmin Team
2013/11/21 Ekaterina Gerasimova kittykat3...@gmail.com On 21 November 2013 15:48, Andrea Veri a...@gnome.org wrote: 2. projects.gnome.org's migration to wiki.gnome.org. The projects.gnome.org website is currently being migrated to the following places: GNOME Apps: https://wiki.gnome.org/Apps GNOME Projects: https://wiki.gnome.org/Projects Both pages are currently under construction. Maintainers and developers will now be able to modify their app / project page without the need of a git account Don't all maintainers have to have a git account anyway? :) Not necessarily, someone might just be a random contributor that spots an error on the documentation and wants to fix it right away. Honestly speaking I'm loving this new look, pages are more readable now, with a new design, easier to maintain and modify by everyone having a Wiki account. Have you ever cloned the gnomeweb-wml repository yourself? It's around 600M in size :-) and most of all without the need to clone an huge repo like gnomeweb-wml. All these without losing some of the benefits of Git like the history of previous changes and a diff between the various page changes themselves. When you document how to lock down individual pages to prevent random people from from editing them, please send the link to the mailing lists as it is moderately complicated if one has not done it before. Sure, that can be done this way: 1. Create a page with the following syntax: 'SysadminGroup' 2. add a list of wiki usernames like https://wiki.gnome.org/SysadminGroup 3. add the ACL at the beginning of the wiki page you want to lock down: #acl WikiPageName/SysadminGroup:read,write,delete,admin,revert All:read Have an awesome day! -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Some updates from the GNOME Sysadmin Team
2013/5/17 Andrea Veri a...@gnome.org KGB Bot --- I've been working during the past week on the KGB Bot [4] (it has been a pain to package dozen of perl libraries!), which is a little IRC bot capable of sendind out notifications when a commit occurs on a specific git repository. I'm currently waiting the RH IT to open the specific port on the firewall for the kgb-client to communicate correctly with the bot which is hosted on a machine outside the datacenter where git.gnome.org runs. I'll make sure to send out an additional mail when the service is ready to go accepting new requests. KGB Bot is finally ready to go, if you are interested in receiving commit notifications for a specific GNOME module on an IRC channel hosted at irc.gnome.org, please open a bug against the 'sysadmin' module on Bugzilla or directly mail me the relevant information: 1. repository-name 2. channel-name In addition to this, the Etherpad istance hosted by the GNOME Infrastructure is up and running at https://etherpad.gnome.org. The service is and will be restricted to all the GNOME teams that will request access to it (at the moment the Board, Release Team, Advisory Board, Marketing Team), if you are interested in the service please drop me an e-mail anytime. -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Some updates from the GNOME Sysadmin Team
Thank you for this information, Andrea! We'll greatly benefit from the bot and the etherpad is a lovely addition! I have sent you a request via email regarding this. Thank you for setting this up :) -Sindhu On Fri, May 24, 2013 at 12:00 AM, Andrea Veri a...@gnome.org wrote: 2013/5/17 Andrea Veri a...@gnome.org KGB Bot --- I've been working during the past week on the KGB Bot [4] (it has been a pain to package dozen of perl libraries!), which is a little IRC bot capable of sendind out notifications when a commit occurs on a specific git repository. I'm currently waiting the RH IT to open the specific port on the firewall for the kgb-client to communicate correctly with the bot which is hosted on a machine outside the datacenter where git.gnome.org runs. I'll make sure to send out an additional mail when the service is ready to go accepting new requests. KGB Bot is finally ready to go, if you are interested in receiving commit notifications for a specific GNOME module on an IRC channel hosted at irc.gnome.org, please open a bug against the 'sysadmin' module on Bugzilla or directly mail me the relevant information: 1. repository-name 2. channel-name In addition to this, the Etherpad istance hosted by the GNOME Infrastructure is up and running at https://etherpad.gnome.org. The service is and will be restricted to all the GNOME teams that will request access to it (at the moment the Board, Release Team, Advisory Board, Marketing Team), if you are interested in the service please drop me an e-mail anytime. -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Some updates from the GNOME Sysadmin Team
This is great stuff. The meetbot should help out with those of you doing irc meetings. Please do use the services. -- Sriram Ramkrishna (sriram.ramkrishna_@@_...@.gmail.com (remove _@@_) On Fri, May 17, 2013 at 12:41 PM, Andrea Veri a...@gnome.org wrote: Hello, some time has passed since my latest update so here we come with a few items I've been working on on the past two weeks. New infrastructure-announce mailing list --- From the 8th of May a new mailing list has been started for all the announcements about downtimes, outages, maintenances related to the GNOME Infrastructure. As a side note the mail you are currently reading will be the last that will be kept CCed on desktop-devel-list and foundation-list. Please take a little minute to subscribe yourself to the new list at [1] to not loose any of the updates from the GNOME Sysadmin Team. --- Jabber --- As you may have noticed our Jabber server currently doesn't allow you to add any JID not equal to j...@jabber.gnome.org, that means you can't chat with people having a JID registered on a different server than the one hosted on the GNOME Infrastructure. The problem is related to a specific firewall port not being open, we've taken action on it and the relevant port will be open really soon for the clients to successfully talk with other clients coming from the outside world. --- live.gnome.org --- Our wiki had a really quick maintenance [2] that upgraded it to the latest available MoinMoin's release. (1.9.7) This release takes in a stronger password encryption (it's not based on SHA anymore, but on PASSLIB instead), I would suggest anyone to change their password as soon as possible. In addition to the above, I've cleaned up a bit inactive users, deleted and trashed pages: 1. inactive users (users that registered but never did a single edit since the time they registered their account) were around 23000 (loads of spammers), the current amount of registered and active users went to 6000. Editing pages became really too slow, MoinMoin currently checks each of the registered user's subscriptions list for eventually notifying the user about the change that occurred on the page being edited. That process was taking around 9-10 seconds, and that was actually expected with an amount of 29000 registered users. 2. deleted pages (pages that were marked as 'Deleted' on the wiki) got moved from the data/ directory of live.gnome.org to a backup directory and the cache was cleaned for the changes to take place. 3. trashed pages (pages that were marked as 'Trashed' on the wiki) got moved from the data/ directory of live.gnome.org to a backup directory and the cache was cleaned for the changes to take place. --- MeetBot --- Our Services bot was enhanced with MeetBot, more details are available at [3]. Make good use of it! --- KGB Bot --- I've been working during the past week on the KGB Bot [4] (it has been a pain to package dozen of perl libraries!), which is a little IRC bot capable of sendind out notifications when a commit occurs on a specific git repository. I'm currently waiting the RH IT to open the specific port on the firewall for the kgb-client to communicate correctly with the bot which is hosted on a machine outside the datacenter where git.gnome.org runs. I'll make sure to send out an additional mail when the service is ready to go accepting new requests. That should be all for now, have an awesome weekend! [1] https://mail.gnome.org/mailman/listinfo/infrastructure-announce [2] https://mail.gnome.org/archives/foundation-list/2013-May/msg00033.html [3] https://mail.gnome.org/archives/foundation-list/2013-April/msg00037.html [4] http://kgb.alioth.debian.org -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Some updates from the GNOME Sysadmin Team
Thank Andrea for the information about KGB bot and live.gnome.org wiki! I myself asked in #sysadmin channel about the mysterious Renato Barruco recently :) Am interested in information related to the wiki and bots, please keep us updated with latest happenings about them. You are doing a good job! thank you :) -Sindhu On Sat, May 18, 2013 at 1:11 AM, Andrea Veri a...@gnome.org wrote: Hello, some time has passed since my latest update so here we come with a few items I've been working on on the past two weeks. New infrastructure-announce mailing list --- From the 8th of May a new mailing list has been started for all the announcements about downtimes, outages, maintenances related to the GNOME Infrastructure. As a side note the mail you are currently reading will be the last that will be kept CCed on desktop-devel-list and foundation-list. Please take a little minute to subscribe yourself to the new list at [1] to not loose any of the updates from the GNOME Sysadmin Team. --- Jabber --- As you may have noticed our Jabber server currently doesn't allow you to add any JID not equal to j...@jabber.gnome.org, that means you can't chat with people having a JID registered on a different server than the one hosted on the GNOME Infrastructure. The problem is related to a specific firewall port not being open, we've taken action on it and the relevant port will be open really soon for the clients to successfully talk with other clients coming from the outside world. --- live.gnome.org --- Our wiki had a really quick maintenance [2] that upgraded it to the latest available MoinMoin's release. (1.9.7) This release takes in a stronger password encryption (it's not based on SHA anymore, but on PASSLIB instead), I would suggest anyone to change their password as soon as possible. In addition to the above, I've cleaned up a bit inactive users, deleted and trashed pages: 1. inactive users (users that registered but never did a single edit since the time they registered their account) were around 23000 (loads of spammers), the current amount of registered and active users went to 6000. Editing pages became really too slow, MoinMoin currently checks each of the registered user's subscriptions list for eventually notifying the user about the change that occurred on the page being edited. That process was taking around 9-10 seconds, and that was actually expected with an amount of 29000 registered users. 2. deleted pages (pages that were marked as 'Deleted' on the wiki) got moved from the data/ directory of live.gnome.org to a backup directory and the cache was cleaned for the changes to take place. 3. trashed pages (pages that were marked as 'Trashed' on the wiki) got moved from the data/ directory of live.gnome.org to a backup directory and the cache was cleaned for the changes to take place. --- MeetBot --- Our Services bot was enhanced with MeetBot, more details are available at [3]. Make good use of it! --- KGB Bot --- I've been working during the past week on the KGB Bot [4] (it has been a pain to package dozen of perl libraries!), which is a little IRC bot capable of sendind out notifications when a commit occurs on a specific git repository. I'm currently waiting the RH IT to open the specific port on the firewall for the kgb-client to communicate correctly with the bot which is hosted on a machine outside the datacenter where git.gnome.org runs. I'll make sure to send out an additional mail when the service is ready to go accepting new requests. That should be all for now, have an awesome weekend! [1] https://mail.gnome.org/mailman/listinfo/infrastructure-announce [2] https://mail.gnome.org/archives/foundation-list/2013-May/msg00033.html [3] https://mail.gnome.org/archives/foundation-list/2013-April/msg00037.html [4] http://kgb.alioth.debian.org -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ foundation-list mailing list foundation-l...@gnome.org https://mail.gnome.org/mailman/listinfo/foundation-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Some updates from the GNOME Sysadmin Team
Hello, some time has passed since my latest update so here we come with a few items I've been working on on the past two weeks. New infrastructure-announce mailing list --- From the 8th of May a new mailing list has been started for all the announcements about downtimes, outages, maintenances related to the GNOME Infrastructure. As a side note the mail you are currently reading will be the last that will be kept CCed on desktop-devel-list and foundation-list. Please take a little minute to subscribe yourself to the new list at [1] to not loose any of the updates from the GNOME Sysadmin Team. --- Jabber --- As you may have noticed our Jabber server currently doesn't allow you to add any JID not equal to j...@jabber.gnome.org, that means you can't chat with people having a JID registered on a different server than the one hosted on the GNOME Infrastructure. The problem is related to a specific firewall port not being open, we've taken action on it and the relevant port will be open really soon for the clients to successfully talk with other clients coming from the outside world. --- live.gnome.org --- Our wiki had a really quick maintenance [2] that upgraded it to the latest available MoinMoin's release. (1.9.7) This release takes in a stronger password encryption (it's not based on SHA anymore, but on PASSLIB instead), I would suggest anyone to change their password as soon as possible. In addition to the above, I've cleaned up a bit inactive users, deleted and trashed pages: 1. inactive users (users that registered but never did a single edit since the time they registered their account) were around 23000 (loads of spammers), the current amount of registered and active users went to 6000. Editing pages became really too slow, MoinMoin currently checks each of the registered user's subscriptions list for eventually notifying the user about the change that occurred on the page being edited. That process was taking around 9-10 seconds, and that was actually expected with an amount of 29000 registered users. 2. deleted pages (pages that were marked as 'Deleted' on the wiki) got moved from the data/ directory of live.gnome.org to a backup directory and the cache was cleaned for the changes to take place. 3. trashed pages (pages that were marked as 'Trashed' on the wiki) got moved from the data/ directory of live.gnome.org to a backup directory and the cache was cleaned for the changes to take place. --- MeetBot --- Our Services bot was enhanced with MeetBot, more details are available at [3]. Make good use of it! --- KGB Bot --- I've been working during the past week on the KGB Bot [4] (it has been a pain to package dozen of perl libraries!), which is a little IRC bot capable of sendind out notifications when a commit occurs on a specific git repository. I'm currently waiting the RH IT to open the specific port on the firewall for the kgb-client to communicate correctly with the bot which is hosted on a machine outside the datacenter where git.gnome.org runs. I'll make sure to send out an additional mail when the service is ready to go accepting new requests. That should be all for now, have an awesome weekend! [1] https://mail.gnome.org/mailman/listinfo/infrastructure-announce [2] https://mail.gnome.org/archives/foundation-list/2013-May/msg00033.html [3] https://mail.gnome.org/archives/foundation-list/2013-April/msg00037.html [4] http://kgb.alioth.debian.org -- Cheers, Andrea Debian Developer, Fedora / EPEL packager, GNOME Sysadmin, GNOME Foundation Membership Elections Committee Chairman Homepage: http://www.gnome.org/~av ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
