Difference: ComputingPuppet (2 vs. 3)

Revision 32014-05-12 - samir

Line: 1 to 1
Changed:
<
<

USCMS T2 Puppet

>
>

T2 Puppet

  The goal of this page is to document notes for a puppet deployment that is generic enough to work on any OSG CMS T2 site (and potentially T3s).
Line: 13 to 13
 
  • It would be cool if we can create a model where one can configure Hiera, site.pp, install the modules and be happy.
  • For worker-nodes, not assume that everyone is using Condor. Or Hadoop. These guys have to be modular. CMS and OSG software(OASIS) though, should be standard.
Added:
>
>
 

Hiera

Where Hiera will be used for. It's not in a lot of places. But here and there in different profiles :

Line: 45 to 48
 
  • gridftp-hdfs packages (replace precise list here)
  • lcmaps (different of the glexec one) -- I call this lcmaps-simple (from what I remember the same for CE or SE).
  • (not mandatory) Gridftp configuration file - it would be cool to have a way to configure in the puppet module, a limit for active transfers (in case of servers that can't handle a lot).
Added:
>
>

Deployment notes for nodes/modules

CE

  • Setup OSG 3.1, hadoop client. Make sure that ls /mnt/hadoop works
  • yum --enablerepo=osg clean all
  • Setup OSG 3.2
  • Run puppet module
  • Copy config.d tarball
  • Configure GUMS authentication (LCMAPS) by hand (no big deal)
  • Look at CEMON
  • Test with RSV
  • Go through the "Services" part and update module
 -- Main.samir - 2014-04-11
View topic | History: r8 < r7 < r6 < r5 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback