Puppet is not really designed to do what you're asking. The idiomatic
Puppet way to install ksh on all your nodes would be to create a node
declaration for each host and either add Package[ksh] on each node or have
them include a class with that resource definition.
If you're looking for a way to push but not manage configurations remotely,
you might want to try scripting with MCollective or something like it.
-- Jenner
On Wednesday, September 5, 2012 12:30:05 PM UTC-7, am-aaron wrote:
>
> hello fellow engineers:
>
> i am currently developing a Puppet manifest to Deploy (Install, Configure)
> a Software Package onto a number of Nodes from a Machine that is network
> connected to the Nodes (can ssh). the Yum Repo for the Nodes is on this
> Deployment Point.
>
> it was and still is very surprising to find that Puppet does not have a *
> Resource* to allow a *Remote Package* installation to be done.
> *Package{}*works on the current Node and will use
> yum by default to install a Software Package. however, if i want to do a yum
> install from another Deployment Point, Puppet does not offer a Resource.
>
> Local Package Install:
> package { 'ksh':
> ensure => installed
> }
>
> i also found out by simply trying that i can do a installation using lists
> as in (also found on Puppet Cookbook much later):
> package { [ 'ksh', 'mksh' ]:
> ensure => installed
> }
>
> but, if i want to install ksh onto Node node from Machine master, i need
> to use *Exec*:
> # Install package
> exec { 'remote-install':
> command => "/usr/bin/ssh root@node 'yum -y install ksh'",
> returns => 0,
> logoutput => on_failure,
> }
>
> what does Puppet Labs and the User Community recommend? is it better and
> more efficient to create a second Puppet manifest for the Nodes so that i
> can use Package{}? that would mean:
> * additional Puppet manifests for the Nodes in addition to the manifest on
> the Deployment Point, which is used for configuration;
> * additional communication between the Puppet Agent and Puppet master for
> package installation (?);
> * additional overhead of maintaining two Puppet manifests;
> * additional overhead of synchronizing the Installation on Nodes with the
> Configuration on Deployment Point.
>
> why does PuppetLabs simply not offer simple Resources to do what we
> require here? is there some Puppet ic way of designing and coding manifests
> that i do not know about?
>
> thank you very, very much in advance.
>
> ciao,
>
> Aaron
> --
> { celltext Nokia E90 Communicator: +353-89-420-8033; Skype: am-aaron }
>
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail.
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/Dj_X8EmpDswJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
