infrastructure September 2009

infrastructure@lists.fedoraproject.org

43 participants
43 discussions

Fedora Insight Zikula on pt6 Is About To Be Upgraded
by Affix 05 Sep '09

05 Sep '09

Hey Guys, I am about to Upgradde pt6 zikula to Zikula 1.1.2 The upgrade process should take between 10-20 Minutes using the zikula patch files. I have backed up the database to : /usr/share/zikula-preupgrade-backup The Theme has been copied to the theme SVN as mentioned in a previous email to the designs list. Regards, Keiran Smith - Fedora Ambassador / BugZapper / Designer - <affix(a)fedoraproject.org> - Free Software Foundation Associate - <keiran.smith(a)member.fsf.org> - http://keiran-smith.net - Call me on +44 (0) 131 208 4347

2 2

Licensing policy for apps developed by Fedora Infrastructure now in effect
by Toshio Kuratomi 05 Sep '09

05 Sep '09

Over the past few months, Fedora Infrastructure has been discussing having a consistent set of licenses for applications and scripts we create for Fedora. The goals of doing this were to * Be able to share code among the various programs that we write. * Not have our libraries force a specific license on the apps that we write. * Not have conflicting licenses between our apps and our libraries * Have a clear understanding of the steps we must take whenever we want to move code from an application under one license to a library under a different one. * Protect the code we write from being taken proprietary (note, this is not the same for every author. Mirrormanager, for instance, is under the MIT/X11 License). * Be able to stay compliant with licenses within our production, staging, and publictest environments At last week's meeting we made a decision about which licenses would best fit our needs. The results are recorded here: https://fedoraproject.org/wiki/Infrastructure_Licensing The basics are: * license code that is meant to be used as a library as LGPLv2+. * license code that's meant to be used as an application as GPLv2+. * If we want to write something and use another license we should discuss it to figure out how it's going to impact us and whether there's a better way to achieve our goals first. Most of our apps are currently under GPLv2(only) so we're going to be working to change the licensing on those apps over time to reflect GPLv2 or later. If you find something that we've written that's not under GPLv2+ (or LGPLv2+) that you want to use, please let us know so we can either get to work on making the license match the guidelines or let you know why it's not being changed. The one other thing for Infrastructure developers and System Admins to note in the Policy is the section on handling AGPLv3 applications. During the discussions about whether to use AGPLv3+ for our web applications we found and delimited many issues that need to be addressed when deploying AGPLv3+ licensed code. The aGPL portion of the policy is our first attempt at keeping us compliant with any code that is under this license. Highlights are: * Apps deployed to production under AGPL must be deployed from RPMs. Any hotfixes to those apps must have the patch in a ticket in trac on http://fedorahosted.org/fedora-infrastructure with the keyword HOTFIX. * Any AGPL app deployed in infrastructure must have links in the footer to the fedora-infrastructure SRPM repo and the trac query that pulls up our hotfixes so that people can find the exact source that we're running at any given time. * Staging must follow the same rules regarding SRPM and hotfixes. Once again, failing to link to the exact source for what we have running would put us out of compliance. * No AGPL apps can be hosted on publictest boxes at this time as publictest boxes are intended for development and the high rate of change in development is not conducive for constantly updating RPMS or patches in trac. If there's demand for publictest hosting of AGPL apps we'll need to design some method of restricting who can access the applications running there to satisfy the legal requirements. -Toshio

3 3

[Important] app7 information Re: [puppet] Add app7 to main rotation for most apps, follow up to fedora-infrastructure-list
by Nigel Jones 03 Sep '09

03 Sep '09

Hi Guys, I just want to provide an explanation at whats going on here with my recent commits, in particular this one! So here is the run down... app7 is deployed as a KVM guest on xen6, both are running Red Hat Enterprise Linux 5 update 4 (the latest and greatest), both had been running without load, stable for around 30 days which is great (xen6 was running Beta at the time, and app7 running 5.3). Today, we decided to put it into production to serve two purposes. 1. as a test of KVMs abilities 2. as a test of if our stuff works with 5.4 The good news, is that everything seems to be working so I've added it to haproxy, with two exceptions. 1. fedoraproject.org wiki 2. smolts.org wiki Both require a process run on our filer so we can mount the required directories, I'll enable these sites in a day or two. If you notice oddities that seem to be as a result to this change with: * mirrorlist * pkgdb * docs.fedoraproject.org * smolt * mirrormanager * bodhi * fedora community * (or very very unlikely) Elections App ;) Please let me, Mike and Smooge know, and if it's really really bad, remove the line from the haproxy.cfg for app7 and that application (and create a fedora-infrastructure ticket assigned to me (nigelj) please). I have verified that these applications load okay though. - Nigel ----- "Nigel Jones" <nigelj(a)fedoraproject.org> wrote: > commit 1088959810b6a0604965f62ce7fa067081658cc6 > Author: Nigel Jones <nigelj(a)puppet1.fedora.phx.redhat.com> > Date: Thu Sep 3 06:47:36 2009 +0000 > > Add app7 to main rotation for most apps, follow up to > fedora-infrastructure-list > > modules/haproxy/files/haproxy.cfg | 11 ++++++++++- > 1 files changed, 10 insertions(+), 1 deletions(-) > --- > diff --git a/modules/haproxy/files/haproxy.cfg > b/modules/haproxy/files/haproxy.cfg > index d9a02e3..8247023 100644 > --- a/modules/haproxy/files/haproxy.cfg > +++ b/modules/haproxy/files/haproxy.cfg > @@ -47,6 +47,7 @@ listen mirror-lists 0.0.0.0:10002 > server app4 app4.fedora.phx.redhat.com:80 check inter 5s rise 2 > fall 3 > server app5 app5.vpn.fedoraproject.org:80 check inter 10s rise 2 > fall 3 > server app6 app6.vpn.fedoraproject.org:80 check inter 10s rise 2 > fall 3 > + server app7 app7.fedora.phx.redhat.com:80 check inter 5s rise 2 > fall 3 > server bapp1 bapp1.fedora.phx.redhat.com:80 backup check inter > 5s rise 2 fall 3 > option httpchk GET /mirrorlist > > @@ -58,6 +59,7 @@ listen pkgdb 0.0.0.0:10003 > server app4 app4.fedora.phx.redhat.com:80 check inter 10s rise 2 > fall 3 > server app5 app5.vpn.fedoraproject.org:80 backup check inter 15s > rise 2 fall 3 > server app6 app6.vpn.fedoraproject.org:80 backup check inter 15s > rise 2 fall 3 > + server app7 app7.fedora.phx.redhat.com:80 check inter 10s rise 2 > fall 3 > server bapp1 bapp1.vpn.fedoraproject.org:80 backup check inter > 10s rise 2 fall 3 > option httpchk GET /pkgdb > > @@ -76,6 +78,7 @@ listen docs 0.0.0.0:10005 > server app4 app4.fedora.phx.redhat.com:80 check inter 5s rise 2 > fall 3 > server app5 app5.vpn.fedoraproject.org:80 check inter 5s rise 2 > fall 3 > server app6 app6.vpn.fedoraproject.org:80 check inter 5s rise 2 > fall 3 > + server app7 app7.fedora.phx.redhat.com:80 check inter 5s rise 2 > fall 3 > server bapp1 bapp1.fedora.phx.redhat.com:80 backup check inter > 5s rise 2 fall 3 > option httpchk GET /docs/ > # > @@ -87,6 +90,7 @@ listen smolt 0.0.0.0:10006 > server app4 app4.fedora.phx.redhat.com:80 check inter 10s rise 2 > fall 5 > server app5 app5.vpn.fedoraproject.org:80 check inter 20s rise 2 > fall 5 > server app6 app6.vpn.fedoraproject.org:80 check inter 20s rise 2 > fall 5 > + server app7 app7.fedora.phx.redhat.com:80 check inter 10s rise 2 > fall 5 > server bapp1 bapp1.fedora.phx.redhat.com:80 backup check inter > 20s rise 2 fall 5 > option httpchk GET /smolt/reports/search_profiles > > @@ -97,7 +101,8 @@ listen voting 0.0.0.0:10007 > server app3 app3.fedora.phx.redhat.com:80 check inter 2s rise 2 > fall 5 > server app4 app4.fedora.phx.redhat.com:80 check inter 2s rise 2 > fall 5 > server app5 app5.vpn.fedoraproject.org:80 backup check inter 2s > rise 2 fall 5 > - server app6 app6.vpn.fedoraproject.org:80 check inter 2s rise 2 > fall 5 > + server app6 app6.vpn.fedoraproject.org:80 backup check inter 2s > rise 2 fall 5 > + server app7 app7.fedora.phx.redhat.com:80 check inter 2s rise 2 > fall 5 > server bapp1 bapp1.fedora.phx.redhat.com:80 backup check inter > 2s rise 2 fall 5 > option httpchk GET /voting/ > > @@ -109,6 +114,7 @@ listen mirrormanager 0.0.0.0:10008 > server app4 app4.fedora.phx.redhat.com:80 check inter 15s rise 2 > fall 3 > server app5 app5.vpn.fedoraproject.org:80 backup check inter 20s > rise 2 fall 3 > server app6 app6.vpn.fedoraproject.org:80 backup check inter 20s > rise 2 fall 3 > + server app7 app7.fedora.phx.redhat.com:80 check inter 15s rise 2 > fall 3 > server bapp1 bapp1.fedora.phx.redhat.com:80 backup check inter > 15s rise 2 fall 3 > option httpchk GET /mirrormanager/static/css/fedora.css > > @@ -120,6 +126,7 @@ listen bodhi 0.0.0.0:10009 > server app4 app4.fedora.phx.redhat.com:80 check inter 20s rise 2 > fall 3 > server app5 app5.vpn.fedoraproject.org:80 backup check inter 35s > rise 2 fall 3 > server app6 app6.vpn.fedoraproject.org:80 backup check inter 35s > rise 2 fall 3 > + server app7 app7.fedora.phx.redhat.com:80 check inter 20s rise 2 > fall 3 > server bapp1 bapp1.fedora.phx.redhat.com:80 backup check inter > 20s rise 2 fall 3 > option httpchk GET /updates/nagios > > @@ -136,6 +143,7 @@ listen freemedia 0.0.0.0:10011 > server app4 app4.fedora.phx.redhat.com:80 check inter 5s rise 2 > fall 3 > server app5 app5.vpn.fedoraproject.org:80 backup check inter 15s > rise 2 fall 3 > server app6 app6.vpn.fedoraproject.org:80 backup check inter 15s > rise 2 fall 3 > + server app7 app7.fedora.phx.redhat.com:80 check inter 5s rise 2 > fall 3 > server bapp1 bapp1.fedora.phx.redhat.com:80 backup check inter > 5s rise 2 fall 3 > option httpchk GET /freemedia/FreeMedia-form.html > > @@ -147,6 +155,7 @@ listen community 0.0.0.0:10012 > server app4 app4.fedora.phx.redhat.com:80 check inter 10s rise 2 > fall 3 > server app5 app5.vpn.fedoraproject.org:80 backup check inter 15s > rise 2 fall 3 > server app6 app6.vpn.fedoraproject.org:80 backup check inter 15s > rise 2 fall 3 > + server app7 app7.fedora.phx.redhat.com:80 check inter 10s rise 2 > fall 3 > server bapp1 bapp1.fedora.phx.redhat.com:80 backup check inter > 5s rise 2 fall 3 > option httpchk GET > /community/apps/fedoracommunity.overviewresource

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure September 2009