puppet provisioning

System version: CentOS release 6.6 (Final)1.puppet Installation#安装puppet官方源rpm-IVH https://yum.puppetlabs.com/puppetlabs-release-el-6.noarch.rpm# Import gpg key rpm--import https://Yum.puppetlabs.com/rpm-gpg-key-puppetlabs #安装rubyyum install ruby ruby-libs ruby-shadow# installation Puppetyum installed puppet Puppet-ser

树结构如下： |-- puppet.conf #主配置配置文件 |-- fileserver.conf #文件服务器配置文件 |-- auth.conf #认证配置文件 |-- autosign.conf # 自动验证配置文件 |-- tagmail.conf #邮件配置文件（将错误信息发送） |-- manifests #文件存储目录(puppet 会先读取该目录的.PP 文件) | --nodes | | | puppetclient.pp | |-- site.pp #定义puppet 相关的变量和默认配置。 | |-- modules.pp #加载class 类模块文件（include syslog）

Puppet PP profile has not been vim support, edit the black background white, not easy to row wrong, it seems difficult to distinguish, need to make further changes to perfect display You must add 2 files to the. Vim in the user's root directory, as follows: 1 Vim directory to create the Syntax/puppet.vim: #mkdir ~/.vim #cd ~/.vim #mkdir syntax #vim Syntax/puppet.vim Add the following: ===========================================================

1, Puppet Environment Deployment 1. puppet-Large-scale cluster deployment management artifact 2. Installing Puppet servers and clients on CentOS and RHEL 3. Saltstack detailed deployment of Debug 4. Puppet error:400 2, Saltstack basic Knowledge 1. Use of the State.sls of Saltstack/salt (v) algorithmic architecture

The first thing that comes to mind is greed... Definitely not... T Then we found that it was actually DP-enabled... However, we need to sort them first. If f [I] indicates that the first puppet has to lose a few at worst F [I] = max (F [J] + calc (J + 1, I) where j The calc (x, y) function compute can discard a maximum of several matching functions from the X to the Y puppet. The method is as follows: Hzw

(1) Error Log:Http://storageboy.com/2013/04/25/quick-tip-on-installing-and-running-redhats-openstack-distro/ERROR: Error during puppet run: err:/Stage [main]/Packstack: Netns/Exec[Netns_dependecy_install]/returns: change from notrun to 0 failed: Command exceeded timeout at/var/tmp/packstack/modules/packstack/manifests/netns. pp: 13 (2) solution: # Vim/usr/lib/python2.6/site-packages/packstack/puppet/modul

I. Configuring automatic registration RulesServer End:Vim/etc/puppet/autosign.conf*.puppet.com # specifies the range of domain names that are automatically registered ( IP no validation, no certainty)Second, clear the authentication configurationPuppet cert list--all ViewPuppet cert--clean client1.puppet.com # clear Set up configurationThird, clean up the client configurationCd/var/lib/puppet/ssl RM-RF * Re

(1) error log: Warning (1) error log:Http://storageboy.com/2013/04/25/quick-tip-on-installing-and-running-redhats-openstack-distro/ERROR: Error during puppet run: err:/Stage [main]/Packstack: Netns/Exec[Netns_dependecy_install]/returns: change from notrun to 0 failed: Command exceeded timeout at/var/tmp/packstack/modules/packstack/manifests/netns. pp: 13 (2) solution: # Vim/usr/lib/python2.6/site-packages/packstack/

System Environment: centos6.3 puppet:puppet-2.7.13 facter:facter-1.6.5 Ruby:yum Source Note: Facter used to obtain client system information (such as HOSTNAME,IP,OS-VERSION,FQDN, etc.) Ruby is the puppet development environment Puppet server:192.168.7.196 Puppet client:192.168.7.197 (server) configuration only for servers (client) configured for client-

The architecture is as follows: ============================ Manifests =========================== 1,at/etc/puppet/mainfests ------------------ Site.pp +++++++++ Import "MODULES.PP" Import "NODES/*.PP" ------------------------------- 2,at/etc/puppet/manifests/nodes ------------------- Node_master.pp ++++++++ Node ' master.puppet.com ' { Include Nginx Include PHP Include MySQL } -------

I haven't written any technical content for a long time. I want to write an article today (my colleagues found that I am only a porter): I ran puppet and giant cards on some machines running mongodb, it takes tens of minutes to run, and the top seems to be the cpu resources occupied by the system instead of the user. solution: Run mong for a well-known reason. I haven't written any technical content for a long time. I want to write an article today (

Puppet's automated distributed environment has strict time requirements, and the following errors may easily occur during routine operations: Triggering test.cn7788.comHost test.cn7788.com failed: certificate verify failed. This is often because the time is out of sync on the server or clienttest.cn7788.com finished with exit code 2Failed: test.cn7788.com You can follow the error message "This is often because the time is out of sync on the server or client". Generally, if a similar word appear

Experimental environment: puppetserver.rsyslog.org Mcollective Client +ACTIVEMQ service side +puppet service end agent1.rsyslog.org Mcollective Service-Side +puppet Client Application: Apache agent2.rsyslog.org Mcollective Service-Side +puppet Client Application: Apache+mysql agent3.rsyslog.org Mcollective Service-Side +

The architecture is as follows ============================ Manifests ============================ 1,at/etc/puppet/mainfests ------------------ Site.pp +++++++++ Import "MODULES.PP" Import "NODES/*.PP" ------------------------------- 2,at/etc/puppet/manifests/nodes ------------------- Node_master.pp ++++++++ Node ' master.puppet.com ' { Include Cron } ------------------------------------

;GID: Basic Group IDGroups: Additional groupsHome: Home DirectoryShell: Default shellName:namevarSystem: Is it user, True|falseUid:uidPasswordFileManage files and their content, dependencies, and permissions, which can be given directly through the content property or downloaded from the remote server path via the Source property;Indicate the source of the file content:Content: Direct file contents, support \ n (newline), \ t (tab);Source: Download the file from the specified location;Recurse:tr

Today to introduce the specific practical functions of puppet, in fact, my understanding is how lazy, hehe. 1. Fill in the contents of the file: (server): To modify the server-side configuration file: # VI/ETC/PUPPET/MANIFESTS/SITE.PP ----------------- Node default{ file {"/tmp/test": Content=> "This is a test file"; } } ----------------- Restart the puppetmaster to update the profile informatio