Proposal: Ansible Spring Cleaning: Update/upgrade scripts
by Stephen John Smoogen
Clement brought up that spring cleaning of our ansible playbooks would
be a good idea. This is painfully obvious during our previous
update/reboot cycles where we have had services not updated or
restarted correctly so that systems did not come up well when we
rebooted.
I have opened https://pagure.io/fedora-infrastructure/issue/7695 which
is the tracking ticket for this problem. I am proposing that we do
major updates something like the following in the future. We can tweak
as we find better ways to do them in clusters later.
If you maintain a service, take that playbook and add comments for the
following:
a. Who is the current maintainer
b. Date when that was last updated
c. Who tested the upgrade and when
d. General comments to explain what things are doing.
If the playbook should be retired, removed, killed, etc please do so.
My goal will be to make our update schedules something like this:
Day 1:
a. Run update playbooks on staging instances.
b. Fix any problems shown by those.
c. Run general update vhost_update on staging instances
d. Reboot staging instances.
e. Fix problems found from this.
Day 2:
a. Access if day 1 was a complete failure and stop upgrade cycle
b. Run update playbooks on low priority systems
c. Fix any problems shown by those.
d. Run general update vhost_update on staging instances
e. Reboot staging instances.
f. Fix problems found from this.
Day 3:
a. Access if day 2 was a complete failure and stop upgrade cycle
b. Run update playbooks on high priority systems
c. Fix any problems shown by those.
d. Run general update vhost_update on staging instances
e. Reboot staging instances.
f. Fix problems found from this.
This should cut down the extra long hours and extended outages we have
needed to do in the last couple of reboot cycles.
--
Stephen J Smoogen.
5 years
Download Metrics
by Jay Greguske
Hi,
I'm looking for download rates for specific bits of RPM content, is this
the right forum to ask, or is there another group/name to direct this?
Thanks,
- Jay
5 years
2019-04-04 Meeting Agenda
by Stephen John Smoogen
The infrastructure team will be having its weekly meeting tomorrow,
2019-04-04 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a gobby document at
https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructu...
which can be edited for the agenda (see: https://fedoraproject.org/wiki/Gobby )
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 =
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 (2019-04-04)
#meetingname infrastructure
#topic aloha
#chair nirik pingou puiterwijk relrod smooge tflink cverna mizdebsk
mkonecny abompard bowlofeggs
= Let new people say hello =
#topic New folks introductions
#info This is a place where people who are interested in Fedora
Infrastructure can introduce themselves
#info Getting Started Guide:
https://fedoraproject.org/wiki/Infrastructure/GettingStarted
= 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 Beta Freeze Is Finished.
#info Final Freeze Starts on 2019-04-16
= 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 /suor 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 Oncall
#info smooge is on call from 2019-04-04 -> 2019-04-11
#info ????? is on call from 2019-04-11 -> 2019-04-18
#info ????? is on call from 2019-04-18 -> 2019-04-25
#info Summary of last week: (from relrod )
#topic Monitoring discussion
#info https://nagios.fedoraproject.org/nagios
#info Go over existing out items and fix
#topic Tickets discussion
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
Go thru each ticket one by one
#topic Priorities for next week?
#info please put tickets needing to be focused on here
=====
Put all topics for discussion under here
=====
= Apprentice office hours =
#topic Apprentice Open office minutes
#info A time where apprentices may ask for help or look at problems.
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 i/nfo 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.)
#info
= Meeting end stuff =
#topic Open Floor
#endmeeting
--
Stephen J Smoogen.
5 years
Fedora 30 Beta freeze now in efect
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 30
Beta release. This is a pre release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 30 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
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2019-03-26 (or later if
release 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
5 years
Pavel Raiskup is a new member of Copr team
by Miroslav Suchý
Hi,
it is my pleasure to announce that Pavel Raiskup (praiskup) joined the Copr team. Pavel has been contributing to Copr
for long time in his free time. He has been maintaining Red Hat internal Copr instance for long time. Now, he is joining
Copr team as his full time job. Pavel replaced Michal Novotny (clime) who left Red Hat and as result you may see Clime
less on IRC during working hours.
Welcome Pavel.
Miroslav
5 years
[PATCH] distgit/pagure: Increase the cross-project ACLs
by Pierre-Yves Chibon
This just makes pagure accept to generate project-less API tokens
with these two ACLs.
Signed-off-by: Pierre-Yves Chibon <pingou(a)pingoured.fr>
---
roles/distgit/pagure/templates/pagure.cfg | 2 --
1 file changed, 2 deletions(-)
diff --git a/roles/distgit/pagure/templates/pagure.cfg b/roles/distgit/pagure/templates/pagure.cfg
index a66b3278b..385b80464 100644
--- a/roles/distgit/pagure/templates/pagure.cfg
+++ b/roles/distgit/pagure/templates/pagure.cfg
@@ -273,10 +273,8 @@ USER_ACLS = [
CROSS_PROJECT_ACLS = [
'fork_project',
'modify_project',
-{% if env == 'staging' %}
'pull_request_create',
'pull_request_comment',
-{% endif %}
]
ADMIN_API_ACLS = [
--
2.20.1
5 years
FBR: Manually unlock FEDORA-CONTAINER-2019-3e42a55b54
by Randy Barlow
FEDORA-CONTAINER-2019-3e42a55b54[0] references a container that has
been deleted from the candidate registry. As a result, the compose has
failed. Since the update is locked, it cannot be edited to replace it
with a build that exists. To fix this, I propose to unlock the update
like this:
$ sudo -u apache bodhi-shell
2019-04-02 15:24:43,617 INFO [bodhi.server][MainThread] Bodhi ready and at your service!
Python 3.7.2 (default, Mar 21 2019, 10:09:12)
[GCC 8.3.1 20190223 (Red Hat 8.3.1-2)] on linux
Type "help" for more information.
Environment:
app The WSGI application.
registry Active Pyramid registry.
request Active request object.
root Root of the default resource tree.
root_factory Default root factory used to create `root`.
Custom Variables:
m bodhi.server.models
s bodhi.server.Session
>>> u = m.Update.query.filter_by(alias='FEDORA-CONTAINER-2019-3e42a55b54').one()
>>> u.locked = False
>>> s().commit()
After this, I will use the Bodhi web UI to swap the build for fedora-
toolbox:28-5.
[0] https://bodhi.fedoraproject.org/updates/FEDORA-CONTAINER-2019-3e42a55b54
5 years
FBR: Unfreeze RelEng to push updates
by Mohan Boddu
Hello,
I dont know if this FBR is needed or not, but now that we have a GOLD
compose for F30 Beta and all the requested f30 builds pushed stable and I
cloned f30-Beta tag from f30, now we can start pushing updates to F30
stable as well along with the others.
+1's please
diff --git a/vars/all/RelEngFrozen.yaml b/vars/all/RelEngFrozen.yaml
index bd7553f..72af779 100644
--- a/vars/all/RelEngFrozen.yaml
+++ b/vars/all/RelEngFrozen.yaml
@@ -1 +1 @@
-RelEngFrozen: True
+RelEngFrozen: False
Thanks.
5 years
