Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

DevOps Practices: Configuration as Code

60 398 vues

Publié le

The DevOps movement, like its Agile predecessor, is focused on improving the communication and collaboration between the development and operations teams responsible for different aspects of an app throughout its lifecycle. While successful DevOps initiatives start and end with organizational and cultural change, there are also common practices that are enablers and/or tools used in support of DevOps. In this session you will learn about the DevOps practice of Configuration as Code &ndash managing and maintaining application configuration as versionable assets. This session will focus on the practice of Configuration as Code, while demonstrating a few of the popular tools available today, including Opscode Chef, Powershell DSC (Desired State Configuration) and others. If you are interested in implementing a DevOps initiative in your organization, then this session is a must-see.

Publié dans : Technologie
  • Login to see the comments

DevOps Practices: Configuration as Code

  1. 1. Execution Code Application Environment
  2. 2. collaborate ensure correct configuration “continuous deployment” “configuration drift”.
  3. 3. Environment Configuration Define the Environment Structural Configuration Idempotent Automation Define the capabilities of the node e.g. 3 Nodes (2 Web Severs, 1 Database Server) (Dev  Test  Production) e.g. Windows IIS Make It So
  4. 4. Execution Code Application Environment
  5. 5. http://tinyurl.com/DevOps-Book