Is there a way to deploy our configuration to agent.

[Ayyanar]

If you know the answer say "Yes" or "No".

Thanks,
Ayyanar Thangaraj

[Brendan Murtagh]

Please go into more detail. Are you referring to changing the Puppet agent config on your nodes or something else?

[Ayyanar]

On Wednesday, 29 July 2015 17:59:02 UTC+5:30, Brendan Murtagh wrote:

Please go into more detail. Are you referring to changing the Puppet agent config on your nodes or something else?

1. I have two agent  ip-10-109-189-241.ec2, ip-10-233-92-172.ec2.internal  node.
2. I want to deploy my configuration to the agents in master itself.
3. I don't want to login to agent and fetch the configuration.

example:

node ['ip-10-109-189-241.ec2.internal' ip-10-233-92-172.ec2.internal] {
        include directory-creation
}

I want to deploy directory-creation class file to agents.

Thanks for your commands.
Ayyanar Thangaraj.

 

[jcbollinger]

Neither Puppet nor any other software running on a given machine can effect changes to a different machine without some form of cooperation for the target machine.

The longstanding default approach to this is to configure each machine to run the agent on a schedule, either via the agent's built-in scheduler (active when running the agent in daemon mode) or via an external scheduler such as cron.  The traditional run interval is 30 minutes, but there is nothing special about that particular timing.

If you want to run the agent on demand on your target machines, but without logging in to the individual machines, then you're looking for some form of remote control software.  Puppet is not such software, but PuppetLabs's MCollective can serve in that role, and it has good integration with Puppet.


John

[Ayyanar]

Thanks John