04/07/2018 Reply Xchange Milan - Cloud Automation Services - How to Automate Cloud Service Management

1. HOW TO AUTOMATE
CLOUD SERVICE
MANAGEMENT
Danilo Albino | COP Leader Cloud Automation Services | Storm Reply
Andrea Mercanti | Sr Cloud Solution Architect | Storm Reply

2. Big
Data
Connected
Devices
Machine/Deep
Learning
Artificial
Intelligence

3. from on-premise to Cloud from manual to Automated
CLOUD AUTOMATION

4. CLOUD AUTOMATION SERVICES
WHAT IS A CLOUD MANAGEMENT FRAMEWORK?
Cloud Management Framework
a set of integrated tools that provide functionalities for
the management of public, private and hybrid cloud environments
Fundamental functionalities include automation of:
 Provisioning and Orchestration of Resources
 Monitoring and Metering
 Multi-Cloud Brokering

5. CLOUD AUTOMATION SERVICES
HOW DO WE IMPLEMENT AUTOMATION?
 Methodologies (from DevOps to NoOps)
 Patterns (CI/CD/AD , Infrastructure as Code )
 Tools
multi-cloud applications management

6. CLOUD AUTOMATION TOOLS
THERE IS A PLENTY OF TOOLS AVAILABLE ON THE MARKET
The goal is to compose the most suitable set of tools to perform
Automated Cloud Services based on the chosen strategic approach
Configuration
tools
Automation
tools
Orchestration
tools
Repository
tools

7. METHODOLOGIES

8. DevOps is not a goal but a never-ending
process of continuous improvement
DEVOPS

9. DEVOPS
AUTOMATION AS A MANTRA
The mantra of DevOps culture is
to automate everything
Under DevOps there is a plethora of paradigms and technologies
 CI  Continuous Integration
 CD  Continuous Delivery
 AD  Automated Deployment
 IaC  Infrastructure as Code
 ASM  Automated Server Mgmt
 IS  Immutable Servers

11. The most powerful tool we have as
developers is Automation
NO-OPS

12. NO-OPS
NO-OPS != NO OPERATION
“No need for the developers to interact with ops team to get things
done, and less time spent actually doing ops tasks than developers
would spend explaining what needed to be done to someone else”
Adrian Cockcroft, Cloud Architect at Netflix
No-Ops means automation of:
 Deploymnet
 Monitoring
 Management

13. PATTERNS

14. Lower the barrier for making
frequent and large changes to infrastructures
INFRASTRUCTURE
AS CODE

15. INFRASTRUCTURE AS CODE
WHY
Infrastructure as Code is an approach to infrastructure automation based
on practices from software development
Managing infrastructures in completely new ways:
 Infrastructure can be provisioned in seconds
 Scale can be achieved without complicated capacity planning
 Interact with infrastructure by code

16. INFRASTRUCTURE AS CODE
GOALS
There are some specific goals that teams and organization wants to achieve
with Infrastructure as Code
 IT infrastructure supports and enables change
 Changes to the system are routine
 IT staff spends their time on valuable things, not on repetitive tasks
 Users are able to provision resources without needing IT team
 Teams are able to easily and quickly recover from failures
 Improvements are made continuously

17. INFRASTRUCTURE AS CODE
ISSUES
There are some problems that teams often see when they adopt dynamic
infrastructure and Infrastructure as Code
 Server Sprawl
 Configuration Drift
 Snowflake Servers
 Fragile Infrastructure
 Automation Fear

19. INFRASTRUCTURE AS CODE
PRINCIPLES
Principles to be follow to avoid problems
 Systems can be easily reproduced
 Systems are disposable
 Systems are consistent
 Processes are repeatable
 Design is always changing

20. INFRASTRUCTURE AS CODE
BEST PRACTICES
Best Practices come from application of principles identified for the Infrastructure as
Code
 Use definition files
 Self-Documented systems and processes
 Version all the things
 Continuously test systems and processes
 Small changes rather than batches

21. From the “Iron Age”
to the “Cloud Era”
AUTOMATED
SERVER MANAGEMENT

22. AUTOMATED SERVER MANAGEMENT
GOALS
Automated Server Management refers to the process of systematically handling
changes in a system in a way that it maintains its integrity over time
Managing server configuration in completely new ways:
 Servers are always in the desired state
 Servers provisioning and configuration are automated
 Interact with configuration with code

23. PRINCIPLES
There are some specific goals that organizations want to achieve with
Automated Server Management
These goals include:
 Quick provisioning of new servers
 No more snowflake servers
 Version Control for the server environment
 Replicated environments
AUTOMATED SERVER MANAGEMENT

24. In software, when something is painful,
the way to reduce the pain is to do it
more frequently, not less
CI/CD

25. DEVOPS
CONTINUOUS INTEGRATION
Continuous Integration is the practice of having the source code in a
centralized repository. This serves as a synchronization point, while
integrating the changes from multiple developers
 The development team should reply on an existing repository
 Define branch/tags/commits standard
 Configuration via scripts
 Closely connected to Continuous Delivery

26. DEVOPS
CONTINUOUS DELIVERY
Continuous Delivery is the approach of delivering package ready for
deployment in short cycles. It might include automated test and quality
gates.
 Based on automated delivery pipelines
 Triggered by the availability of a new version from CI
 Prepares a package ready for production deployment

27. DEVOPS
AUTOMATED DEPLOYMENT
Automated Deployment is the process of automatically deploying in
production the newest software release available from CI/CD
 Automatically trigger deployment in production
 Required strong CI/CD implementation
 No manual step involved
 Not for all companies and workloads
 Last step of automation

28. Treat your servers like cattle, not pets
IMMUTABLE
SERVERS

29. IMMUTABLE SERVERS
WHY
Immutable Servers is an approach to server configuration automation
based on reusable templates and artefacts
Managing servers configuration in completely new ways:
 Instead of maintaining a server, replace it with a new one
 Build static images, test it and store as artefacts
 Automate the whole delivery process

30. IMMUTABLE SERVERS
GOALS
There are some specific goals that organizations want to achieve with
Immutable Servers
These goals include:
 Fast deployment
 Repeatable tasks
 High failure tolerance
 Improved stability and testability
 Configuration versioning
 High level of security

31. IMMUTABLE SERVERS
PROBLEMS
There are some typical issues teams often see when they adopt dynamic
infrastructure and Immutable Servers
These problems include:
 Change of mindset is required
 Tooling is not mature
 Stateful workloads and management of local data

32. TOOLS

33. Power is nothing
without control

34. INFRASTRUCTURE AS CODE
TOOLS
Selection of Tool most used to implement the Infrastructure as Code paradigm
These tools include:
 Terraform
 AWS Cloudformation
 Open Stack Heat

35. AUTOMATED SERVER MANAGEMENT
TOOLS
Most common tools to implement the Automated Server Management paradigm
These tools include:
 Ansible
 Chef
 Puppet

36. CI/CD/AD
TOOLS
Most effective tools to implement the CI/CD/AD paradigm
These tools include:
 Jenkins
 Bamboo
 Spinnaker
 Travis CI

37. IMMUTABLE SERVERS
TOOLS
Main tools supporting the implementation of the Immutable Servers paradigm
These tools include:
 Packer
 Docker

38. CONCLUSIONS

39. REPLY PROPOSAL
CLOUD AUTOMATION FRAMEWORK
Reply’s Cloud Management Framework is being built on expertise,
templates and tools to implement an effective and flexible Cloud Automation
Platform for the fitting of specific customer needs
Reply‘s framework includes:
 Unified IaC tools templates and expertise
 Unified Automated Configuration templates and expertise
 Unified CI/CD tools and expertise

40. REPLY (NEXT) PROPOSAL
KUBERNETES AS A UNIFIED CLOUD SOLUTION

41. THANK YOU
#ReplyXchange
#LifeAtReply