(→SQL Databases) |
(→Useful pages: remove "Test") |
||
(21 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
+ | [[File:Valstar.jpg|300px|right]] | ||
= Contact/join the team = | = Contact/join the team = | ||
− | * join the [irc://irc.freenode.net/#mageia-sysadm IRC channel] and/or subscribe to [https:// | + | * join the [irc://irc.freenode.net/#mageia-sysadm IRC channel] and/or subscribe to the [https://ml.mageia.org/l/info/sysadmin-discuss sysadmin-discuss] mailing-list |
− | * team is built from: | + | * team is built from: see [http://people.mageia.org/g/mga-sysadmin.html mga-sysadmin ldap group] |
− | |||
= Participating to the team = | = Participating to the team = | ||
− | The whole infrastructure is managed by Puppet and | + | The whole infrastructure is managed by Puppet and git. The repository is public, and can be found at http://gitweb.mageia.org/ under the Infrastructure section. |
− | If you wish to join the team, the recommended way is to study how the infrastructure is organized, and start sending | + | If you wish to join the team, the recommended way is to study how the infrastructure is organized, and start sending patches as in any free software project. |
To get a checkout of our puppet configuration, you use : | To get a checkout of our puppet configuration, you use : | ||
− | + | git clone git://git.mageia.org/infrastructure/puppet | |
− | To test it, you should use a virtual machine, running | + | To test it, you should use a virtual machine, running Mageia, and you will need a recent puppet backport ( > 2.6.0 ). Any virtualisation technology should work. |
== Infrastructure clone == | == Infrastructure clone == | ||
To replicate our own infrastructure for test purpose, the main puppet server should be on a computer who can be contacted on puppetmaster.$yourdomain. | To replicate our own infrastructure for test purpose, the main puppet server should be on a computer who can be contacted on puppetmaster.$yourdomain. | ||
− | It is much easier to call the computers like we do ( valstar being the main node ), see [http:// | + | It is much easier to call the computers like we do ( valstar being the main node ), see [http://gitweb.mageia.org/infrastructure/puppet/tree/manifests/nodes.pp] ). Using our configuration will automatically checkout in /etc/puppet |
− | on the puppetmaster, so | + | on the puppetmaster, so please be aware of this. For the more advanced tests, a ldap directory |
− | is needed, even if almost empty. | + | is needed, even if almost empty. |
− | = | + | = Mailing lists = |
− | + | * [https://ml.mageia.org/l/info/sysadmin-discuss Sysadmin discussion list] | |
+ | * Other lists can be found [https://ml.mageia.org/l/lists/sysadmin on this page] (commits, bugs, reports, etc ...) | ||
− | + | = User accounts requests = | |
+ | Requests about user accounts or additional permissions should be done using bugzilla on the [https://bugs.mageia.org/enter_bug.cgi?product=Infrastructure&format=guided Infrastructure -> Account request] component. | ||
− | == | + | = Useful pages = |
− | |||
− | * | + | * [[Pushing_updates|Pushing package updates]] |
− | * | + | * [[SOP_Sysadmin_access_revocation|Removing Sysadm access]] |
− | * | + | * [[SOP_Certificate_update|Updating SSL Certificates]] |
− | * | + | * [[SOP_Version_and_Release_freeze|Controlling version/release freeze]] |
− | * | + | * [[SOP_Rename_user|Renaming users]] |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | [[Category:Sysadmin]] [[Category:Teams]] | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 22:05, 18 March 2020
Contents
Contact/join the team
- join the IRC channel and/or subscribe to the sysadmin-discuss mailing-list
- team is built from: see mga-sysadmin ldap group
Participating to the team
The whole infrastructure is managed by Puppet and git. The repository is public, and can be found at http://gitweb.mageia.org/ under the Infrastructure section.
If you wish to join the team, the recommended way is to study how the infrastructure is organized, and start sending patches as in any free software project.
To get a checkout of our puppet configuration, you use :
git clone git://git.mageia.org/infrastructure/puppet
To test it, you should use a virtual machine, running Mageia, and you will need a recent puppet backport ( > 2.6.0 ). Any virtualisation technology should work.
Infrastructure clone
To replicate our own infrastructure for test purpose, the main puppet server should be on a computer who can be contacted on puppetmaster.$yourdomain. It is much easier to call the computers like we do ( valstar being the main node ), see [1] ). Using our configuration will automatically checkout in /etc/puppet on the puppetmaster, so please be aware of this. For the more advanced tests, a ldap directory is needed, even if almost empty.
Mailing lists
- Sysadmin discussion list
- Other lists can be found on this page (commits, bugs, reports, etc ...)
User accounts requests
Requests about user accounts or additional permissions should be done using bugzilla on the Infrastructure -> Account request component.