Reader small image

You're reading from  Practical Site Reliability Engineering

Product typeBook
Published inNov 2018
PublisherPackt
ISBN-139781788839563
Edition1st Edition
Right arrow
Authors (3):
Pethuru Raj Chelliah
Pethuru Raj Chelliah
author image
Pethuru Raj Chelliah

 Pethuru Raj Chelliah (PhD) works as the chief architect at the Site Reliability Engineering Center of Excellence, Reliance Jio Infocomm Ltd. (RJIL), Bangalore. Previously, he worked as a cloud infrastructure architect at the IBM Global Cloud Center of Excellence, IBM India, Bangalore, for four years. He also had an extended stint as a TOGAF-certified enterprise architecture consultant in Wipro Consulting services division and as a lead architect in the corporate research division of Robert Bosch, Bangalore. He has more than 17 years of IT industry experience.
Read more about Pethuru Raj Chelliah

Shreyash Naithani
Shreyash Naithani
author image
Shreyash Naithani

Shreyash Naithani is currently a site reliability engineer at Microsoft R&D. Prior to Microsoft, he worked with both start-ups and mid-level companies. He completed his PG Diploma from the Centre for Development of Advanced Computing, Bengaluru, India, and is a computer science graduate from Punjab Technical University, India. In a short span of time, he has had the opportunity to work as a DevOps engineer with Python/C#, and as a tools developer, site/service reliability engineer, and Unix system administrator. During his leisure time, he loves to travel and binge watch series.
Read more about Shreyash Naithani

Shailender Singh
Shailender Singh
author image
Shailender Singh

Shailender Singh is a principal site reliability engineer and a solution architect with around 11 year's IT experience who holds two master's degrees in IT and computer application. He has worked as a C developer on the Linux platform. He had exposure to almost all infrastructure technologies from hybrid to cloud-hosted environments. In the past, he has worked with companies including Mckinsey, HP, HCL, Revionics and Avalara and these days he tends to use AWS, K8s, Terraform, Packer, Jenkins, Ansible, and OpenShift.
Read more about Shailender Singh

View More author details
Right arrow

Chapter 4. DevOps as a Service

This chapter is going to cover various topics related to the DevOps world. We are going to look at DevOps in the context of Site Reliability Engineering (SRE), as automation and DevOps play an important role in this area. We will be integrating our system with monitoring solutions to collect various metrics to improve our services. This chapter will cover recent trends in this domain and give an idea about the expanding market of DaaS providers. We will also provide a brief introduction to various topics related to DaaS.

We are going to cover the following topics in this chapter. This should give us an idea about what exactly DevOps means to the agile world:

  • What is DaaS?
  • One-click deployments and rollback
  • Configuring automated alerts
  • Centralized log management
  • Infrastructure security
  • Continuous process and infrastructure development
  • Continuous integration and continuous development
  • Collaboration with development and QA teams

What is DaaS?


DevOps-as-a-Service (DaaS) is a service that allows you to get all the compilation, building, and Continuous Integration (CI)/Continuous Development (CD) tool chains setup instead of having to setup your own. DaaS can be provided by an internal team. In this case, the development team won't take any direct actions to manage its infrastructure; it will just feed its code to get compile, build, and CI/CD features. Alternatively, DaaS can be provided by external vendors, in a market that is expanding rapidly. These can help with your journey to achieve CI and CD.

In 2016, Gartner declared that 25% of 2,000 global companies that are surveyed will be using DevOps. However, this year, Forrester research has said that this will reach 50%. According to a study by cloud management provider RightScale,

the ratio of enterprises that have adopted some aspects of DevOps principles reached 84% in 2017

.

There are multiple websites that list all the major DaaS vendors. The following are among...

Collaboration with development and QA teams


As the name DevOps suggests, DevOps refers to a combination of development and operations teams who come together to complete a business project successfully. DevOps refers to the collaboration of teams that are involved in the development, delivery, and maintenance of a project to make it faster and more efficient in every dimension. Our main focus inDevOps is on the development and quality analysis teams. This is due to the CD and the delivery of new builds.

In today's competitive world, a new innovation or idea is hot property, that everyone wants to cash in on quickly. This need to deliver a new product rapidly leads to an additional load on developers to create new features that need to be optimal in every sense. This may lead the code to break, causing the entire application to shut down. A faulty deployment, in turn, may cause the application's configuration to break, which may be non-recoverable.

The role of developers in DevOps

Developers...

Summary


DevOps as a service is an emerging philosophy in application development. There's not one path to setup DevOps as a service. It varies from organization to organization, and you need to decide what works in your organization. Many organizations adapt DaaS to manage their application to the cloud. By using DevOps as a service, we can automate build, test, and deploy processes. We can achieve this by implementing effective CI and CD process. In this chapter, we have learned how to setup one-click deployment and rollback using the Jenkins tool. Throughout this book, we have been focusing on microservices, and we have seen how to collect and send automatic monitoring alerts. We learned how to setup Jenkins and GitHub to achieve CI and deployment end to end. This is going to help us improve the engineering pipeline and improve the delivery process. We have also discussed collaboration between development and QA teams.

We can conclude that the DevOps life cycle contains development, testing...

lock icon
The rest of the chapter is locked
You have been reading a chapter from
Practical Site Reliability Engineering
Published in: Nov 2018Publisher: PacktISBN-13: 9781788839563
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
undefined
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime

Authors (3)

author image
Pethuru Raj Chelliah

 Pethuru Raj Chelliah (PhD) works as the chief architect at the Site Reliability Engineering Center of Excellence, Reliance Jio Infocomm Ltd. (RJIL), Bangalore. Previously, he worked as a cloud infrastructure architect at the IBM Global Cloud Center of Excellence, IBM India, Bangalore, for four years. He also had an extended stint as a TOGAF-certified enterprise architecture consultant in Wipro Consulting services division and as a lead architect in the corporate research division of Robert Bosch, Bangalore. He has more than 17 years of IT industry experience.
Read more about Pethuru Raj Chelliah

author image
Shreyash Naithani

Shreyash Naithani is currently a site reliability engineer at Microsoft R&D. Prior to Microsoft, he worked with both start-ups and mid-level companies. He completed his PG Diploma from the Centre for Development of Advanced Computing, Bengaluru, India, and is a computer science graduate from Punjab Technical University, India. In a short span of time, he has had the opportunity to work as a DevOps engineer with Python/C#, and as a tools developer, site/service reliability engineer, and Unix system administrator. During his leisure time, he loves to travel and binge watch series.
Read more about Shreyash Naithani

author image
Shailender Singh

Shailender Singh is a principal site reliability engineer and a solution architect with around 11 year's IT experience who holds two master's degrees in IT and computer application. He has worked as a C developer on the Linux platform. He had exposure to almost all infrastructure technologies from hybrid to cloud-hosted environments. In the past, he has worked with companies including Mckinsey, HP, HCL, Revionics and Avalara and these days he tends to use AWS, K8s, Terraform, Packer, Jenkins, Ansible, and OpenShift.
Read more about Shailender Singh