puppet agent

Before using any software, we need to understand how it works, otherwise it will cause a lot of inconvenience to the subsequent use. Puppet uses a very simple C/s architecture, all data interaction through SSL, to ensure security. It is shown in Workflow 1.650) this.width=650; "title=" Figure 1 Puppet Workflow "src=" Http://ipad-cms.csdn.net/cms/attachment/201209/5048569d92738.jpg " height= "325" width= "37

scheme to enhance Master's ability to compute "pseudocode." Typically, this architecture supports about 1000 servers. Of course, it also depends on whether your system is "complex" enough. Fig. 2 Loadblancer Scheme There are two common implementations of this architecture: Apache+passenger, and Nginx+mongrel. This article will take the latter as an example to briefly describe its working methods. 1. Puppet Master runs multiple processes:

addition, community developers and donors are constantly enhancing the functionality of Puppet. A large developer and user community is also committed to providing Puppet documentation and technical support. Puppet is also easy to expand. Custom software package support and special system environment configuration can be quickly and easily added into the

Environment Description:192.168.153.133 Master.localdomain #Puppet Server192.168.153.134 Agent1.localdomain #Puppet AgentThe machine name here does not have the underline and other special services, otherwise it will be reported "the scheme puppet does not accept registry part" error message.1. Installing puppet Server

localhost. localdomain localhost: 1 localhost6.localdomain6 localhost6192.168.0.200 master.gangpao.com puppet192.168.0.202 agent02.gangpao.com agent02(2) modify the hostname# Vim/etc/sysconfig/networkNETWORKING = yesNETWORKING_IPV6 = noHOSTNAME = agent02.gangpao.comGATEWAY = 192.168.0.1#/Etc/init. d/network restart8. Start the Server Service(1) generate the config file# Puppet -- genconfig>/etc/puppet. con

puppetmaster startStart puppetmaster: [OK][Root @ master ~] # Netstat-tunlp | grep: 8140Tcp 0 0 0.0.0.0: 8140 0.0.0.0: * LISTEN 9148/ruby Start[Root @ master ~] # Chkconfig -- list | grep puppetPuppet 0: Close 1: Close 2: Close 3: Close 4: Close 5: Close 6: ClosePuppetmaster 0: Close 1: Close 2: Close 3: Close 4: Close 5: Close 6: Close[Root @ master ~] # Chkconfig puppetmaster on[Root @ master ~] # Chkconfig -- list | grep puppetPuppet 0: Close 1: Close 2: Close 3: Close 4: Close 5: Close 6:

' $confdir/ssl '. ssldir = $vardir/ssl autosign = True Server = master.com Start puppetmaster[[email protected] ~]# service puppetmaster startStart puppetmaster: [ OK ][email protected] ~]# NETSTAT-TUNLP | grep:8140TCP 0 0 0.0.0.0:8140 0.0.0.0:* LISTEN 9148/ruby Boot up[email protected] ~]# chkconfig--list |grep puppetPuppet 0: Off 1: Off 2: Off 3: Off 4: off 5: off 6: Offpuppetmaster 0: Off 1: Off 2: off 3: off 4: off 5: off 6: Off[email protected] ~]# chkconfig puppetmaster on

Tags: des HTTP Io OS AR for SP on Log Puppet's commands Puppet's command line interface consists of a singlePuppetCommand with subcommands. Puppet's companion utilities, facter and hiera, have their own command line interfaces, which differ slightly from puppet's. Core Services The following subcommands are the main applications puppet uses to manage systems. Every user shoshould understand what they do. Puppe