Hi all -
Just an FYI that I have enabled a watchdog timer (virtual) device in our
virt-install command for new VMs in staging, a few days ago. This is
something Kevin asked me to look into a while back.
There shouldn't be any noticeable changes, but as staging VMs get
rebuilt, they will have a /dev/watchdog device and a 'watchdog' service
running. Relevant commit is here: .
Let me know if there are any problems or questions or reboot loops
(hopefully not!) on new VM builds. Existing (non-rebuilt) VMs do not
have the watchdog device at this time, so this message only concerns new
or rebuilt VMs.
Also, if anyone is really familiar with the watchdog daemon and can
suggest other checks to add, please chime in! It looks like it is
capable of a fair number of types of checks, but right now I just have
it in the most simple configuration possible.
If this goes well with stg VM rebuilds for a while, we can drop the
conditionals and move it to prod in a similar fashion (as VMs get
rebuilt). Alternatively, we could edit our VMs XML files and add the
device manually, and install watchdog (via ansible) on everything. I
defer to Kevin for the decision on that.
I'm starting this as a separate thread to offer an alternative solution
for hosting SIP and XMPP.
Basically, I would be happy to continue running the services on my own
infrastructure with the fedoraproject.org domain. I'm running Xen Cloud
Platform in a data center with plenty of bandwidth (both IPv4 and IPv6).
There are two things that the Fedora infrastructure team would still
need to assist with though:
a) creating the DNS SRV and NAPTR records under fedoraproject.org to
direct all SIP and XMPP activity to the servers
b) providing TLS certificates for
to be installed on the servers. Wildcard certificates are not valid
Running the services with the fedoraproject.org domain will engage more
people and allow me to launch an XMPP service, which isn't running at
all on fedrtc.org due to the potential inconvenience if people had to
move buddy lists to fedoraproject.org in future.
At some point, it would be good to see fedrtc.org migrate to Fedora
infrastructure and use the fedoraproject.org domain
I'd be happy to submit the full request for resources but I just want
to see if there is any initial comment on it. Here is a list of what is
- it uses a PostgreSQL database schema
- it requires some DNS entries (SRV and NAPTR), examples
- it needs a TLS cert for fedoraproject.org on the host(s) where it runs
- it has static HTTP content and PHP that is currently hosted with all
but one problem on a RHEL7 httpd. Content is in Github, it could
be presented as an RPM if necessary.
- all packages are in EPEL7, except:
cajun-json in EPEL6, in testing for EPEL7
resiprocate in Fedora, builds from SRPM on RHEL7
- the SIP proxy is a single daemon, managed by systemctl. All settings
in a single file, /etc/repro/repro.config
- the TURN server process is also a single daemon, managed by systemctl.
All settings in a single file, /etc/reTurn/reTurnServer.config
Just to clarify the scope of this: it is not a full telephony service
like Asterisk, just a SIP proxy and TURN server. There is no persistent
state information (as there would be for voicemail, email service, etc)
and no customized routing.
Ongoing maintenance requirements:
- TLS certificate renewals
- monitoring the ports
- package updates from time to time
It currently runs on a lab machine, I'd be happy to arrange SSH access
to the Fedora Infrastructure team to see exactly what is involved and
verify that it is manageable.
Good Morning everyone,
I just cut a new release of pagure: 0.1.32
There are quite a few changes, mostly bug fixes though.
Here is the corresponding changelog:
* Fri Nov 13 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.32-1
- Update to 0.1.32
- Fix the example configuration file
- Make pagure work on MySQL
- Hide sections on the front page only if the user is logged out
- Fix the release page where sometime tags are commits
- Escape the raw html in markdown
- Decode the bytes returned by pygit2 to try to guess if the content is a text
- Fix the 'Clear' button on the pull-request page (farhaanbukhsh)
- Fix installing pagure in a venv
- Fix uploading images when editing the first comment of a ticket
- Let the author of the merge commit be the user doing the merge
- Suggest the title of the PR only if it has one and only one commit in
- Do not hide sections on the user page if we set some to be hidden on the front
- Forward the head to the commits page to fix the pull-request button
- Ensure we create the git-daemon-export-ok when forking a repo (fixes cloning
- Add instructions on how to get pagure working in a venv (Daniel Mach)
- Improve the way we retrieve and check pygit2's version (Daniel Mach)
This is happily running in stg and prod.
The infrastructure team will be having it's weekly meeting tomorrow,
2015-10-15 at 18:00 UTC in #fedora-meeting on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
NOTE: Gobby has changed, we are now using gobby05 and infinote. :)
fedora-infrastructure-meeting-next is the document.
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
= Introduction =
This shared document is for the next fedora infrastructure meeting.
We will use it over the week before the meeting to gather status and info and
discussion items and so forth, then use it in the irc meeting to transfer
information to the meetbot logs.
= Meeting start stuff =
#startmeeting Infrastructure (2015-11-12)
#chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk pbrobinson
#topic New folks introductions / Apprentice feedback
= Status / information / Trivia / Announcements =
(We put things here we want others on the team to know, but don't need to discuss)
(Please use #info <the thing> - your name)
#topic announcements and information
#info Setup ticket for phx2 site visit in jan: https://fedorahosted.org/fedora-infrastructure/ticket/4948
#info Setup ticket for re-arranging networks: https://fedorahosted.org/fedora-infrastructure/ticket/4949
#info Re-installed buildvm-01 to 09 with Fedora23 - kevin
#info Have done some ansible 2.0 testing and upstream has been fixing issues - kevin
#info Got reproducer for sigul batch signing issues and updated bug - kevin
= Things we should discuss =
We use this section to bring up discussion topics. Things we want to talk about
as a group and come up with some consensus or decision or just brainstorm a
problem or issue. If there are none of these we skip this section.
(Use #topic your discussion topic - your username)
= Learn about some application or setup in infrastructure =
(This section, each week we get 1 person to talk about an application or setup
that we have. Just going over what it is, how to contribute, ideas for improvement,
etc. Whoever would like to do this, just add the info in this section. In the
event we don't find someone to teach about something, we skip this section
and just move on to open floor.)
2015-11-12 - Learn about mdapi - pingou
2015-11-19 - Learn about apprentices - nirik and aikidouke
2015-12-03 - Learn about buildbot - tflink
#topic Learn about: mdapi - pingou
= Meeting end stuff =
#topic Open Floor
I've been following this email list for a couple of months. It's about
time, I think, to take the plunge and join the apprentices group if
possible. So here I go.
For the sake of clarity, I'll use the structure suggested in the first-
1. Name: Juan Jimenez-Anca
2. Time Zone / Country: UTC UK(London)
3. Basic skills and experiences
For the past year and a half I have been developing a small project for
open books. In the meantime, I have learned Linux systems
administration to be able to set up and manage various types of
servers: web, mail, monitoring, database, etc.
In regards to knowledge, I can write code in Python and JS, and basic
scripts in bash. I'm also fairly proficient with ansible and git.
4. Why you're joining
I am an advocate of free culture in general. My background up until a
couple of years ago was mainly as an academic in Humanities subjects.
However, after starting my project on open books I've been learning a
lot about how open source works. So far I've been in the receiving end,
and I would like to contribute too. I use Fedora and CentOS, so joining
the Fedora Projects feels like a logical step forward.
5. What you're looking to do (be specific)
I am aware there is an apprentices day next week. So, ideally, I'd like
to be present that day and get acquainted with areas of possible work.
As far as I know, ansible has been mentioned for the day. I'm quite
happy to start writing playbooks for any task that requires them.
More generally, I would also like to contribute to any monitoring,
deployment, etc. that may be necessary.
6. How much time you can contribute (usually hours per week)
About one morning/afternoon a week
I thought I would send out this reminder as it's bitten us a few times
When you commit something to ansible, you are saying:
"This is the desired state".
This means you should run any affected playbooks and confirm that the
changes have been pushed out and are working as you expect. If you are
unable to do this, please revert back to the last state that actually
reflects whats on the machines you are managing.
At any time ansible could be run with your changes and push them out
with unrelated changes, possibly causing breakage. It then falls to
whoever last ran ansible to fix your previous changes, possibly without
you around, which is unfair and wrong.
If you make some changes and don't have the access to push them out,
please contact someone who does to make them live and confirm they are
working as expected.
If there's some reason you are in the middle of some complex changes
and don't wish them to be pushed yet, please let everyone else who
could be doing ansible runs that that is the case.
Thank you all.
I have started bootstrapping a group of volunteers from the community
who will help us to do manual testing of Fedora cloud images (including
atomic). Right now I have only a limited number of people whom we will
help so that they pick up the required skill set to understand the
process/systems, and be able to help. This level of manual testing will
be above the automatic tests autocloud is doing. This is the same
group of people who will also write (few already started) new tests for
the Cloud SIG.
Because bandwidth is an issue, we will require access to Fedora Infra
Cloud (or something similar), where we can create (of course not the
long running ones) instances or add new images to do the required
Please let me know what should be the next step for this.
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
I'm waiting to see if the last person that worked on this ticket is
still actively involved and trying to do some testing on my own.
However, the CentOS 7 VM I am using has a different version of squid.
I've left a diff of my squid.conf and kojipkgs' squid.conf and notes on
how I set up apache. Would anyone have the bandwidth to look at my
notes on the ticket
https://fedorahosted.org/fedora-infrastructure/ticket/4507 and see if
it looks like I am on the right track or give me some guidance on how I
could recreate the issue?
PS. I remember a month or so ago there was an issue with squid hitting
100% CPU on one of our boxes (sorry I can't remember which.) I just saw
this bug and thought it might be relevant. Not sure if the issue was
ever resolved or not. I didn't see any active tickets and couldn't find
any alerts that looked promising.
You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the
Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.
At the first of every month(or so), I am going to be sending out an
email like this one. I would like feedback on how things are going for
I'd like to ask for everyone to send me a quick reply with the
following data or anything related you can think of that might help us
make the apprentice program more useful.
0. Whats your fedora account system login?
1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?
2. Has it helped you decide any area you wish to focus on or contribute
3. Have you looked at or been able to work on any of the fi-apprentice
4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?
5. Is there any help or communication or ideas you have that would help
you do any of the above?
6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?
7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting?
8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby
9. Did you know that we are having an apprentice work day on November
18th? Will you be able to stop by and talk with us then and get more
Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.
Any folks I do not hear from in the next week will be removed from the
group. (Note that it's easy to be readded when you have time or
whatever and it's nothing at all personal, we just want to keep the
group up to date with active folks).
Thanks, and looking forward to your feedback!