From Mageia wiki
Jump to: navigation, search
(Useful pages)
(Update svn to git usage)
Line 5: Line 5:
  
 
= Participating to the team =
 
= Participating to the team =
The whole infrastructure is managed by Puppet and SVN. The repository is public, and can be found at: http://svnweb.mageia.org/adm/
+
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 patchs, like any free software project.
+
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 :
   svn co svn://svn.mageia.org/svn/adm/puppet/
+
   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.  
 
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.  
Line 17: Line 17:
  
 
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://svnweb.mageia.org/adm/puppet/manifests/nodes.pp?view=markup|manifest/nodes.pp] ). Using our configuration will automatically run a svn checkout in /etc/puppet  
+
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 take care if you plan to use git-svn or similar. For the more advanced tests, a ldap directory  
+
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.
  

Revision as of 16:58, 1 April 2015

Valstar.jpg

Contact/join the team

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

User accounts requests

Requests about user accounts or additional permissions should be done using bugzilla on the Infrastructure -> Account request component.

Useful pages