mirroring for alternative content
by Colin Walters
Hi,
We have several forms of non-Koji internal builds:
1) COPR (the most visible)
2) http://alt.fedoraproject.org/pub/alt/rawhide-kernel-nodebug/ (this
could be a COPR)
3) rpm-ostree: http://rpm-ostree.cloud.fedoraproject.org/#/
Now, I recently was allocated a new atomic01.qa.fedoraproject.org server
dedicated to rpm-ostree composes, and I'm happy to announce I now have
it composing trees:
fedora-atomic/rawhide/x86_64/server/docker-host =>
175510ab77ef39ec6000db2745c70444d55957e38c5ff28f890237e1f012ea5e
fedora-atomic/rawhide/x86_64/workstation/gnome/core =>
b6f3f3b53ef957c71e8d8bdc36c35519888d4177bf6a582ba37e33416ff84216
But it's on the QA network, and so I can't just serve the content
directly from it. Nor would I want to have the compose server doing
double duty as a static webserver anyways.
I could just rsync this content to the current
rpm-ostree.cloud.fedoraproject.org, but there are a few issues with
that:
1) It's a one off instance in the fedora cloud with no backup/monitoring
2) No redundancy
3) No tuning for static webserving
4) Most critically, no TLS
COPR only relatively recently gained TLS, which is fundamentally
necessary for retrieving arbitrary executable code that runs as root.
But COPR also (from what I understand from <puiterwijk>) is just one
machine.
What do you think about investing in having e.g.
altcdn.fedoraproject.org be a load-balanced static webserver farm
protected by TLS that could be written to by a trusted subset of
non-Koji build/compose tooling?
"altcdn" is the first thing that came to mind offhand for a name, feel
free to pick others =)
We'd need to determine the writing process; could be rsync-over-ssh
access to specific subdirectories gated by ssh key? Something else?
9 years, 8 months
Meeting Agenda Item: Introduction John Dulaney
by John Dulaney
Hello!
My name is John Dulaney, and I am a long time contributor. I have
been kicking the idea of joining the infrastructure team for quite
some time now.
I can bring the following to the table:
Red Hat Certified Engineer
Many years of contributing to Fedora
Experience supporting Red Hat Enterprise Linux for Red Hat
Python
I look forward to helping out!
John.
IRC: handsome_pirate
9 years, 8 months
Review for new rbac_playbook
by Tim Flink
I've been working to rewrite and extend the script that we've been
using to control playbook execution for folks who are not in
sysadmin-main.
https://bitbucket.org/tflink/rbac-ansible
I've been testing the script but before we actually start using it on
lockbox01, I'd appreciate a review of the code to make sure I didn't
miss any security holes.
Injection attacks shouldn't be an issue due to usage of os.execv - all
injection attempts are grouped as a single argument and will not be
broken up.
Tim
9 years, 8 months
Plan for tomorrow's Fedora Infrastructure meeting (2014-06-25)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2014-06-25 at 18:00 UTC in #fedora-meeting on the freenode network.
Suggested topics:
#topic New folks introductions and Apprentice tasks.
If any new folks want to give a quick one line bio or any apprentices
would like to ask general questions, they can do so in this part of the
meeting. Don't be shy!
#topic Applications status / discussion
Check in on status of our applications: pkgdb, fas, bodhi, koji,
community, voting, tagger, packager, dpsearch, etc.
If there's new releases, bugs we need to work around or things to note.
#topic Sysadmin status / discussion
Here we talk about sysadmin related happenings from the previous week,
or things that are upcoming.
#topic nagios/alerts recap
Here we go over the last weeks alerts and see if we can find ways to
make it so they don't happen again.
#topic Upcoming Tasks/Items
https://apps.fedoraproject.org/calendar/list/infrastructure/
#topic Open Floor
Submit your agenda items, as tickets in the trac instance and send a
note replying to this thread.
More info here:
https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings
Thanks
kevin
9 years, 8 months
June status update for Fedora Infrastructure Apprentices
by Kevin Fenzi
Greetings.
You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the
infrastructure list).
Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.
https://fedoraproject.org/wiki/Infrastructure_Apprentice
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
you.
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
to more?
3. Have you looked at or been able to work on any of the fi-apprentice
'easyfix' tickets?
https://fedorahosted.org/fedora-infrastructure/report/14
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. Whats your most used command in your bash history?
(run:
cut -d\ -f 1 ~/.bash_history | sort | uniq -c | sort -rn | head -n 1 | sed 's/.*/ &/g'
to see)
(if using zsh:
history 1| awk '{print $2}' | sort | uniq -c | sort -rn | head -n1
)
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!
kevin
9 years, 8 months
introduction
by Gonçalo Gomes
Hello Fedora Infrastructure!
I'm a Linux engineer with a keen interest in Linux, OSS and Fedora in
general. I want to contribute to Fedora as an outlet to get involved in the
open source. I have attempted in the past to contribute to Fedora as a
bugzapper, but due to other commitments taking place around the same time,
this never really materialised.
I am happy to contribute to fedora's infrastructure. The subjects that seem
to get my attention the most are: Distributed Systems, Automation,
Virtualization. I normally write most code in Python, Shell and C..
Name: Goncalo Gomes
Time Zone / Country: UTC / IRELAND
IRC: goncalo
Interests: Distributed systems & Automation, C, Kernel and Program
Analysis. Python.
Contribution hours per week: upwards of 5hours, hard to estimate how much
time I will be able to spend on Fedora at this stage.
Skills: System Engineer/DevOps, Software Development in Python and C
Having said that, I am looking for a sponsor/mentor within the group. Thank
you.
Goncalo
N.B: I templated this email using Selva's recent introduction email. I hope
it's not a big issue! And, Welcome Selva! :-)
9 years, 8 months
Meeting Agenda Item: Introduction Selvakumar (Selva)
by Selvakumar M
Hello Everyone,
I am looking to join Fedora project infrastructure community. I had been
working on linux some years ago & tried to build email service using qmail
system for one of my friend organization, which was successful at the pilot
phase. It was a wonderful experience with limited Linux skill. Over the
period, i groom myself in Linux specifically on system administration and
scripting (automation). Now i would like to contribute for fedora project.
Please find below my details.
Name: Selvakumar M (Selva)
Time Zone / Country: UTC +05:30 / INDIA
IRC Handle: selvakumarm
Interest: Design & Administer Linux Infrastructure, Automation using Perl,
Linux Satellite & OpenSource Deployment (E-mail, Web, Nagios & ERP Services)
Contribution hours per week: Ranging from 6 - 10 hrs
Skills: System Administrator & Automation (PERL)
Having said, I am looking for a sponsor/mentor within the group. Thank You
!!
Regards,
Selva
9 years, 9 months
Reliability of Fedora infrastructure to download cloud images
by Kashyap Chamarthy
[I'm not subscribed to this list, please keep me in CC.]
Heya,
A little while ago, we (Matthew Miller, myself, Attila Fazekas (upstream
OpenStack developer) had an IRC discussion (on #openstack-qa, Freenode)
with OpenStack upstream CI infrastructure folks about their concerns for
continuing to have Fedora as a default to run as CI voting guest (Nova
instance). They (mostly Sean Dague - a major upstream OpenStack
contributor who voiced these) outlined a few issues:
1. It's not possible to download from the fedora infrastructure
reliably - 10% failure rate from their cloud providers (HP and
RAX).
- About this point, when mattdm inquired - "is the failure in
hitting the fedora mirrors or fedora core infrastructure?",
their response - "I don't fully know, I think going through the
url we are using we get bounced to mirrors".
2. There are possibly issues with the normal upstream fedora image
that could be fixed with custom respin.
- NOTE: I'm doubtful of this idea, as existing Fedora cloud images
itself are not really extensively tested. I'd think focusing on
_official_ cloud images and having a solid set of tests so that
it can be consumed by cloud projects (OpenStack, etc).
- Having a custom respin means that we're off the main path for
testing of the image -- which again needs _some_ level of
assurance that it can be used in a higher-level cloud project's
CI infr- which again needs _some_ level of assurance that it can
be used in a higher-level cloud project's CI infra.
3. Another important point OpenStack infra folks emphasized is - these
images will get 4000 test runs a week on them
Any suggestions to allay these are welcome.
--
/kashyap
9 years, 9 months