Per request from pjones, he would like us to add fwupdate to the
secure-boot channel in koji.
The following patch does this. Would require restart of the hub, but
shouldn't be any downtime.
diff --git a/roles/koji_hub/templates/hub.conf.j2 b/roles/koji_hub/templates/hub.conf.j2
index abe650c..6758196 100644
@@ -116,6 +116,7 @@ channel =
source */fedora-release* && has_perm secure-boot :: use secure-boot
source */fedora-repos* && has_perm secure-boot :: use secure-boot
source */pesign* && has_perm secure-boot :: use secure-boot
+ source */fwupdate* && has_perm secure-boot :: use secure-boot
# we have some arm builders that have ssd's in them, eclipse is 7 hours faster building on them so lets
# make sure that we always build eclipse on them.
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. when was the last plane trip you took?
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!
I'm Tiago (FAS: tiagovieira, IRC: tmoreira). I've been around Fedora
for few years - I'm a Fedora advocate in the UK (UK ambassador) and I
am a QE engineer at Red Hat.
I have great interest in systems engineering - I've been developing
tools to assist automations, configuration management and
troubleshooting. In the last few years I've been developing my skills
in the security area - I've got a PG diploma in systems and software
security at Univ. of Oxford (UK). Fedora has always been my favourite
dist, and I want contribute back.
As I've been working with troubleshooting, tools development and
configuration management, this is the things I can learn and do within my
comfort zone. I am willing to learn more about the infrastructure
security and, and hopefully focus in this area as I learn more about how
this is done in this group. I would be grateful if I can get an sponsor.
The languages I've worked in the past are C and Java, and I've been
working with Python in the past 4 years.
Apart from the academic diplomas, I've got RHCSA and RHCE certification
(and I'm currently working on the expertise certifications for a
Datacenter RHCA certification).
You can also check my about page at: http://tvieira.com/about/ with few
I'm looking forward to working with you.
We have a chicken and egg problem, the tests require mirrormanager to point at
the right content, and we do not want to sync the content unless we are sure
it is okay for users and will work as expected. So the thought I was was to
setup in the qa network a mirrormanager instance that will be able to point
the tests at the just built composes and content. it would like need its own
dns view so that the expected urls work in the expected ways, but point the
the QA test specific instances.
I wanted to get a conversation started on what it would take to implement
Fedora 24 alpha is running into some bugs because the updates-testing
repo does not have any weak deps in it's repodata. This is because
bodhi-backend01 is a rhel7 instance and it's rpm is too old to have
So, I have created a bodhi-backend03 instance thats Fedora 24 and would
like to try pushing the fedora-24-updates-testing updates (to start
with) from there to see if it fixes the issue.
The attached patch should fix the bodhi roles to call 'package' instead
of yum module (so they work on either rhel7 or fedora24) and add in a
bodhi2 f24 repo to install from.
The infrastructure team will be having it's weekly meeting tomorrow,
2016-08-11 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.
= 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-08-11)
#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 flock 2016 is over. Lots of blogs and soon videos to recap - everyone
#info Fedora 25 Alpha Freeze has started - kevin
#info nagios is all green for freeze - kevin/smooge/patrick
#info Aug apprentice email went out (a bit late), reply by friday - kevin
#info virthost-comm02 has been reinstalled with rhel7 - kevin
#info rawhide/branched composers are now Fedora 24 - 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)
#topic flock workshop followup - kevin
= 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