Skip to main content

Systems Administration Koans [2008]

Some koans...

-----------

A sysadmin asked the Master,

"What's the best way to install a new system?"

The Master answered,

"Turn it on."

The sysadmin was enlightened.

-----------

A sysadmin asked the Master,

"What's the root password to this server?"

The Master asked,

"Do you have access to the console?"

The sysadmin replied,

"Yes."

The Master replied,

"The root password is whatever you want it to be."

The sysadmin was enlightened.

-----------

An sysadmin seeks approval from the Master:

"Master, I have designed and implemented a system with no single points of failure!"

The Master answered, "Have you documented it?"

"Not yet - I wanted to get it done first."

The Master asked, "Give me the name of a team member that can build another one without seeing you or contacting you."

"Well, I can't, yet - I just built it."

The Master answered, "Your system has at least one single point of failure."

The sysadmin was enlightened.

-----------

The Master called the two lead operational sysadmins into the office, asking,

"What is your daily routine?"

The first admin answered,

"First I check to see if my security patches went out, then I push out patches that failed to push the first time, then I ping all the systems to make sure they are up, then I go through the logs for each of my machines to check for issues, then I see if systems engineering has any updates, then I push those, as well; then - "

The Master cut the first admin short, asking the second, "What about you?"

"I have nothing to do," said the second.

The first admin was reprimanded, the second, given a raise.

-----------

The Master asked a junior administrator, "Tell me how your installation system works."

The junior administrator replied,

"First I boot from the network into the automated installation, then the automated post-installation, I wrote, runs, then any post-installation package updates run, then I configure the machine to get updates from my automatic update system. Then I deploy the machine."

The Master replied, "Why waste time on post-installation?"

The junior admin was enlightened.

-------------

The Master asked two junior admins how their weekend upgrades went.

The first related that he sent out his maintenance notice on time, scheduled downtime, and successfully completed every item on his process checklist within his downtime window. His clients were able to restart their applications within the downtime window with no issues. His successfully restored his services before the downtime window ended and sent his completion notice.

The second related that she had sent out her maintenance notice on time, completed every item on her process checklist within her window, and sent her completion notice.

The Masters asked, "You clients said they were not asked to restart their applications and emailed me asking if you actually did your upgrade. What happened?"

The second junior said, "I designed my process so that my services were never interrupted."

The first admin was reprimanded. The second, rewarded.

-------------

A junior admin once inquired of the Master.

"Master, what is the One True Text Editor for finding the One True Path?"

The Master admonished him.

"Your desire to find the One True Path will keep you from finding the One True Path. Go complete your work."

The junior admin was enlightened.

-------------

A Manager once said to the Master,

"I get 100s of resumes a week from people looking for jobs. You are all replaceable."

The Master replied,

"True. Given unlimited time and money, you can replace any employee."

-------------

(c) Adam Keck 2008. All rights reserved. (a0f29b982)

The above post is not licensed in any way.

Comments

  1. Koans Bookmarks...

    Remmrit.com user has just tagged your post as koans!...

    ReplyDelete

Post a Comment

Popular posts from this blog

PowerShell One-Liners

Introduction

PowerShell is Microsoft's shell for their product lines. It's now on version 3.0. If you miss the power of the command line while using Windows on either your laptop or servers, PowerShell provides that power.


Important concepts:
Almost all aspects of the Microsoft ecosystem are objects within an overarching structure. You query and manipulate this structure and its objects with PowerShell. This includes all aspects of SharePoint, Active Directory, and Exchange. Other companies, like VMware (see below) have also written PowerShell modules.This "object nature" means that PowerShell pipes pass objects and properties, not just text. Variables store data-structures of objects. 
One-liners

Note: Unwrap the code lines before you use them.

Get Help

Get the usage of the command "Select-Object":

Get-Help Select-Object

Built-in examples for the command "Select-Object":

Get-Help Select-Object -examples | more

Get the list of all commands and sort it:

Fixing SSH connection problems in EGit in Eclipse

Note: I posted a version of this on Stack Overflow. Errors can occur when there is an underlying SSH authentication issue, like having the wrong public key on the git remote server or if the git remote server changed its SSH host key. Often the an SSH error will appear as: "Invalid remote: origin: Invalid remote: origin"
Eclipse will use the .ssh directory you specify in Preferences -> General -> Network Connections -> SSH2 for its ssh configuration. Set it "{your default user directory}.ssh\" . To fix things, first you need to determine which ssh client you are using for Git. This is stored in the GIT_SSH environmental variable. Right-click on "Computer" (Windows 7), then choose Properties -> Advanced System Settings -> Environment Variables. If GIT_SSH contains a path to plink.exe, you are using the PuTTY stack. To get your public key, open PuTTYgen.exe and then load your private key file (*.ppk). The listed public key should match the pu…

How to fix this ssh error from a Cisco switch: ssh_rsa_verify: RSA modulus too small: 512 < minimum 768 bits

Problemssh user@cisco_switch returns:
ssh_rsa_verify: RSA modulus too small: 512 < minimum 768 bits key_verify failed for server_host_key Solution The modulus of the ssh RSA key pair on the switch is too small. If you have access, generate a new key pair on the switch with a larger modulus.
ProcedureLogin with ssh protocol version 1 (ssh space dash one): ssh -1 user@cisco_switch(On the switch): enable(On the switch): Authenticate to "Privileged Exec Mode" mode on the switch.(On the switch): conf t(On the switch): crypto key generate rsa general-keys modulus 1024(On the switch): Press enter to accept that the current key pair for the switch will be replaced. You now should be able to log into the switch with ssh protocol version 2.