On Tuesday, August 27, 2013 10:05:09 AM UTC-5, am-aaron wrote: > > good afternoon Jenner and JC Bollinger: > > the question is connected to deployment (installation and configuration) > of VCS. since VCS is quite popular in the indiustry, this will help many > people. > > thank you Jenner and JCB for your informative responses. i apologize > because my initial response to Jenner was not really nice. i was stressed > due to the deadline. i Normally do not use ¬that language and tone¬. > > initially, i hesitated to explain which software had to be deployed, but > now, here goes: > - we want to deploy Veritas Cluster Server (high-availability cluster > software) onto multiple RHEL Nodes from a separate RHEL management node. > - Puppet Master runs on the Manager and each Node runs Puppet Agent. > - VCS software is a collection of RPMs with a separate installer > executable. > - software can be installed using the Installer that uses SSH to install > the RPMs onto multiple nodes, given the list. > - software can also be installed by simply installing the RPMs directly on > each Node. > - the VCS RPMs have to be installed in a specifc order. > - once the RPMs are installed, a second Installer program is available on > each Node, allowing Cluster Creation from one of the Nodes. > > Questions > - which Puppet resource can we use to run the VCS software installer > executable from the Puppet Master? > the list of Nodes is to be passed to the Installer. >
None*. The master just records resources in a catalog, which it then passes on to the client to apply. You can, however, use the generate() function to run a program on the master during catalog compilation. Your node list would need to be hardcoded into the appropriate manifest, loaded from some external source (e.g. via Hiera), or fed in by an external node classifier (ENC). [*] Of course, the master can be its own client. In that context, you could use an Exec resource to run the installer. Inasmuch as this seems to be a singular, once-per-cluster activity, it is probably not something best done via Puppet. > - if we want to install the VCS RPMs directly ourselves onto multiple > Nodes, we can: > - use Puppet 'package' on each Node or > - use 'exec' on the manager to ssh and yum RPMs to multiple Nodes. > is there a better way to use Puppet for this? > Package resources are the Puppet way to do this. Put the needed RPMs into a private Yum repository, and use Packages to ensure them installed. If the RPMs have correct dependency information then you might not need to declare all the needed packages individually, for Yum automatically finds and installs needed dependencies when they are available. > > - VCS comes with: > - an Installer to install VCS software onto all Nodes; > - an Config program to create the Cluster; > - CLI commands to create resources to be monitored. > so, i think that it would be best to use Exec to run these programs. > > If you want Puppet to cause a program to be run on a node, then an Exec resource is the way to describe it. Alternatively, you could consider creating a custom resource type for the purpose. Either way, though, I am somewhat doubtful that Puppet is the best tool for this job. What do you hope to gain over just running the Installer and Config programs directly? John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
