Introduction
by Joerg Stephan
Good morning to the list,
My name is Jörg Stephan, i am an 34 years old system administrator from germany. I basically work on maintaining some hundreds of debian/ubuntu based servers and a handful of centos machines. I would like to participate/contribute to the infrastructure team. Besides my administrator work i am also responsible for IT security questions.
I have some advanced knowledge in topics like basic administration (webservers, databases, fileserver, etc) monitoring with nagios and zabbix and configuration via puppet.
Please find some (maybe out dated) infos at https://fedoraproject.org/wiki/User:Johe
--
Joerg Stephan
10 years, 3 months
Hello World! (intro)
by Elizabeta S⌀resen
Hello infra! My name is Elizabeta and I'd like to contribute!
I'm now a student at RMIT in Melbourne, however for the past 5 years
I've been a sysadmin working in managed hosting and vfx. I'm a python
developer, config management (puppet, ansible) and fairly confident
dba. I'd like to learn more about fedora (Primarily supported debian)
and eventually get into kernel dev.
I look forward to helping out in anyway I can, I can provide about 12
hours a week until March then I'd drop down to 6 as uni starts.
Thanks,
Elizabeta
10 years, 3 months
introducing myself
by Seenu Reddy
hi Fedora,
i am newbie to Linux
i have two years experience in c c++ and driver development in
windows OS.
I have worked on PCI ,USB drivers ,and developed Single Document,
Multiple Document Interface applications for simulating data logger
cards .
I have started working on Linux and currently developing an application
using qt designer.
I am very interested in Operating System designing and development about
which i know just a little.
I want to learn this through Linux .
I can spend minimum 1 hour per day and more than 3 hours on weekends.
i am interested in Fedora because Fedora has vast community to help
starters and i just like it to learn through contributing .
so what are the groups i should join ?
Please suggest me some groups where i can use my existing skills ,so
that i can get familiar with things happening here.
so please consider my request and reply me any suggestions .
Thank you,
--
cnu <seenureddy42(a)gmail.com>
10 years, 4 months
ansible variable fix commit
by Kevin Fenzi
Thanks to janeznemanic, I have a commit ready for the ansible repo that
should replace all the old $foo and ${foo} variables with new style
ansible/jinja2 {{ foo }} style. ;)
Anyone around to +1 it? :)
It's rather large, so it's in /tmp/ansible-variables.patch on lockbox01.
kevin
10 years, 4 months
state of the infra ansible, cron job and roadmap
by Kevin Fenzi
Greetings.
So, over the holiday break I did some massive cleanup on our ansible
repo. I took an initial patch from janeznemanic to fix old syntax and
went from there. I got all the depreciated syntax fixed (there might be
some small amount of stray ones). I also moved accelerate into
global.yml, so it should apply to all playbooks. The needed package
and firewall port should be set in the kickstarts now.
Next I took a simple script to run --check --diff on each host and
group playbook and got it up and running. It takes about an hour to run
against our host/group playbooks when it's run one at a time. We could
just fire them all off but that might swamp lockbox01.
Ideally, what I would like to see from a run of this script is all
hosts/groups reachable and 0 items changed. This is the state we should
strive for. ;)
* The following hosts are unreachable:
209.132.184.158 (see jenkins note below)
209.132.184.209 (see jenkins note below)
arm03-packager01.arm.fedoraproject.org (will fix)
arm03-packager02.arm.fedoraproject.org (will fix)
arm03-qa01.arm.fedoraproject.org (will fix)
buildvm-27.phx2.fedoraproject.org (test buildvm, expected down)
jenkins-cloud
jenkins-slaves (these look to need a bit of tweaking)
lists-dev.cloud.fedoraproject.org (is up, but / is 100% full)
mailman01.stg.phx2.fedoraproject.org
releng01.phx2.fedoraproject.org (is down since we don't have a branched
right now)
* The following hosts have changed > 0:
209.132.184.144
209.132.184.153
209.132.184.157
arm03-qa00.arm.fedoraproject.org
arm03-qa02.arm.fedoraproject.org
arm03-qa03.arm.fedoraproject.org
arm03-releng00.arm.fedoraproject.org
arm03-releng01.arm.fedoraproject.org
arm03-releng02.arm.fedoraproject.org
arm03-releng03.arm.fedoraproject.org
backup03.phx2.fedoraproject.org
beaker01.qa.fedoraproject.org
bkernel01.phx2.fedoraproject.org
bkernel02.phx2.fedoraproject.org
buildvm-01.phx2.fedoraproject.org
buildvmhost-10.phx2.fedoraproject.org
buildvmhost-11.phx2.fedoraproject.org
buildvmhost-12.phx2.fedoraproject.org
bvirthost07.phx2.fedoraproject.org
copr-be-dev.cloud.fedoraproject.org
copr-fe-dev.cloud.fedoraproject.org
db02.stg.phx2.fedoraproject.org
docs-backend01.phx2.fedoraproject.org
fedocal01.phx2.fedoraproject.org
fedocal01.stg.phx2.fedoraproject.org
fedocal02.phx2.fedoraproject.org
gallery01.stg.phx2.fedoraproject.org
kernel01.qa.fedoraproject.org
kernel02.qa.fedoraproject.org
keys01.fedoraproject.org
mailman01.stg.phx2.fedoraproject.org
notifs-backend01.stg.phx2.fedoraproject.org
notifs-web01.stg.phx2.fedoraproject.org
notifs-web02.stg.phx2.fedoraproject.org
nuancier01.phx2.fedoraproject.org
nuancier01.stg.phx2.fedoraproject.org
nuancier02.phx2.fedoraproject.org
nuancier02.stg.phx2.fedoraproject.org
releng02.phx2.fedoraproject.org
taskotron-dev01.qa.fedoraproject.org
virthost15.phx2.fedoraproject.org
I'll work with others to get those all fixed up in the coming weeks.
That said, how do we want to run our non manual ansible jobs?
a) run a --check --diff once a day and yell about unreachable or
changed>0
(I could commit this now)
b) just run them once a day and yell about anything that changes.
(I could commit this now)
c) Trigger them on git commits.
This would take work to figure out what was affected by the commit,
or just fire off a run of everything.
d) setup some file somewhere that can be created by sysadmin group and
a cron job picks it up and runs the next time it runs. This would allow
someone to commit something, schedule a run and give a bit of time for
someone to notice a problem with it before it does.
Thoughts?
As far as roadmap for migration:
I'm going to try and work on splitting out everything that is still on
app* servers to their own ansible instances. Once the app servers are
fully migrated we can tackle proxy*, then virthosts, then various
singletons. Then we can see where we are, and work a final push to get
everything left moved over. ;)
kevin
10 years, 4 months
Plan for tomorrow's Fedora Infrastructure meeting (2014-01-09)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2014-01-09 at 19: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 Upcoming Tasks/Items
https://apps.fedoraproject.org/calendar/list/infrastructure/
#topic 2014 dreaming
Some discussion about what we want to get done in 2014. :)
#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
10 years, 4 months
Fedora koji upgrade -- features and schedule
by Matthew Miller
I'm not sure if this is more appropriate for this list or for RelEng, but I
figure the RelEng folks read this too, so I'd start here.
The newer release of upstream Koji has the feature where images can be
generated with Anaconda rather than appliance-creator (through Oz via
ImageFactory). Since appliance-creator is not really maintained upstream
(excepting Dennis's hacking to keep it working), this is pretty important.
And since it will require the cloud kickstart (and anything else that wants
to use it) to be updated, the longer we have to get the kinks out, the
better.
On top of this, upstream ImageFactory is gaining support for generating
Docker images, and we're getting a lot of push for making these official, or
at least more official than they are now, and generated-in-koji would be a
great start. That code should be in the upstreams (and the Fedora packages)
soon, but isn't yet. Since I assume we don't want to do the upgrade more
times than necessary, this is adds a wrinkle to the timing.
Are there existing plans for upgrading koji? What all is needed to make this
happen? Thanks!
--
Matthew Miller -- Fedora Project -- <mattdm(a)fedoraproject.org>
10 years, 4 months
January 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).
When you reply, please include your fedora account system login.
Additionally, this month, I am CC'ing the infrastructure list. If you
would like to send your feedback there as well everyone can see and
comment on it.
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. What are you most looking forward to in the world of computing for
2014?
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
10 years, 4 months
