Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

How to bring continuous configuration benefits to legacy systems


Published on

New security threats and the the growing regulations make automation and compliance not only an option but a requirement, even for production systems that were not designed with automation in mind. Adding automation tools on existing production services might sound like a nightmare, but you won’t go from legacy to fully automated public Cloud / immutable infrastructure / Continuous Infrastructure in a day. With the right tools and methodologies, and small iterations, it is possible to sanitize and prepare convergence towards modern standards.
Based on real life examples, this talk will go through the different phases of the process. It will cover the identification of the needs, how to chose the first points to automate, the reverse engineering of the infrastructure’s state, the automation and API-fication of the configuration, the continuous checking of its compliance, and the ability to move to new infrastructure standards.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

How to bring continuous configuration benefits to legacy systems

  1. 1. Rudder for continuous audit and configuration How to bring Continuous Configuration benefits to legacy systems
  2. 2. Automating and standardizing technical baseline Onboarding new employees Auditability / Traceability / Compliance
  3. 3. Rudder
  4. 4. Building configuration rules File templating : jinja2
  5. 5. Provisioning process Perimeter definition Integration to internal tools
  6. 6. # memcached parameters -p {{ cmdb.apps.memcached.port }}
  7. 7. 1. Start by internal infrastructure 2. Migrate existing automation 3. Fully automated provisioning 4. Use policies in audit mode on existing nodes 5. Fix policies/nodes and move to enforce mode 6. Repeat from 4 with older machines
  8. 8. Adapting processes Access to compliance data Compliance for customers Contribution to changes
  9. 9. Normation – 87 rue de Turbigo, 75003 PARIS, France – +33 – 16 Questions?