Skip to main content

2008 Year End Summary

It’s been almost a year since I started blogging. Sam Buchanan, who has been blogging since 2001, tried to get me started a couple times years ago, but I didn’t really think I had anything to write about, or maybe I thought that nobody would read what I wrote, or maybe I wouldn’t admit that I didn’t really know what  blog was, so I never started. My boss finally convinced me to start writing, and this blog is the result. I’m probably late to the party, as the trend seems to be shifted toward micro-blogs or Tweets. I’m a fan of well written, original thoughts in the longer blog format though, so that’s what I’ve tried to present here on this blog.
Here’s a short summary of the interesting posts from the first year.

Security related posts include a post on protecting yourself from your own applications.  It’s a concept that we’ve used for years that unbeknownst to me is closely related to Biba and BLP. Hopefully I’ve recorded the essence. I also wrote some thoughts on de-provisioning as related to security, and a bit on the recent shift toward applications as the target of Internet hacks. 

System management posts include thoughts on minimally configuring systems, on ad hoc versus structured system management, and a proof of concept that we did a few years ago on self provisioning servers. I got thoroughly annoyed by the bloggers who ranted on about ISP’s that didn’t patch their DNS’s overnight, making no allowance for a reasonable test/QA cycle, so I wrote some thoughts on rapid patching versus availability.

Availability posts outlined essential transitions to higher availability, touched MTTR and MTBF and availability when humans are included, and availability versus complexity. I also wrote a series of posts on estimating the availability of redundant and non-redundant systems. (The availability related posts seem to catch more search engine referrals than anything else on the blog).

Other possibly interesting posts might be the one on scaling our on-line instructional management system to over 14 million page views per day. For some people, that’s a small system. For us, it’s our largest application by far, touching almost all students and faculty in the state. We also started calculating the rough cost of running certain database queries and feeding the data back to the application developers, figuring that optimization effort should be tied somehow to operational costs.

Non-nerdy posts include a couple posts on energy use for wall warts and game consoles, a couple posts on privacy in a security camera and database infested world, and my initial post and a follow up post on my annoyance at having to be tethered to a bulky computer or notebook.
And finally, a nostalgia post generated a bit of interest among the been-around-the-block readers.

It’s been interesting.

Michael Janke

Popular posts from this blog

Cargo Cult System Administration

“imitate the superficial exterior of a process or system without having any understanding of the underlying substance” --Wikipedia During and after WWII, some native south pacific islanders erroneously associated the presence of war related technology with the delivery of highly desirable cargo. When the war ended and the cargo stopped showing up, they built crude facsimiles of runways, control towers, and airplanes in the belief that the presence of war technology caused the delivery of desirable cargo. From our point of view, it looks pretty amusing to see people build fake airplanes, runways and control towers  and wait for cargo to fall from the sky.The question is, how amusing are we?We have cargo cult science[1], cargo cult management[2], cargo cult programming[3], how about cargo cult system management?Here’s some common system administration failures that might be ‘cargo cult’:Failing to understand the difference between necessary and sufficient. A daily backup is necessary, b…

Ad-Hoc Verses Structured System Management

Structured system management is a concept that covers the fundamentals of building, securing, deploying, monitoring, logging, alerting, and documenting networks, servers and applications. Structured system management implies that you have those fundamentals in place, you execute them consistently, and you know all cases where you are inconsistent. The converse of structured system management is what I call ad hoc system management, where every system has it own plan, undocumented and inconsistent, and you don't know how inconsistent they are, because you've never looked.

In previous posts (here and here) I implied that structured system management was an integral part of improving system availability. Having inherited several platforms that had, at best, ad hoc system management, and having moved the platforms to something resembling structured system management, I've concluded that implementing basic structure around system management will be the best and fastest path to …

The Cloud – Provider Failure Modes

In The Cloud - Outsourcing Moved up the Stack[1] I compared the outsourcing that we do routinely (wide area networks) with the outsourcing of the higher layers of the application stack (processor, memory, storage). Conceptually they are similar:
In both cases you’ve entrusted your bits to someone else, you’ve shared physical and logical resources with others, you’ve disassociated physical devices (circuits or servers) from logical devices (virtual circuits, virtual severs), and in exchange for what is hopefully better, faster, cheaper service, you give up visibility, manageability and control to a provider. There are differences though. In the case of networking, your cloud provider is only entrusted with your bits for the time it takes for those bits to cross the providers network, and the loss of a few bits is not catastrophic. For providers of higher layer services, the bits are entrusted to the provider for the life of the bits, and the loss of a few bits is a major problem. The…