A friend forwarded the news that Bill Loeffler passed away from melanoma this month at the age of 54.

The friend asked if I knew Bill, and yes I had many conversations on the concept of Infrastructure Patterns for IT in my Microsoft days. Bill and I connected on LinkedIn 5 years ago, but he was based in NYC, so it didn’t seem convenient to chat about his work and mine.

Bill has posted some good content on building a Cloud Infrastructure.

http://social.technet.microsoft.com/wiki/contents/articles/5711.private-cloud-infrastructure-as-a-service-self-service.aspx

Private Cloud Infrastructure as a Service Self Service

Self Service capability is a characteristic of private cloud computing and must be present in any implementation. The intent is to permit users to approach a self-service capability and be presented with options available for provisioning in an organization. The capability may be basic provisioning of a virtual machine with a pre-defined configuration or may be more advanced allowing configuration options to the base configuration and leading up to a platform capability or service.

http://social.technet.microsoft.com/wiki/contents/articles/4633.what-is-infrastructure-as-a-service.aspx

What is Infrastructure as a Service?

In defining Infrastructure as a Service (IaaS), we need to drill into specific characteristics that a cloud platform provider must provide to be considered Infrastructure as a Service. This has been no easy task as nearly every cloud platform provider has recently promoted features and services designed to address the IaaS and cloud computing market. Fortunately, as the technology has evolved, a definition of cloud computing has emerged from the National Institute of Standards and Technology (NIST) that is composed of five essential characteristics, three service models, and four deployment models.

I looked up some of our shared connections on LinkedIn and I should set some time aside to chat about Bill.