[Mageia-sysadm] Clearifying questions

Joerg Stephan johe.stephan at ymail.com
Mon Sep 17 12:45:58 CEST 2012

Hi there,

nice topics, all of them

1. Topic: Virtual Machines
What do we use? xen/kwm/vmware? I already done automatic setups for xen machines on our side. I could take a look. Could be hart whitout accessing the machines.

2. Topic sympa emails
maybe we could maniulate the databases. For we use LDAP shouldnt be the problem if both systems can interact. 

3. On the Sysadmin side
Backups could be done via bacula. i could set that up. Would be easy to integrate that in puppet for the clients. Needs talking about schedule for incremental and full backups. And i would need access to a backup server.

4. This ruby puppet
I used to not running an puppetd on the none masters. I use a ssh script via public_key which rtuns the agent on the system when i need it. Its scripted. So after i made changes to puppet i trigger the script and let the client run.

5. I made a copy of the puppet svn and will have a closer look this evening.

Kind regards
From: nicolas vigier <boklm at mars-attacks.org>
To: Mageia Sysadmin discussions <mageia-sysadm at mageia.org> 
Sent: Monday, September 17, 2012 11:01 AM
Subject: Re: [Mageia-sysadm] Clearifying questions

On Sun, 16 Sep 2012, Joerg Stephan wrote:

> Good morning @All,
> i have some questions:
> 1. Who can grant me access to the systems?

We cannot give root access to the servers to anybody who asks. We need
to trust people who get root access, so we need to know them very well,
for a long time, and we need some proof that they will be helpful in
the team and that they know what they are doing, for instance by seeing
that they have made useful contributions to Mageia in the past.

However there are many areas where it's possible to help without having
root access. For instance :
- we need to find a solution so that email changed on
  identity.mageia.org is automatically changed on sympa mailing lists.
  This require making some changes to identity and/or sympa.
- we need to make mirrorlist redundant, for instance by allowing
  generation of static files by MGA::Mirrors, so that we can copy the
  files on a 2nd server, and changing urpmi to be able to use 2 servers
- we need to work on some tools to manage virtual machines creations /
  deletions by contributors on a server, to allow them to use test VMs
- there is a lot of bugfix or improvements to be made on build system

> 2. Do we have a Todo list? Where can i see current projects of the sysadm team.

Many bugs are assigned to sysadmin on bugzilla :

A few on the wiki :

And others that you can see by following discussions on mailing lists.

> 3. What is this: /usr/bin/ruby /usr/sbin/puppetd -o --no-daemonize -l syslog i mean, why does rruby start the puppetd (?!?)

Because puppet is written in ruby.

> 4. Are there ayn meetings scheduled?

Not at the moment, but we can schedule one if someone thinks there is
important topics to discuss.

> 5. Do we have a system description, like which server does what?

You can see that in puppet configuration.

Mageia-sysadm mailing list
Mageia-sysadm at mageia.org

More information about the Mageia-sysadm mailing list