Exciting news! Just got recognized as Most Valuable Blogger (MVB) By DZone.com. This is a very good sign for my ultimate goal: Be a DevOps Influencer.
Bash scripting is a must-have skill for DevOps. I used to be very very confident at bash. But when I first tried ShellCheck , I realized that I’m just too proud and arrogant.
ShellCheck is a powerful code analysis tool for bash scripts. Like Pylint for Python or Rubocop for Ruby. Give it a try! You’ll get surprised.
Ever bothered by suspicious processes running in your servers? No doubt how dangerous they might be: valuable data leaked, CPU/memory wasted, or DDoS attack other victims, etc.
How to easily capture those annoying troublemakers? Even better, get alerted without extra human effort.
While go cloud is a prevailing trend, security is something we can’t afford to ignore. People hate malicious access. Periodically check all widely open TCP Ports is one good practice to secure our system in cloud. Obviously DB ports can’t be exposed to the whole internet. Our internal REST API also need to be protected.
We should make sure firewall is properly configured. What’s more important, we need to be always on top of these security holes with minimum efforts. So let’s automate the audit process of insecure TCP Ports.
Sandbox indicates an isolated and autonomous play-yard, where anyone can do their own code build, deployment and debugging locally. It won’t effect anything outside. Ideally it should not be effected by outer world either. This is especially useful for new member on-board, daily development, QA cycle, etc.
How to get an easy and reliable sandbox for your projects? Check it out.
No doubt container is a breakthrough technology in DevOps world. How to effectively build and use docker image to speed up our deployment? This would be important to in both our development and release cycle. Here are some our experience and sharing. Check it out, buddy!
Occasionally DevOps code needs to check and wait status, before running further steps. For example, wait for service A to be up, then start service B; confirm TCP port is listening, then launch requests; etc.
For simplicity or time pressure, people usually use a blind wait like “sleep 10″ to fix this. This is certainly not good enough. How we can improve this with affordable cost?
After a lot of effort and communication, finally the system deployment works! To guarantee a smooth deployment anytime, we enforce daily deployment test as a next step.
Surprisingly daily deployment doesn’t always succeed like we expect, even if no major changes. More interesting, many failed tests are kinds of false negatives. So what are the obstacles? And how we can avoid them?
Like most people, I usually google, instead of reading books for technical learning. To get a deeper understanding and structured study for DevOps, I also find some extraordinary books. Worth Reading!