Can we install puppet agent on multiple host machine using remote machine (considering puppet master is already installed on the remote machine)?

211 views
Skip to first unread message

Patil Jyotsna

unread,
Jan 30, 2017, 7:40:52 AM1/30/17
to Puppet Users
Can we install puppet agent on multiple host machine using one remote machine (considering puppet master is already installed on the remote machine)?

The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify ATMECS and delete it from your computer.

jcbollinger

unread,
Jan 31, 2017, 9:17:10 AM1/31/17
to Puppet Users


On Monday, January 30, 2017 at 6:40:52 AM UTC-6, Patil Jyotsna wrote:
Can we install puppet agent on multiple host machine using one remote machine (considering puppet master is already installed on the remote machine)?


I suppose you mean to ask whether you can use Puppet to do that.  No, generally you can't.  Puppet has no magic.  The agent is its way to apply remotely-specified configuration to any given machine; it follows that if the agent is not already installed then Puppet provides no way for a remote master to modify the system.  And that's exactly as you should want, for otherwise, what would prevent a rogue actor from using Puppet to apply changes of their choosing?

Puppet Enterprise does have mechanisms to facilitate installation of the agent, and there are various technologies for remote installation available for various computing platforms.  And for new deployments, it is advisable to incorporate agent installation into the provisioning and deployment process.  But no, Puppet does not do remote installation -- neither of itself, nor of anything else.  Do not be confused by the capability of the agent, once installed, to perform local software installation as directed by catalogs provided to it by a remote master.


John

James Perry

unread,
Jan 31, 2017, 3:24:50 PM1/31/17
to Puppet Users
Prior to installing Spacewalk on my Linux hosts to push updates / packages, I used to do the following:

1. Setup SSH trust from a secured account to Remote host with sudo permissions to root.
2. Remotely copy and install the Puppet Agent
3. Remotely run, as root, <path to puppet>/puppet config set server=<puppet master> 
4. Remotely run puppet agent --test --verbose to generate the initial key exchange.
5. Sign the key on the master.
6. Remotely re-run the puppet agent --test --verbose to verify it is communicating with the master, which usually gives the error that the host isn't yet setup on Puppet, as expected. 
7. After setting up host and testing that the catalogs are processing correctly, remote run chkconfig puppet on via sudo. 
Reply all
Reply to author
Forward
0 new messages