The document details a cloud-based continuous delivery implementation presented by Pavel Chunyayev, covering techniques such as on-demand VM provisioning using VMware vSphere, environment configuration with Puppet, and lifecycle control through Jenkins. Key challenges addressed include automating environment setups, managing software releases, and optimizing test configurations across various platforms. The solutions discussed emphasize automation, visibility, and time savings in software deployment practices.

1. A Cloud Based Continuous
Delivery Implementation
Pavel Chunyayev
Amsterdam, 22-04-2015

2. Continuous Delivery in 2015
Development
• Commit
• Merge
• Trigger pipeline
Build
• Create artifact
• Assign version
Testing
• Journey across environments
• Quality criteria
Production
• Canary deployment
• Release != deployment

3. Continuous Delivery in 2015
Development
• Commit
• Merge
• Trigger pipeline
Build
• Create artifact
• Assign version
Infrastructure
• Infrastructure as a code
• Automated
• On-demand
Testing
• Journey across
environments
• Quality criteria
Production
• Canary deployment
• Release != deployment

4. Declarative vs Imperative
Declarative
• I want this server in this state
Imperative
• I want you to apply this sequence of actions

5. Mutable (reusable) vs Immutable (disposable)
Reusable
• I want to use the same server during the life of the project.
Immutable
• I want to provision a new server when I need to change something.

6. Configuration Management tools
Declarative
Imperative
Mutable Immutable
#!/bin/bash

7. Case 1
Declarative
Imperative
Mutable Immutable

8. Case 1
Challenges
• Projects require environments to be created
• A lot of environments are similar
• Takes time for admins to provision and configure them

9. Private cloud enables automation
What we did
• VMware vSphere to provide on-demand VMs
• Puppet to configure environments
• Hiera to separate data from the code
• Jenkins to control the lifecycle
Continuous Delivery
• Huge time savings and code reuse
• Developers are enabled to create configurations
• Deployments are scripted
Apache
New
server
Java
Zabbix
agent
MySQL

10. Declarative
Imperative
Mutable Immutable

11. Case 2
Declarative
Imperative
Mutable Immutable

12. Case 2
Challenges
• Control the state of the environments
• Release new versions of applications safely
• Automate the procedures to save time

13. Case 2
What we did
• Puppet to control the state of the servers
• Package artifact and assign version
• Deploy specific version to specific environment
• Rebuild the whole environment on deploy
Continuous Delivery
• Visibility
• Repeatable process
• Scripted deployments
Production
1.3-127
Staging
1.3-140
Testing
1.3-156

14. Declarative
Imperative
Mutable Immutable

15. Case 3
Declarative
Imperative
Mutable Immutable

16. Case 3
Challenge
• Software needs to be tested in different configurations
• Test environments are multi-server
• Environments take days to provision manually

17. Environments as a service
Solution
• Amazon Web Services to provision infrastructure
• Ansible to create procedures for each configuration
• REST API service to coordinate requests
Continuous Delivery
• Ready for both human and robots
• 20 minutes to create any environment
• Reduced feedback time
REST API
Ansible

18. Environments as a service
Declarative
Imperative
Mutable Immutable

19. Configuration Management Review
Declarative
Imperative
Mutable Immutable

20. Key takeaways
• Optimize for Continuous Delivery
• Automate infrastructure
pavel@levi9.com
@PavelChunyayev
Any questions?