Introduction of Ioannis Aslanidis
by Ioannis Aslanidis
Hello,
My name is Ioannis Aslanidis. I am 27 years old and I was born in
Drama, Greece. I grew up in Spain and I currently live in the city of
Barcelona. My time zone is CET(UTC+1)/CEST(UTC+2).
I normally have free time most of the workdays nights and some
weekends and will be able to dedicate a few hours every week.
About my background, I have been a Gentoo packager, developer and
global forums moderator since 2005 and I have also been part of
different projects, besides attenting some years to FOSDEM to support
the booth.
I have finished a degree in computer engineering and a master in
computer security.
Professionally, I am the System and Network Administration Team Leader
in Fluendo/Flumotion since 2008, administrating almost 500 RHEL5
machines betweet 2-3 people. I have pretty good background in
monitoring (nagios 3), setting up streaming clusters (flumotion),
working with bind and dhcpd, setting up machine setups using puppet,
working in xen/kvm virtual environments and I have very good skills
scripting in bash and average with python. Besides, I am pretty
skilled in C/C++ and Java. I have also had the usual chance to write
some spec files for custom packages.
I have also developed a small python application called `pylsyncd`
that stands for `python live syncing daemon`, that uses pynotify to
detect changes in filesystems and replicate using rsync wrappers the
changes in parallel among several servers.
I am willing to join in to learn even more about administering Fedora
and RHEL-based systems, learn new things from other people and share
my knowledge with others as well. This can be very interesting.
Among my motivations, here's a small list:
- scripting
- monitoring
- security
- building systems for multi-target architectures and platforms
- automation and rapid deployment
I hope to be a good addition to your team, do cool stuff and have some real fun!
Best regards.
--
Ioannis Aslanidis
13 years, 4 months
Trac-0.12.1 upgrade for Fedora Hosted
by Jesse Keating
I've been working to get trac-0.12.1 built in EPEL6 as well as the
plugins so that we could potentially upgrade our fedorahosted setup.
http://publictest03.fedoraproject.org/ is up and running with a few
projects from fedorahosted copied over with their source control.
Covered is hg, bzr, git, and svn. I don't have authentication hooked up
yet so it is hard/impossible to test the ticket template plugin and
other related ones.
My testing of trac-0.12.1 is mostly complete, would somebody like to
take on more formal testing of upgrading fedorahosted?
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
13 years, 4 months
Sponsor wanted.
by Mailing Lists
I've been lurking on the mailing list, and in IRC the past month or so, and
would like to actually dive in at this point, and would like to be paired
with a sponsor to work with and learn the more specific ropes to our
infrastructure.
I'm a well rounded sysadmin using fedora in a cloud based production
environment and would like to start by looking at our trac system, and
tickets. Let me know if you can use me better any where else.
Thanks,
-Rob Felsburg
13 years, 4 months
Transifex update - intltool requirement (was: Need a Sysadmin Greeter)
by Domingo Becker
2010/12/9 Kevin Fenzi <kevin(a)scrye.com>:
> On Wed, 8 Dec 2010 18:42:02 -0300
> Domingo Becker <domingobecker(a)gmail.com> wrote:
>
>> Yes, you're right, it's sysadmin-web.
>> I'm new in fedora-admin and I'm working on ticket 2389, about
>> Transifex update.
>>
>> I have no problem to take care of Transifex once I get it updated.
>
> Cool. There are several other tickets related to it...
>
>> I'm currently stuck with the transifex package requirement of intltool
>> 0.37.1 or above.
>> CentOS 5.5 base repo has intltool 0.35.0 so I guess it would be faster
>> for Fedora to push an update to Fedora EPEL 5 updates-testing repo.
>
> Not possible I'm afraid.
>
> EPEL never ships anything thats part of the base OS.
>
Oops
>> I asked Matthias Lasen (mclasen), the intltool package maintainer,
>> about the possibility to push an update to Fedora EPEL 5. I'm still
>> waiting for an answer.
>
> He's likely not going to be able to help.
> You would need to get the RHEL maintainer (whoever that is) to push
> such an update. I suspect they would have very strong resistance to
> doing so in a stable release. ;(
>
I tested in CentOS 5.5 with a package for F10.
But I did that by hand.
Doing that would be like cheating!
And it may be not acceptable by some internal policy.
I thought of the install to be as easy as doing a
yum install --enablerepo=epel-testing transifex
I have all packages in place now, except intltool. :-(
Who maintains intltool in RHEL5?
Perhaps asking...
> Perhaps it would be better to target RHEL6?
>
The python software stack RHEL6 has is incompatible with transifex 0.9.0.
And we need to update to transifex 0.9.0 in order to be able to update
later to 1.0, which may use the RHEL6 python software stack.
Some solution we will find.
Doing a hand installation of intltool for F10 from the package in koji
with a command like
yum install --nogpgcheck ~/intltool-0.40.5-1.fc10.i386.rpm
and then installing transifex with
yum install --enablerepo=epel-testing transifex
it works. But I don't know if it would be acceptable.
kind regards
Domingo Becker
13 years, 4 months
RFC: SSH cipher change on pt7
by Jason Brown
Related to ticket #1406, a vulnerability was discovered in the CBC
cipher for OpenSSH v2. The recommended change is to only allow CTR and
arcfour ciphers to be used by sshd. This change took affect last night
on pt7. Please notify us of any issues you may have.
Thanks,
Jason
13 years, 4 months
Meeting Reminder 20:00 UTC Tomorrow
by Derek Carter
Add your agenda items to the trac instance with a keyword of 'meeting'
or
Respond to this email.
Unticketed items I'm aware of right now:
* FreeIPA FAS migration talks
* Our meeting has consistently ran into the Cloud FIG meeting
* should we move? or ask cloud to move back?
--
Derek
aka goozbach
13 years, 4 months
xmpp based nagios notifications
by Seth Vidal
This is really only relevant for the folks who get the nagios alerts but
I thought it was cool.
I setup a test jabber/xmpp address for fedora services it is:
fedora-svc-test(a)jabber.org
And then I wrote:
http://skvidal.fedorapeople.org/misc/xmppsend.py
and set the whole thing up on our nagios server(s)
I setup my contacts to add a: skvidal_xmpp contact
with contact email set to my xmpp/jabber address.
Then I added the fedora-svc-test address as a contact in my jabber
client.
And now I get nagios notices as popups in my jabber client(s).
-sv
13 years, 4 months
Introduction....
by Tim Casey
Hi everyone,
I've been lurking for awhile now, so thought I'd finally send off my
introduction email.
I'm currently working as a Migration Specialist in the Health industry.
Moving customers off a dying proprietary database on to ElevateDB.
I also study part time, decided to finish off my Bachelor of IT at RMIT.
I'm interested in helping out with the Fedora Talk (Asterisk) bugs/requests.
I'll be looking for a sponsor for sysadmin-tools once I've found my feet.
I'm in Melbourne, Australia, and can be found on freenode as timc. Feel
free to say hello.
Cheers
Tim
13 years, 4 months
RFC: hosted VCS changes, do we offer that as a service?
by David Nalley
I noticed three hosted tickets this afternoon (2466, 2369, and 1661)
that involve VCS changes.
I started looking into accomplishing the svn moves and I wonder if
this is a service we offer, or if we suggest that they prepare their
repository themselves, and we merely make an empty git repo available.
At least with the svn-to-git, it requires creating a list of users of
all users who have committed to the svn repo, so that git log is
properly populated. While not terribly hard, it can be a lot of time
to track down users (at least one of the respositories existed prior
to living on fh.o, so there isn't a one to one mapping of fas names,)
This strikes me as best done by those who know the repo rather than
people who administer the service.
I propose that we inform the users that they can make the change, and
we'll give them a new repo of whatever type, but that we don't
actually do the conversion ourselves. The only potential issue I see
with this is the potential for commits to to be made to the old VCS
before conversion is complete.
Thoughts, comments, flames?
13 years, 4 months
RFC: Work needed to be done.
by Stephen John Smoogen
0x1) Upgrading puppet to 2.6.4. We are currently on 0.25.2 (or 2.5.x
in new nomenclature). How to test deploy and build out?
0x2) Monthly upgrades.. lots of kernel and glibc updates so everything
needs to be rebooted.
0x3) Rebuilding RHEL6 systems and getting them ready
0x4) Moving .devel and .stg systems to dedicated hardware.
0x5) Moving to newer bacula
0x6) Rolling out new EL6 systems (what ones and why)
0x7) Mirror systems moving to Fedora hardware
0x8) Rolling out replacement hardware for old stuff
0x9) Nurturing and growing relationships with outside sponsors.
0xA) Documenting procedures, testing procedures, updating procedures
0xB) Tickets in queue
0xC) New projects
--
Stephen J Smoogen.
"The core skill of innovators is error recovery, not failure avoidance."
Randy Nelson, President of Pixar University.
"Let us be kind, one to another, for most of us are fighting a hard
battle." -- Ian MacLaren
13 years, 4 months
