The addition of mm-frontend02 yesterday meant that all the dynamically
generated fedmsg config needs to add a entry for it.
This means the check/diff daily report is pretty large because all
these are pending.
I would like to run the master playbook with -t fedmsgdconfig and then
I don't think there will be any issues.
This will make the following changes on fedmsg enabled hosts:
--- before: /etc/fedmsg.d/endpoints.py
+++ after: /srv/web/infra/ansible/roles/fedmsg/base/templates/endpoints.py.j2
@@ -41,20 +41,24 @@
"tcp://ask02.%s:30%02i" % (suffix, i)
for i in range(6)
# The mirrormanager2 frontend runs as 2 processes with 1 thread each.
"tcp://mm-frontend01.%s:30%02i" % (suffix, i)
+ for i in range(2)
+ "mirrormanager2.mm-frontend02": [
+ "tcp://mm-frontend02.%s:30%02i" % (suffix, i)
for i in range(2)
# mizdebsk says he thinks we'll need four sockets. Two services
# (koschei-resolver and koschei-polling) are only sending messages, one
# service (koschei-watcher) can both send and receive them. The wsgi
# webapp doesn't use fedmsg at all and all services are single-threaded
# koschei-watcher uses two endpoints
"tcp://koschei01.%s:30%02i" % (suffix, i)
Can I get two +1's for:
Author: Adrian Reber <adrian(a)lisas.de>
Date: Wed Jul 29 19:20:19 2015 +0000
Reduce the number of parallel crawled hosts to 29.
There has been a report that the MM database was not updated correctly
and dmesg on mm-crawler01 shows three OOM killed crawlers.
diff --git a/roles/mirrormanager/crawler/files/crawler.cron b/roles/mirrormanager/crawler/files/crawler.cron
index 43f85f7..f77d61d 100644
@@ -1,8 +1,8 @@
# run the crawler twice a day
# logs sent to /var/log/mirrormanager/crawler.log and crawl/* by default
-# 30 threads with 32GB of RAM seems to work so far
+# 29 threads with 32GB of RAM seems to work so far
# [ "`hostname -s`" == "mm-crawler02" ] && sleep 2h is used to start the crawl
# later on the second crawler to reduce the number of parallel accesses to
# the database
-0 */12 * * * mirrormanager [ "`hostname -s`" == "mm-crawler02" ] && sleep 2h; /usr/bin/mm2_crawler --timeout-minutes 180 --threads 30 `/usr/local/bin/run_crawler.sh 2` > /dev/null 2>&1
+0 */12 * * * mirrormanager [ "`hostname -s`" == "mm-crawler02" ] && sleep 2h; /usr/bin/mm2_crawler --timeout-minutes 180 --threads 29 `/usr/local/bin/run_crawler.sh 2` > /dev/null 2>&1
I was planning on making a new release of pagure today, not realizing that we
were entering freeze.
I would like to hear more opinions about pushing this release, here is the
- Include the tags in the JSON representation of a project
- Add the ability to open a pull-request from a git repo not hosted on pagure
- Fix pagination when browsing the list of commits
- Fix the fork button when viewing the Settings of a project
- Adjust the example apache configuration file
- Add a favicon with pagure's logo
- Fix asynchronous commentting on pull-requests
- Start working on some documentation on how to install pagure
- Do not blink the tittle of the page if the page is already on focus
- Retrieve ssh key from FAS and set it up in pagure if none is currently set-up
The remote PR needs a small DB change, everything else is pretty much bug fixes
or minor improvements.
Good morning everyone,
I just released a new version of MirrorManager2: 0.4.1
Here is its changelog:
* Tue Jul 28 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.4.1-1
- Update to 0.4.1
- If the host has no categories do not auto-disable it (Adrian Reber)
- Different small umdl and crawler fixe (Adrian Reber)
As you can see it is a bug-fix release with few fixes by Adrian.
It is currently running in staging and will be pushed to prod once testing is
we are now in the infrastructure freeze leading up to the Fedora 23
Alpha release. This is a pre-release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 23 Alpha when it's available.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
git clone https://infrastructure.fedoraproject.org/infra/ansible.git
scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2015-08-12. (or later if
Alpha slips). Frozen hosts should have no changes made to them
without a sign-off on the change from at least 2 sysadmin-main or
rel-eng members, along with (in most cases) a patch of the exact
change to be made to this list.
Over the last few weeks we have been working to get all the old
instances off our old private cloud and on to the new one (or just
terminated if no longer used).
I'd like to try and get that all completed by this friday (2015-07-31).
There's a few people I have mailed but haven't heard back from, and if
they don't say anything by friday their instances may well be
In progress still is jenkins. I will look at moving the builders to the
new cloud in the next few days and hopefully we can migrate to the
fedora-22 based jenkins in the new cloud soon.
I mailed the following people last week and again this morning, but
haven't heard anything back yet. If you know any of these folks, please
let them know their instances will be terminated this friday:
skottler - skottler-rhel7
bkabrda ncoghlan - devpi
besser82 - shogun-ca
Please let me know if you have any issues or concerns with a friday
deadline for the old cloud to go away.