puppet camp tokyo 2014: why we stopped using puppet agent daemon

13
Why we stopped using Puppet Agent Daemon Katsuaki AWAIISHIMA VOYAGE GROUP, Inc.

Upload: puppet-labs

Post on 10-May-2015

585 views

Category:

Spiritual


2 download

DESCRIPTION

"Why we stopped using Puppet Agent Daemon" presented at Puppet Camp Tokyo 2014 by Katsuaki Awaiishima, Voyage Group

TRANSCRIPT

  • 1.Why we stopped using Puppet Agent Daemon Katsuaki AWAIISHIMA VOYAGE GROUP, Inc.

2. In this session This year, We enhance the start of the new IDC, I have changed each time the application by mcollective's puppet plugin from starting up this operation of the puppet agent daemon. Why changed, What I wanted to What came to be, and what can no longer be Challenges for the future 3. Me Name: Katsuaki AWAIISHIMA ( ) Company: adingo, Inc. (in VOYAGE GROUP) Service: Fluct (http://fluct.jp) Mission: Infrastructure management Favorite: cobbler/puppet/vagrant etc.., *BSD 4. Fluct? (SSP?) 5. Infrastracture IDC #1 ! Deliver Impression Logs Management etc.. IDC #2 ! Deliver AWS ! Deliver Over 200 Servers 6. Why changed, What I wanted to Purpose of using the puppet has changed. As well as configuration management, to deploy management. For testing, change the settings only some servers. 7. Configuration/Deploy Management Manifests to be taken from github. No automatic apply, using mco puppet agent. Mcollective/Deploy Management explained in the session by Ms. Kondo. 8. puppet/mcollective/rabbitmq (normal operation) puppet master dlv server #1 rabbitmq dlv server #2 dlv server #3 dlv server #4 mco puppet -I /.*/ runonce puppet agent --test --color=false me ! me ! me !me ! 9. puppet/mcollective/rabbitmq (single host) puppet master server #1 rabbitmq server #2 server #3 server #4 mco puppet -I /#4/ runonce puppet agent --test --color=false not me not me not me me ! 10. What came to be, and what can no longer be Apply specific manifests (branch) to a server using mcollective (mco puppet agent). Apply Manifest to the server is no longer automatic. Need to ensure that do not change the settings on the server, and check changes automatically. 11. Challenges for the future Version control of the catalog that have been applied Plugin agent result of puppet mco puppet status cant catch error in catalog compile. (syslog can do) 12. And others.. Now, we can deliver dlv servers at instant power on. It use only cobbler and puppet, no use of mcollective. If you have interested in, talk later. 13. Welcome to AJITO VOYAGE GROUP AJITO Thanks.