fedorahosted read link
by emmanuel segura
Hello List
Maybe this is not the best way to post this :) but i'll try to explain what
i see, if i go to this link https://fedorahosted.org/readahead/ in the Docs
sessions, i get this error when click on README link
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Network Error (dns_unresolved_hostname)
Your requested host "git.fedoraproject.org" could not be resolved by DNS.
For assistance, contact your network support team.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Thanks
Emmanuel
--
esta es mi vida e me la vivo hasta que dios quiera
10 years, 8 months
Meeting Agenda Item: Introduction Ulrich Habel (rhaen)
by Ulrich Habel
Hi list,
I'd like to join the team. Here is the short introduction and the meeting item.
IRC handle: rhaen
Skills: puppet (quite advanced), build infrastructures, perl, selinux, ldap
Willing to learn: python (maybe), the fedora project :)
What you'd like to work on/issues: I saw some puppet/selinux/build related stuff, I am more infrastructure related than web related (but this might change).
Issues: Still looking through the tickets
Regards,
Uli
10 years, 8 months
Fedora 19 Final Freeze in effect.
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 19
final release.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
git clone http://infrastructure.fedoraproject.org/infra/ansible.git
scripts/freezelist -i inventory/inventory
Anything listed as freezes is frozen until 2013-07-03 (or later if Beta
slips). Frozen hosts should have no changes made to them without a
signoff on the change from at least 2 sysadmin-main or rel-eng members.
Thanks,
kevin
10 years, 8 months
Wiki edit statistics - past few months
by Robyn Bergeron
Hi,
A bit of background regarding this page:
https://fedoraproject.org/wiki/Statistics
Once a week I get an automated email from a script that Paul has had set up since his FPL days, which contains the following content:
* Updates for the total release connections section, which I use to (with manual calculator work) update current release connections info, and I also get info about direct downloads, which goes into the direct downloads section of the wiki.
Once a month, I also get an email with the following information (example from end of June), which I also paste into the wiki:
Fedoraproject.org visitors for 2013-06: 1877495
Wiki edits for 2013-06: Total=6785, Unique=993
While this work is admittedly fairly tedious, I have found that doing them in a batch of several at once is a bit more time efficient, as I have to have the Stats page, my email, a calculator, the addition of lots of commas, and the legacy statistics page on hand, and thus until tonight I was about 4 weeks behind. (Have I mentioned just how much I look forward to an automated version of this? :D)
In any case: I was pasting in the numbers for May & June tonight - and this is what the past few months of updates to the wiki, as well as # of wiki updates from unique IPs, looks like:
Period Total edits Edits from unique IPs
January 2013 5,262 771
February 2013 2,807 544
March 2013 3,489 621
April 2013 6,416 804
May 2013 23,359 1,172
June 2013 6,785 993
A few points of interest: We normally see an uptick in the number of total edits/unique IPs in the month of release - mostly due (I suspect) to test days, TC/RC test matrices, etc. Our all-time high was 17k in May 2010; since June 2011, the number has been relatively steady, hovering between 2500 and 7k.
So obviously - May is .... way, way, way out of the norm, beyond the highest high we've ever had, and June seemed to settle back into a more normal routine.
Does anyone have any clue what happened in May? Did we have an exorbitant amount of spam? (Or do we likely have an exorbitant amount of spam still lingering on the wiki?) I tried using the "contributions" history but didn't really come up with anything (other than noticing that for "new accounts" - nothing shows up prior to May 15 for the month of may).
Thoughts?
-robyn
10 years, 8 months
[Freeze Break] Remove app05-08 for pkgdb
by Toshio Kuratomi
We've been seeing intermittent timeouts with a particular long running pkgdb
url. In an attempt to narrow down where the problem is coming from we'd
like to remove sending pkgdb requests to app05-app08. Those are backup app
servers that don't live in phx so the latency for them to talk to the db
server is high. For this particular page, it takes around 35s to get the
page from app01-04. It takes 2.5-3.5 minutes (roughly) to get the page from
app05-08.
We somewhat expect that the problem will continue but doing this will allow
us to eliminate the non-phx app servers as the source of the timeout.
Could I get two +1's for the following change?
diff --git a/modules/haproxy/files/haproxy.cfg b/modules/haproxy/files/haproxy.cfg
index b796235..ed45179 100644
--- a/modules/haproxy/files/haproxy.cfg
+++ b/modules/haproxy/files/haproxy.cfg
@@ -65,9 +65,9 @@ listen pkgdb 0.0.0.0:10003
server app2 app2:80 check inter 10s rise 2 fall 3
server app3 app3:80 check inter 10s rise 2 fall 3
server app4 app4:80 check inter 10s rise 2 fall 3
- server app05 app05:80 backup check inter 15s rise 2 fall 3
- server app6 app6:80 backup check inter 15s rise 2 fall 3
- server app08 app08:80 backup check inter 15s rise 2 fall 3
+# server app05 app05:80 backup check inter 15s rise 2 fall 3
+# server app6 app6:80 backup check inter 15s rise 2 fall 3
+# server app08 app08:80 backup check inter 15s rise 2 fall 3
# server bapp1 bapp1:80 backup check inter 10s rise 2 fall 3
option httpchk GET /pkgdb/collections/
-Toshio
10 years, 8 months
retroactive freeze break: exclude old staged content on download-ib01
by Kevin Fenzi
I just applied the following:
diff --git a/modules/mirrormanager/manifests/init.pp b/modules/mirrormanager/manifests/init.pp
index ad24df5..db33566 100644
--- a/modules/mirrormanager/manifests/init.pp
+++ b/modules/mirrormanager/manifests/init.pp
@@ -338,7 +338,7 @@ class mirrormanager::sync {
}
cron { "releng-sync":
- command => "/usr/local/bin/lock-wrapper staging '/usr/bin/rsync -qaH --progress --numeric-ids --exclude deltaisos/archive --delete --delete-delay --delay-updates alt.fedoraproject.org::fedora-stage /srv/pub/alt/stage/'",
+ command => "/usr/local/bin/lock-wrapper staging '/usr/bin/rsync -qaH --progress --numeric-ids --exclude deltaisos/archive --exclude 19-Alpha --exclude 19-Beta --delete --delete-delay --delay-updates alt.fedoraproject.org::fedora-stage /srv/pub/alt/stage/'",
user => 'root',
minute => [ 15 ]
}
This is to allow download-ib01 to exclude the old Alpha/Beta content
so it has space to mirror the actual release content. Since we need
to get it updated asap as some people pull from it, I went ahead
and applied this.
Retroactive +1s? or better ways to do it?
:)
kevin
10 years, 8 months
mirrormanager support for the cloud image
by Matthew Miller
Um, sorry, this is kind of a last-minute afterthought, so I'm not expecting
it for F19 launch or anything crazy. But:
For F19, we're putting cloud images on the mirrors. In the staging tree, the
URL is like this:
https://dl.fedoraproject.org/pub/alt/stage/19-RC1/Images/x86_64/Fedora-x8...
and I presume that the final pattern will be
../19/Images/x86_64/Fedora-x86_64-19-20130624-sda.qcow2
(Or possibly s/Images/Cloud/ -- I had thought that's what we previously
agreed but I need to dig that up.)
Is there a way that we could make permanent URLs for the following:
- per-versionsorted list of URLs to the image on mirrors
- per-version redirect to the closest (or at least randomly chosen) image suitable
for giving to OpenStack Glance directly
- an unversioned URL redirecting to the latest per-version list
- an unversioned URL redirecting to the latest-version redirect
I'm just guessing that mirrormanager is the best place for this. I'm happy
with any other solution....
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>
10 years, 8 months