I’m getting ready to start installing RHEL7 at home. One of the biggest changes is the infrastructure that used to maintain the services (daemon processes) is not rolled into an architecture called “systemD”. Here is a cheat sheet to help deal with the change over
SystemD Cheat Sheet
systemctl Cheat Sheet
I thought I’d add this article on systemd
“The battle over systemd exposes a fundamental gap between the old Unix guard and a new guard of Linux developers and admins”
I’m probably considered an “Old Guard UNIX” guy, and I’m not crazy about the fundamental design of systemd, but I’m smart enough to realize that things change, and if you don’t change with them, you become irrelevant.
DevOps is the blending of tasks performed by a company’s application development and systems operations teams.
The term DevOps is being used in several ways. In its most broad meaning, DevOps is a philosophy or cultural approach that promotes better communication between the two teams as more elements of operations become programmable. In its most narrow interpretation, DevOp is a job description for an employee who possesses the skills to work as a both a developer and a systems engineer. In some industries, the term is also being used to describe a moderator between the two groups who functions as a type of scrum master to help developers and operations teams keep application lifecycle management (ALM) top-of-mind.
Back on July 27th I blogged about beginning to learn the Python language for software development. Here is an update. I’m nearly complete with my Python course on Udemy.com and I’ve started actual work with Python.
So, here’s where I’m at.
I got close to completing the on-line course, but decided to really dive in and start working with it, in favor of going back and finishing the course later on. I have every intention of finishing it, but I wanted to have a little experience first so that I could know what sections I really want to concentrate on. Like most software developers, I tend to reuse code all the time. As a long time Perl programmer, I always had my standard “go-to” functions and libraries, that I’d either import or “cut and paste” pieces of into new code. So, to get into the swing of things, I’ve now written functions to update a MySQL database, send email alerts, parse the output of UNIX commands, do CGI form handling, sys logging, find network errors/dropped packets, automate ssh connections, send pings, etc.
I’m a long way from becoming an expert, and it’s not nearly as second nature as some of the other languages I know, but I’m happy that I’m getting used to the syntax and that I’m starting to do some useful things with it.
Counting down to [SysAdmin Day](http://sysadminday.com/about-sysadmin-day/when-is-sysadmin-day/)
This was taken at the local library. They have a baby program - today was a sing-a-long!
I know that in the past I have flirted with learning Python development, but I really couldn’t think of a reason why I should put the time in to learn it. I have been using Perl since the 1990’s and Perl and Python appear to do the same things. I couldn’t see what I could accomplish in Python that I couldn’t already accomplish in Perl. I didn’t have anything against Python, but just never really found a compelling reason to start learning it… that is until now. Python has just surpassed Java as the teaching language of choice for most universities. While I love Perl programming, I’m smart enough to know that in just a few years, Python will be as wide spread as Java is today. To keep ahead of the curve and keep myself marketable I’ve finally decided to put an honest effort in learning Python. To help, I’ve enrolled in a course at The Ultimate Python Programming Course. I’m up to the 9th lesson so far and I’m finding the course REALLY helpful.
I’ll keep you posted to my progress here, and I’ll start uploading some sample code too!