This document discusses using Ansible for infrastructure automation. It provides examples of how Ansible can be used for provisioning infrastructure, configuring servers, patching, backups, cluster deployment, and scaling. It also gives three use cases: creating a platform for a client, integrating Ansible with other tools like vRA and CyberArk, and automating a two year project involving RedHat and Windows systems. It concludes by discussing common problems providing "DevOps as a service" and introducing Crevise PowerOps to address these.

1. Automating using Ansible
By Alok Patra and Paresh Patil

2. Why Ansible ?
● Opensource
● Agentless
● Easy to read and write - yaml based
● Ready made modules available
● Readily available roles (Ansible Galaxy)
● Easy to install

3. Ansible Use Cases
● Infra Provisioning
● Server Configuration
● Patching
● Backups
○ Tools
○ Databases
○ Configs
○ AMI’s
● Cluster Deployment
● Scaling

4. Client 1 Use Case

5. Client 1 Use Case
● Platform creation for client

6. Abstraction of Technical Details
● User Input
○ Cloud Provider
○ Region
○ Cluster Size (S / M / L / XL / XXL)
○ Tools
○ Database

7. Infrastructure Provisioning
● IAM roles
● VPC
● Networking
● Key pairs
● Instances
● Elastic IP
● S3 Buckets

8. Server Hardening

9. User Creation
● Admin
● Service Account
● Non-root

10. Server
Configuration
Cluster
Application Database

11. Cluster
● Kubernetes Cluster
deployment using
Kubespray
● Adding Nodes to the
cluster

12. Application
● Web Server (Apache / Nginx)
● Redis
● Jenkins + Jenkins Plugins
● Application Database Backup to S3 Bucket
● Application Config Backup to S3 Bucket

13. Database
● Mongodb
● MySQL
● Postgres
● DB User Creation
● DB Database Backup

14. The BORING monotonous tasks
● Installing Packages
● AMI Creation
● Adding or removing volumes to instance
● Vulnerability Assessment
● Patching
● Password Rotation
● Add new config to web server

15. Ad Hoc Tasks
● User management
○ Add user
○ Privilege management
○ Delete user
○ Update user password
○ Add or update user groups
● Gitlab
○ Project management
○ Gitlab user management
○ Access management

16. Client 2 Use Case

17. Client 2 Use Case
● vRA → vRO → Ansible Tower → Ansible
● Input Validation
○ Validate Datatypes
○ Validate value of variables
● Integration with CyberArk
● Integration with SAP Hana
○ Log onto DB, archive and wipe file and email report
● Dynamically enable/disable logging for Passwords
● Custom config file
● Ansible Tower Setup

18. Client 3 Use Case

19. Client 3 Use Case
● 2 year engagement
● One of RedHat’s most successful projects in APAC
● Automation with RHEl and Windows
● OS hardening
● Install and configure MSSQL multi-node cluster
● Integrated workflow with Cloudform

20. Other Use Cases

21. Other Use Cases
54321 6

22. Our Accelerator - PowerOps
Common problems while providing “DevOps as a Service”
1. Dependency on good devops engineers
2. Simple CI/CD setup takes a long time
3. Custom implementation and automation
Crevise PowerOps:
- Eliminate people dependency
- Faster and smoother CI CD implementation
● - Multi platform and multi tool integration

23. Thank You
● Paresh Patil
○ Email ID: paresh.patil@crevise.com
○ Contact No: +91-8554909992
● Alok Patra
○ Email ID: alok.patra@crevise.com
○ Contact No: +91-9545059374
Crevise Technologies Pvt Ltd
Website: https://www.crevise.com/
Email ID: hr@crevise.com