A reflection on how we migrated from an era of production deployments once a week to more than 10 deployments a day. The story of transforming a mere sys-admin to super sophisticated DevOps team, armed with multiple tools, scripts and plugins for achieving automations, accuracy and invincible agility. As we continue on our endeavor for further improvisation, I believe its worth sharing the experience with community. Tentative topics outline:
1.Arming teams for their transformation to DevOps from mere sys-admins.
2.Killing manual deployments (manual deployment->capistrano->webistrano)
3.Automation (for daily backups,monitoring applications and servers deploying dependencies)
4.Saving up time on setting up new instances(using golden image).
5.Using LDAP to maintain servers with public key(avoiding individual logins to every server makes it less messy)
6.Using Puppet for instantiating multiple servers at once.
7.Commissioning our own Cloud Infrastructure.
3. •
•
•
•
•
•
A Weboniser and Rubyist
A Blogger(vparihar01.github.com)
A Geek
DevOps Guy
An Aspiring Tech Innovator
Tweet with @vparihar
4. With the new born startup and freshly
out of college grad’s, everything we did
was an experiment.
Deployments and relevant techniques
were completely alien with no
experience on how to deal with our first
application going live.
6. •
•
•
Doing every task manually on the
server for each deployment - Not
again...
Database migrations and rolling back
is such a headache.
We need versions for our deployments!
13. “Put this Code Live, here’s a tarball” NOW!
•
•
•
•
•
•
•
What dependencies ?
No machines available ?
What database ?
Security ?
High Availability ?
Scalability ?
My computer can’t install this!
27. We were spending around
1-1.5 lac/month for our Test
and Stage Servers
28. Why not our own Private Cloud ??
So, we went ahead and bought our own servers
and migrated all test and stage instances to our
own in-house private cloud.