2. Amazon’s web infrastructure guru James Hamilton uses Facebook’s recently
released energy data to make an educated guess for how many servers
Facebook now has: potentially 180,000. That’s up from an estimated 30,000
in the winter of 2009, and 60,000 by the Summer of 2010.
google has more than one million servers
10 releases per day!
● 3 engineers
● over 14 million users
● no hardware
● +100 instances on Amazon EC2
3. - competition - Reduce Time to Market
- Increasing users and traffic.
- Huge amount of servers on cloud.
- Zero downtime.
- Huge data
- Cost!
More Servers, More Releases, More Data!
4. Need of the hour!
FASTER, EFFICIENT, ERROR-FREE,
AUTOMATED DELIVERY OF
SOFTWARE
16. Build pipelines
t makes every part of the process of building, deploying, testing, and releasing software visible to everybody involved, aiding collaboration.
Increases visibility of each step.
Early feedback.
Automate deploy and release any version to any
environment.
19. Configuration Management
● How soon can you write this script?
● How maintainable is it?
● Can you write test cases for it?
● Can you have versioning?
● Can you have reusability?
● Risk????
● Idempotency
20.
21. Infrastructure as code
Evolving from Scripts to code
"a flexible model for reuse by enabling users to model
infrastructure as code to easily and consistently configure
and deploy infrastructure across any platform.
Create a blueprint of your infrastructure that enables you to
build or rebuild, automatically in minutes or hours – not
weeks or months."
23. What is Chef?
Chef is a configuration management tool.
Using its cookbooks and recipes we can
provisions VMs, environments.
Community maintained code, almost everything
is prebuilt (cookbooks and recipes), need not
reinvent the wheel, just modify as per the need.
24. Cloud Support : EC2
$ knife ec2 server create "role[Demo] -N "demo.example.
net" -i ami -3e02f257
31. The Ops World
IT buying
Installation of server hardware and OS
Configuration of servers, networks, storage, etc…
Monitoring of servers
Respond to outages
IT security
Managing phone systems, network
Change control
Backup and disaster recovery planning
Manage active directory
Asset tracking
34. its a culture... its a movement..
Started as devOps days in Belgium in 2009.
Developers interested in cloud, clusters, servers,
deployments, databases learn to write code to maintain
them.
Ops people evolve and start developing the code to
maintain infrastructure.
35. Collaboration -> Best practices
Ops learn from developers - > Coding
principles,
managed code, versioning.
Dev learn from Ops -> Insights of environment
and deployments, their problems.
