![Constant Contact Market leader for Small Businesses ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
Similar to Puppet at Constant Contact: Configuration as Code
Similar to Puppet at Constant Contact: Configuration as Code (20)
Recently uploaded
Recently uploaded (20)
Puppet at Constant Contact: Configuration as Code
- 1. Puppet at Constant Contact Adoption, the process
- 14. Daemon mode, at last
- 15. Cultural Change, part one Ok, let’s start with Incremental Config & Push
- 16. Time to market better, but…
- 17. Special thanks to: Our DevOps, “we can do this with Puppet” guy, Mark Schena & our puppetmaster, AleksMargan
- 18. Cultural Change, part two
- 19. It works, right? Yes, errr. Well… kinda.
- 20. 12
- 22. The dream of CI
- 23. Fix The Flow
- 24. I Я COW!
- 27. 19
- 30. code
- 31. puppet module
- 33. database schemaRepository layout Source Control
- 37. complete set of puppet modules environment environment environment environment QA-1 QA-2 PROD Deployment puppetmaster
- 38. Thanks! “Dave Connors” <dconnors@constantcontact.com> VP, Operations “Hawk Newton” <hnewton@constantcontact.com> Software Architect
Editor's Notes
- Quick snapshot of CTCTLittle bit on how we adopted PuppetThen over to the cleanup hitter
- Fast growingMicro businessesOffices in Loveland, Boca, SF and NYCLots of apps, at decent scale --- Top 20 email senders worldwide
- Business DriversDiverse: not all uniform web app servers multiple applicationsDistributed: memcached, sso, coherence, cassandraManage it cost-effectively, keep things consistent in order to max uptime and mean time to recovery - don’t slow down the rate of changeAnd oh yeah, improve gross margins
- We hit a bit of a tipping point on managing servers, couple of hundred or soStarted with a small piece of the puzzleSystem stuff resolve.conf, host…etcWork out the basic process, gain trust
- Getting adoption by leaving control in hands of adminsThe declarative model was challenging to many at firstPush via func was a good interim step
- Good news along the way thoughConfidence gained – Automated System Warning!Moved mail subsystem to daemon modeStandard well understood configuration postfix and centosSystems folks were onboard
- Change in control, ownership, processesRetooling without stopping rate of changeGaining trust while changing folx mindset
- Manage social data cost-effectively3 months cycle, cheaperBut still had challenges around branching and testingIntegration in pre-productionIndependent upgradesSo we had some work to do, including orchestration
- Quick Shout Out
- We could only go so far pulling from the Systems sideBut it had to work for Developers, so…Here you go Dev, own the config, trust in Hawk
- The monolith!We had some significant challenges:New appsUgly handoffsEnvironmentsDecreased velocityFUDFrustrated parties on both sides of the house…