puppet server

As the company's application demand increases, the number of servers is also increasing. As the number of servers increases, we will find that a puppetmaster is under great pressure and resolution is slow, in addition, there may be errors such as "time out" from time to time. Is there any optimization solution? We found a solution on the official Puppet website. We found that puppetmaster can configure multiple ports and combine them with WEB Proxy (N

puppet Certificate Automatic certification of learning summaryThis article mainly introduces briefly puppet Certificate automatic authentication, due to manual authentication is more cumbersome. puppet installation is not described here, refer to the previous document "puppet Introduction and based on httpd instance D

, software client installation. Of course puppet clients can also be installed and configured in Kickstart. When the system is running stably, now we need to adjust and manage some of the servers, such as to modify the system parameters of 100 servers, remote command, and so on, how to operate? We might think of a script, a good idea, if you have to manually go to 100 servers to execute the same script, or modify a certain configuration, is not also

" ============== =================================== mysql> Create database puppet CHARACTER SET UTF8; Mysql> grant all privileges in puppet.* to Puppet@ ' localhost ' identified by ' puppet '; mysql> flush Privileges; # cd/usr/share/foreman/rails_env=production Rake db:migrate rake puppet:migrate:po

Puppet automated Nginx + Mongrel server load balancer configuration preface * as the company's application demand increases, the number of servers will also increase. when the number of servers increases, we will find that a puppetmaster is under great pressure and the resolution is slow. What are the optimization methods at this time... puppet automated Nginx +

puppet Getting StartedSkip to end of metadata 1puppet Puppet is an open source software automation configuration and Deployment tool, and many large IT companies are using puppet to manage and deploy software in a cluster. 2. The Design architecture Puppet is based on the C/S architecture. The

is, each git repository corresponds to a grouped puppet configuration.Second, the realization of the functionThe functions that Git management puppet can achieve are as follows:1. Unified installation and configuration management software2. Unified configuration System optimization parameters, modify the configuration file3. After the server restarts, you can ha

Puppet automated Nginx + Mongrel Server Load balancer configuration preface * as the company's application demand increases, the number of servers will also increase. When the number of servers increases, we will find that a puppetmaster is under high pressure and has slow resolution. Is there any optimization method at this time? The answer is! The Puppet offici

Nginx-to-(apache+foreman+puppet) Load BalancingFirst, the prerequisite preparationTest environment:Os:centos 6.5_x86puppet-server-3.8.3foreman-1.9.2foreman-proxy-1.9.2httpd-2.2.15The server is set up. Apache+foreman+puppet for details, please refer to:http://4709096.blog.51cto.com/4699096/1710697Second, modify the Pupe

How the puppet client cancels the active updateRunintervalHow often puppet agent applies the client configuration, in seconds. Note that a runinterval of 0 means "run continuously" rather than "never run." If you want puppet agent to Never run, you should start it with the--no-client option. Can be specified as a duration.default:30mroughly means that the

Dashboard is the puppet console for displaying information about puppet Master and puppet agents. This article provides Web services with the default Webrick. DashBoard installed in master.test.com. And in the client configuration file do the following configuration#vim/etc/puppet/puppet.conf[Agent]Report = TrueFirst,

In the production environment, the puppet update needs the node to update automatically, there is need to push the update through the puppetmaster, and the node update time is discrete. Here are three ways to update 2.7 Puppet update mode 2.7.1 Node Timing update [Root@agent1 ~]# vim/etc/puppet/puppet.conf [Main] Server