DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. DevOps and CI/CD
  4. DevOps Protocol: No Manual Changes

DevOps Protocol: No Manual Changes

[deleted] user avatar by
[deleted]
·
Nov. 07, 12 · Interview
Like (0)
Save
Tweet
Share
11.02K Views

Join the DZone community and get the full member experience.

Join For Free

 You’ve heard about Devops and you like the idea. But how can you grow a Devops culture in your organization? In my series about Devops Protocols I talk about the fundamental building blocks for growing a Devops culture.
No Manual Changes refers to the behavioural trait of not messing with any productive systems. Let’s discuss why messing with production systems is bad and what to do about it.

Manual Changes Lead to Configuration Drift

You know how this goes: Your servers are under heavy load and you just want to kick up the number of worker processes a bit. You ssh into the first server and just start a bunch of additional workers. Now you sit back and see whether the box is behaving as expected. You find that all is fine and make a mental note that you need to persist your change in the startup script of your service and you need to roll out that change to all other servers. But your mental note is quickly forgotten because another urgent issue demands your full attention…
You end up with one server configured differently from the rest of the bunch. Even worse, your configuration is not even restart safe. As soon as anyone starts an automated configuration run or restarts the box your changes are gone. In our example case this might lead to the box crashing under load without anyone understanding why.

Automate All Changes

The way to go is obvious. Change the number of worker processes in your configuration management tool and let it reconfigure the box for you. This approach makes sure that your changes survive restarts and configuration runs. And it makes sure that your teammates see what you’ve done if any problems arise. Even your developers are now able to see that their code might need optimizations because it requires so many worker processes to run (way more than they initially expected).
Congratulations, you’ve made one more step toward Devops collaboration!

No Rule Without Any Exception – Really?

You might argue that my example is a bad one. If your production systems are in trouble, there’s no time to lose in going the extra mile of automation. Jump in and fight the fire!
While this approach might look reasonable at first glance, it is a very dangerous one. Especially when in fire fighting mode, you might not remember all the changes made to your production system. You think your problems solved but in reality they’ll come back worse than ever (and sooner then you expect).
You need to prepare in advance to avoid the need to go in and hot fix. Setup log monitoring services like splunk or graylog2 to be able to analyze what is happening. And you should have your configuration management tool (like Puppet or Chef) setup so that you can try out possible solutions without having to go in and do it manually.

How do you avoid manual changes to your production systems? Do you “electrify the fence” as described in the Visible Ops Handbook? Please let us know in the comments!




DevOps Protocol (object-oriented programming)

Published at DZone with permission of [deleted], DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Promises, Thenables, and Lazy-Evaluation: What, Why, How
  • Core Machine Learning Metrics
  • Public Cloud-to-Cloud Repatriation Trend
  • Last Chance To Take the DZone 2023 DevOps Survey and Win $250! [Closes on 1/25 at 8 AM]

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: