fedmsg-atomic-composer in the atomic-composer ansible role
by Randy Barlow
Heyo!
While deploying bodhi 2.3.0-0.1.beta to stg tonight, my playbook failed
because the fedmsg-atomic-composer rpm was renamed to python2-fedmsg-
atomic-composer because long names let you type more on that fancy
mechanical keyboard of yours.
I'm fixing the usage of the old name in roles/bodhi2, but git grep
informed me that roles/atomic-composer also references the old package
name. I went ahead and changed it there under the assumption that this
makes sense, but I'm not so familiar with the various roles so I wanted
to send a heads up that I did this in case I shouldn't have.
7 years, 6 months
Plan for tomorrow's Fedora Infrastructure meeting - 2016-10-20
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2016-10-20 at 18:00 UTC in #fedora-meeting on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
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.
kevin
--
= 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 (2016-10-20)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson
#topic New folks introductions
= 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 starting to migrate dbs in stg to new pgbdr pair of servers - kevin
#info closed/moved/upstreamed a bunch of old tickets - kevin
#info askbot load issues, due to a session db table - kevin/patrick
#info sign-vault03 re-installed, some more sigul config to come - kevin/partick
#info kevin out next week 2016-10-26 to 2016-10-30 - kevin
#info jenkins outage friday - kevin
#info
= 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)
#topic change fedmsg setup to handle more hosts - patrick
#topic
= Apprentice office hours =
#topic Apprentice Open office hours
Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.
= 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.)
#topic Learn about:
= Meeting end stuff =
#topic Open Floor
#endmeeting
7 years, 6 months
[PATCH] improve fedmsg rules for g11n
by Parag Nemade
Hi,
The pagure ticket update fedmsg notifications were not coming for i18n
and g11n projects. I think attached patch will fix this. Please review this
patch and if it looks good, merge it, not urgent maybe after freeze period
gets completed.
Regards,
Parag Nemade.
7 years, 6 months
[release] pagure: 2.7
by Pierre-Yves Chibon
Good Morning Everyone,
I just cut a new release of pagure: 2.7
It comes with quite a few changes, here is the changelog:
* Tue Oct 11 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.7-1
- Update to 2.7
- Clean imports (Vivek Anand)
- Fix NoneType error when pagure-ci form is inactively updated first time
(Farhaan Bukhsh)
- Fix minor typos in configuration documentation (Jeremy Cline)
- Use context managers to ensure files are closed (Jeremy Cline)
- Adjust update_tickets_from_git to add milestones for issues as well (Vivek
Anand)
- Update milestone description in Settings (Lubomír Sedlář)
- Add checks for the validity of the ssh keys provided (Patrick Uiterwijk)
- Remove hardcoded hostnames in unit tests (Jeremy Cline)
- Skip clamd-dependent tests when pyclamd isn't installed (Patrick Uiterwijk)
- Fix interacting with branch containing a dot in their name (new PR button,
delete branch button)
- Ensure only project admins can create reports
- Do not warn admins when a build in jenkins did not correspond to a
pull-request
- Fix the progress bar on the page listing the issues (d3prof3t)
- Do not call the API when viewing a diff or a PR if issues or PRs are disabled
- Port pagure to flask 0.13+
- Fix displaying the reason when a PR cannot be merged
- Allow projects to turn on/off fedmsg notifications
- Fix the web-hook service so when a project is updated the service is as well
- Add the possibility to specify a status to close ticket (closed as upstream,
works for me, invalid...)
- Let all the optional SelectFields in forms return None when they should
- Make each tests in the test suite run in its own temporary directory (Jeremy
Cline)
- Use long dash in footer instead of two short ones (Lubomír Sedlář)
- Add a welcome screen to new comers (does not work with local auth)
- Ensure user are not logged in if we couldn't properly set them up in pagure
- Add the possibility to search through issues (AnjaliPardeshi)
- Add a default hook to all new projects, this hook re-set the merge status of
all the open PR upon push to the main branch of the repo
- Add support for setting custom fields for issues per projects
The last item here should interest some people, I still need to write some
documentation around it but the basic doc is in the PR:
https://pagure.io/pagure/pull-request/1395
This is currently happily running in stg: https://stg.pagure.io feel free to
poke at it there and report any issue you may have.
If all goes well, I might cut a 2.7.1 tomorrow (found a few quick bugs while
deploying 2.7) and push to prod once freeze is over.
Happy hacking,
Pierre
7 years, 6 months
[release] pagure: 2.7.2
by Pierre-Yves Chibon
Good Morning Everyone,
I just cut a new release of pagure: 2.7.2.
Here is the corresponding changelog:
* Thu Oct 13 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.7.2-1
- Update to 2.7.2
- Do not show the custom field if the project has none
- Improve the documentation around SEND_EMAIL (Jeremy Cline)
This is currently running in stg, I'm going to push it to prod as well which
will lead to a little outage.
Happy hacking,
Pierre
7 years, 6 months
Plan for tomorrow's Fedora Infrastructure meeting - 2016-10-13
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2016-10-13 at 18:00 UTC in #fedora-meeting on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
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.
kevin
--
= 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 (2016-10-13)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson
#topic New folks introductions
= 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 fedora-flask-admin and mirrormanager2 now in Fedora/EPEL - patrick
#info Fedora 25 Beta released! - everyone
#info modernpaste plans sorted out - relrod
#info database replication setup with koji.stg, please test - kevin
#info
= 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)
#topic
= Apprentice office hours =
#topic Apprentice Open office hours
Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.
= 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.)
#topic Learn about:
= Meeting end stuff =
#topic Open Floor
#endmeeting
7 years, 6 months
[release] pagure: 2.7.1
by Pierre-Yves Chibon
Good Morning Everyone,
I just cut a new pagure release: 2.7.1
Here is the changelog:
* Wed Oct 12 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.7.1-1
- Update to 2.7.1
- Bug fix to the custom fields feature
It is currently running in stg, I am planning on updating prod tomorrow when the
US are asleep as it will lead to a few minutes of outage (just the time to
upgrade the DB scheme).
Happy hacking,
Pierre
7 years, 6 months
Fedora 25 Beta freeze now in effect
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 25
Beta release. This is a pre-release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 25 Beta 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 2016-10-11. (or later if
Beta 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.
Thanks,
kevin
7 years, 6 months
koji db replication in staging... working!
by Kevin Fenzi
Greetings.
After a bunch of playing around, I managed to get bidirectional
database replication working for koji.stg.fedoraproject.org.
Basic outline:
db-koji01.stg and db-koji02.stg both have postgresql-9.4-bdr installed.
init a koji db on both.
create a koji user and set password on both.
restore prod db dump on one of them.
enable replication of the koji db.
wait for a while for them to sync up
(It took about 4.5 hours to sync ~170GB of database)
run the staging sql script on either node.
I then added keepalived to keep a 'application ip' between the two of
them (favoring 01).
Then I pointed koji01.stg at the application ip
(well, I really just removed it's /etc/hosts entry for db-koji)
I tested switching the ip back and forth.
I tested rebooting one node or the other.
I tested disabling keepalived on one and rebooting (so the other one
became and stayed primary).
Everything seemed to work. ;)
So, next steps:
1. Pound on koji.stg and see if anything breaks. ;) I tried to enable
koschei, but I think we have it currently set too not do staging
builds. If we could enable it that might be good. If anyone notices
anything broken on koji.stg, please let me know. If you can think of
some common cases we should test, please let me know that too. ;)
2. I am going to look at setting up another pair and get this all in
ansible and then see about migrating other staging services. I'm
hopeful that if koji works all our less database heavy apps will work
ok too.
3. If everything keeps looking good, move to production.
Longer term what does this mean?
It means we can do updates/reboot cycles with pretty close to no
downtime. We may have to be clever about the openvpn hub, but if we can
reboot database servers as desired we may be able to avoid maint
windows entirely, or at least reduce them a great deal.
kevin
7 years, 6 months
