Introduction
by Alexander Rudolf
Hi folks,
I would like to introduce myself too:
First of all I would like to give a "thanks a lot" and "wow - great
job!!!" to all who have made fedora become reality!!! It is fun to work
with it.
My name is Alexander Rudolf. I live in Germany. I am an IT
infrastructure consultant and systems engineer working for a company in
Dresden, Saxony.
"Growed up" (I am 39) with MS-DOS an Novell NetWare in the early 90s
when I started my work live I now have a lot experience with
heterogeneous networks, network equipment and security, systems
management, high availability solutions and those things. Made my MCSA
for Windows Server and am LPI-C certified since 2006.
My most recent experiences are in Linux system administration, security,
virtualization and most of all - Nagios. I supported a number of related
projects for some customers and wrote a couple of Nagios plugins. Most
of them in bash, but also in VBS and PowerShell for the windows driven
landscape.
I would now like to actively join the fedora infrastructure team and do
my very best to provide support. Please help me to understand how I can
contribute best!
Best regards,
Alex
11 years, 1 month
ansible musings...
by Kevin Fenzi
Greetings.
The upstream ansible folks have been discussing a 'best practices' doc
at:
https://github.com/ansible/ansible/blob/devel/docsite/rst/bestpractices.rst
and I have been pondering how we want to setup things on our ansible
instance before we add a bunch more things to it.
So, some outstanding questions for comment/discussion:
a) I think I like the idea of splitting out per role trees for things.
But we need to decide what level of granularity a 'role' is.
For example, mirrormanager in puppet is a single module.
However, it's really:
mirrormanager proxy setup files
mirrormanager mirrorlist server web app
mirrormanager web app (the admin part)
mirrormanager backend scripts (crawler, creating lists, etc)
So, for our purposes should we have mirrormanager all in the same
'role' tree? or should we split it out by functionality?
Many roles won't have this issue, as they will be simpler.
b) What would be the workflow for staging with ansible?
Ie, I want to make some config changes only in staging and iron them
out and then merge them back to production when ready. Do we copy the
role and modify? Do we require only changing vars and seperate files?
Will be thinking on it more, but input welcome.
kevin
11 years, 1 month
GSoC @ Infra
by Pierre-Yves Chibon
Hi all,
I brought up the subject at the meeting but we should discuss this here
as well.
Do we want to be involved in the GSoC?
Do we have wishes/ideas/desires?
The main page for Fedora seems to be at [1] and there are already some
ideas presented at [2].
Among these ideas we find again gitlab for Fedora Hosted. There is also
something for the spins (might be worth checking this wrt formulas).
I'm sure we can come up with ideas from our project, fedmsg, badges (I
can come up with some myself) but then there is of course the question
of supervision.
Note that you can also team up for the supervision, which can make
things easier.
Apparently we still have some time but we shouldn't wait too long if we
are interested.
Food for thoughts :)
Pierre
[1] https://fedoraproject.org/wiki/GSOC_2013
[2] https://fedoraproject.org/wiki/Summer_coding_ideas_for_2013
11 years, 1 month
Plan for tomorrow's Fedora Infrastructure meeting (2013-02-28)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2013-02-28 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 Private Cloud status update / discussion
#topic Upcoming Tasks/Items
#info 2013-02-28 end of 4th quarter
#info 2013-03-01 nag fi-apprentices
#info 2013-03-07 remove inactive apprentices.
#info 2013-03-19 to 2013-03-26 - koji update
#info 2013-03-29 - spring holiday.
#info 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze
#info 2013-04-16 F19 alpha release
#info 2013-05-07 to 2013-05-21 BETA infrastructure freeze
#info 2013-05-21 F19 beta release
#info 2013-05-31 end of 1st quarter
#info 2013-06-11 to 2013-06-25 FINAL infrastructure freeze.
#info 2013-06-25 F19 FINAL release
#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
11 years, 1 month
Joining the sysadmin-build group
by Daniel Hamacher
Greetings,
I would like to joint the sysadmin-build group and I am wondering what I
have to do for an invitation. Tahnks
Best,
Daniel
11 years, 1 month
Certificate Generation problem
by Christopher Meng
Hi,
after generating the certificate,I found the browser just downloaded a
dogencert.htm.
What's up?
Thanks.
*Yours sincerely,*
*Christopher Meng*
Got problems with Windows? - ReBoot
Got problems with Linux? - Be Root
Ambassador/Contributor of Fedora Project and many others.
http://cicku.me
11 years, 1 month
Meeting Agenda: Introduction Daniel Hamacher
by Daniel Hamacher
Greetings,
My name is Daniel and I am currently a second year University student in
a Computing and Information systems program. What I can offer is basic
scripting in Bourne, Bash, and Python. I have more advanced skills in
Java programming since this is the main language is used in my
University program. I spend additional time with reading Linux related
literature such as "The Linux Administration Handbook" and the "Linux
Programming Interface". The latter inspired me learn the C language so I
can apply the concepts I have learned and experiment with kernel system
calls. I also work part time as Technical Support Representative in a
Cable/Internet Company.
My goal for the next 3 years is to become a Software Developer with good
coding practice and a solid foundation in algorithmic computation and
design patterns. I have a keen interest in the kernel structure and the
lower level aspect of hard- and software communication. I want to
contribute to the team that provided me with an operation system that
gave me possibilities to be as creative as I wanted to be - and that is
for free. I want to become a valuable member of this community and I
want to be known for my commitment and skill. I will join the fedora
meetings on a regular basis to get the big picture of what is going on
right know. I cannot always attend the meeting since I work and
day/night shift rotations, but I'll do my best.
I am looking forward to work with the team.
Best Regards,
Daniel Hamacher
IRC brundlfly
11 years, 1 month
Fedocal to prod?
by Pierre-Yves Chibon
Hi all,
I am getting some pressure to move fedocal to production (which is
pretty nice).
So just to be sure the next steps should be:
- roll out the 0.1.0 release
- package it
- it now has a setup.py so I hope that it'll be pretty simple
- request for hosting/hw ?
- create the adequate puppet module
- which url? admin.fedoraproject.org/calendar ?
Do I miss anything?
Also, what's the traditional time-line to move from stg to prod?
Thanks,
Pierre
11 years, 1 month
python-fedora and pkgdb repository changes -- reclone i necessary
by Toshio Kuratomi
Today we did some housecleaning on the python-fedora and packagedb github
repositories. Depending on what you were doing, you may want/need to
reclone the repository.
or packagedb, we renamed the old devel branch to devel-old. I don't
anticipate that anyone was currently using this. People should be using
develop instead. This rename should hopeully keep people rom being conused
as to where they should be making commits.
For python-fedora, we renamed the devel branch to develop. This is because
git flow's deault branch scheme is to use develop as the branch where active
work is being performed. Using devel instead of develop was just confusing
people and was a difference from the defaults when running git flow init.
I you have a python-fedora checkout, the easiest way to get setup to use the
new develop branch is to reclone the repository from github. It is possible
to change the branches you have to push, pull, and use git low to the
develop branch instead of devel but it's a multistep process o renaming
branches locally, changing your remote, and manually editing the .git/conig
to set git low to use the right branches. Much easier to just reclone in
this case.
-Toshio
11 years, 1 month
