Top 5 Questions to Ask When Buying Public Cloud IaaS
Tuesday, December 20, 2011 by Jon Corwin
Public Cloud Infrastructure as a Service (IaaS) is transforming the hosting industry. Traditional hosting companies and fresh service provider faces both play an active role in this emerging market. IaaS offerings taut agility for early adopters, while slower moving enterprises—still managing their own cloud—watch from the sidelines. Ever expanding datacenters, operational responsibilities and security requirements, amidst shrinking IT budgets, means traditional infrastructure often only makes sense for the largest of organizations.

Despite Public Cloud IaaS still solidifying a market foothold, some 65 percent of enterprises are already adopting IaaS and PaaS (Platform) services, according to a recent F5 Networks survey. So, what is IaaS? Infrastructure as a Service is a provision model in which an organization outsources the equipment used to support operations, including storage, hardware, servers and networking components (via SearchCloudComputing). The service provider owns the equipment and is responsible for housing, running and maintaining it. The client typically pays on a per-use basis. Common IaaS use cases include the ability to expand and contract as needed, pay-as-you-go billing, backups, disaster recovery, patching, antivirus and security compliance.
Here are five questions you should answer before deciding on an IaaS service provider (this is a shortened version of Jeff Vance's original IaaS Buying Guide):
  1. Is the IaaS model right for you, or are you  better off with PaaS, SaaS or other cloud models?
    Disseminating IaaS from PaaS and SaaS is simplest to understand using the cloud stack model. IaaS includes all datacenter and network plumbing and service and storage hardware. A virtualization layer on top encases the IaaS offering. PaaS handles the next two layers of the stack; operating systems and infrastructure software. Finally, SaaS delivers hosted applications, ranging from personal email to full blown CRM systems. Leveraging the on-demand nature of these mdoels requires that an organization understand how they intend to develop and deploy applications. IT agility and autonomy beckons an IaaS structure.
  2. Will implementing IaaS require additional IT resources?
    Adjusting from a static on-premise datacenter to a dynamic IaaS model can be a tremendous shift for enterprise IT organizations. IaaS solution providers also vary in their delivery of managed services. Providers like Bluelock offer managed services traditionally handled by internal IT to streamline operational tasks. This allows organizations to focus on their core business, not running their business. Examples of Bluelock managed services include operating system patching, load balancing, virtual machine backup and antivirus. The ease of IT operations inherent in IaaS solutions makes cloud particularly attractive to nimble startups with limited resources. Cloud investment and resources can scale with fluctuating businesses.
  3. How easy is it to scale up (or down) your services?
    A key characteristic of cloud computing is scalability, or more precisely the ease with which scalability can be achieved. IaaS enables scalability through dynamic provisioning of resources on a self-service basis to meet business demands. While easy cloud offering takes a different approach to scaling parameters, all IaaS models are far more flexible than traditional one-app-per-service computing.
    A good illustration of IaaS scalability existed when Lehman Brothers Holdings Inc (LMHI) filed for Chapter 11 bankruptcy in 2008. Amist the sell off of business divisions, LMHI was left without the technology assets necessary to support the wind-down of the company. Lehmann formed an asset manager business, LAMCO. Tasked with building infrastructure able to assume peek capacity day one and slowly wind down over time, cloud computing was the logical choice. LAMCO selected Bluelock’s VMware-based Virtual Datacenters due in large part to its flexible scaling capabilities.
  4. Does the IaaS provide adequate support?
    The ability to quickly and accurately diagnose and resolve issues with infrastructure not only ensures reduced downtime, but keeps one issue from threatening an entire network. Dedicated support teams ensure enterprise IT and infrastructure keep pace with your business. Keep in mind, select vendor’s customer service is not offered 24/7 or is only available at an additional cost.
    Transitioning to the cloud is no small task. A staff of cloud experts at your disposal for guidance and support may help organizations new to the cloud. Bluelock has a proven track record in providing scalability and client support.
  5. What is your plan for outages?
    Outages are a problem for any computing model. On-premise datacenters are especially susceptible to outages. Designing for failure should be obvious, but each cloud providers approach to blackouts varies. For example, Bluelock offers 99.99% uptime in the cloud because our clients are enterprise-level companies with mission-critical production environment needs. You likely can’t afford the downtime that would be threatened with a provider who can only promise 99.9% or 99.95% uptime.

My Top Ten Favorite Blog Posts
Tuesday, November 3, 2009 by Alicia Gaba
Just last week I wrote a post on the top ten most viewed blog posts from the BlueLock Blog.  Granted, they were all great blog posts, but it didn’t really give me the ability to post my favorites.  Here is a list of my all-time favorite blog posts from the BlueLock Blog.  Let me know if I missed your favorite!

1.    Cloud Computing – a five-layer model 
2.    Going green in your data center 
3.    Seven things you should know about cloud computing
4.    Fuzzy math in the cloud – TCO of cloud vs. internal IT
5.    Your infrastructure choices: a cloud is not a cloud is not a cloud 
6.    Why cloud computing makes perfect sense
7.    Marian College catapults their IT infrastructure with a private cloud from BlueLock
8.    My favorite virtualization myths
9.    What is cloud computing – beyond the buzzwords
10.  What’s emerging in cloud computing


BlueLock Blog: All-Time Top Ten Viewed Blog Posts
Monday, October 26, 2009 by Alicia Gaba
The BlueLock Blog has been alive and breathing for about a year now, which is why I felt it necessary to look back and review those posts that have time and time again proven themselves as leaders, just like BlueLock has. 

Take a look and enjoy the all-time top ten viewed posts from the BlueLock Blog.

1. Virtualization is not for Amateurs
2. Cloud Computing - A Five-Layer Model
3. What's the Difference Between Cloud Computing and Virtualization?
4. Vocabulary of the Cloud
5. More on the Economics of Cloud Computing
6. Rackspace: Scoble Hiring
7. BlueLock vCloud Express has Officially Launched
8. Key Differences between Amazon EC2 and VMware vCloud Express
9. Virtualization Overtakes Traditional Data Centers and Creates Demand for Support
10. Private, Public or Hybrid - What is the Best Cloud Computing Alternative?
Cloud Computing – A Five Layer Model
Tuesday, February 3, 2009 by Brian Wolff

When someone talks about Cloud Computing, what exactly are they talking about? 

As more functionality moves to the internet cloud every provider and user is developing their own defintion.   Industry experts and researchers are struggling to formulate a standard set of terms to describe all the different functions.  This graphic developed by Lamia Youseff, University of California, Santa Barbara and Maria Butrico, Dilma Da Silva, IBM T.J. Watson Research Center depicts as five layers, with three constituents to the cloud infrastructure layer. The figure represents the inter-dependency between the different layers in the cloud.
 

 

They define the five levels as follows: 

A. Cloud Application Layer –The most visible layer to the end-users of the cloud. Normally, the users access the services provided by this layer through web-portals, and are sometimes required to pay fees to use them.

B. Cloud Software Environment Layer - The second layer in our proposed cloud ontology is the cloud software environment layer (also dubbed the software platform layer). The users of this layer are cloud applications’ developers, implementing their applications for and deploying them on the cloud.

C. Cloud Software Infrastructure Layer - The cloud software infrastructure layer provides fundamental resources to other higher-level layers. Cloud services offered in this layer can be categorized into: computational resources, data storage, and communications.

D. Software Kernel - This cloud layer provides the basic software management for the physical servers that compose the cloud. Software kernels at this level can be implemented as an OS kernel, hypervisor, and virtual machine monitor and/or clustering middleware.

E. Hardware and Firmware - The bottom layer of the cloud stack in our proposed ontology is the actual physical hardware and switches that form the backbone of the cloud. In this regard, users of this layer of the cloud are normally big enterprises with huge IT requirements in need of subleasing Hardware as a Service (HaaS).

Are these really five different levels.  Is there much difference between Infrastructure and Hardware?  Or are the two merging as the technology continues to evolve?