Cloud File System

Hybridizing DR for the Cloud: Concerns

by dave on March 2, 2009


Over at Information Playground, Steve Todd has started down the path of no return: private clouds.  (Incidentally, I find it quite ironic that private clouds are no more private than public clouds in that they’re essentially run on the same infrastructure and face the exact same challenges for security, data mobility, and perminence that the aforementioned public clouds do…but, I digress) In his posting from last week, he details some of the challenges in looking at replication to the cloud (whether public or private is a mere stroke of the pen difference).  The good news is: he’s not alone in thinking this way. The bad news: well, we’ll get to that.  Let’s begin…

[click to continue…]

Share

{ 0 comments }

Private Clouds & Storage: Considerations

by dave on February 13, 2009


One of the current “hot” topics within the IT industry these days is the concept of cloud computing.  While there is a level of ambiguity around what cloud computing actually is, there is a definite trend towards looking at what these cloud services and storage can do for the commercial and enterprise.

Private Cloud Challenges

In a previous posting, I talked about the concept of a common cloud file system or cFS.  Some folks responded on Twitter that perhaps IBM‘s GPFS filesystem (as a part of their SOFS strategy) could indeed fulfill that role for the cloud.  As an additional twist, PaaS “connectors” such as SnapLogic, et. al. that seek to tie front-end processes or applications to underlying cloud services could simply provide a API hook to entities like Nirvanix, GoGrid, Amazon S3, etc. for handling discrete storage functions (with the obvious implications of data access/protection SLAs being separate and distinct from the middleware providers).  The provision for this changes when you start talking about privatizing the cloud.

[click to continue…]

Share

{ 3 comments }


In Part 3a of the Cloud Optimized Storage Solution series, I covered the concept of data tiering within the COSS solution.  In this particular post, I’m going to start the conversation on how SLAs may tie into the overall concept of data tiering as well as infrastructure access SLAs. This particular post is more of a “working edition” than anything else, so, comments are certainly welcome and warranted. 

Service Level Agreements provide additional frameworks for data storage and access along with particular sensitivities to the methodology of access as driven by compliance.  Understandably this subject is very broad in scope so, for the purpose of clarity, focus will be given to two basic SLA metrics: data storage and data access.  These SLAs serve two purposes: to structure the type of relationship between a customer and their data within the cloud and provide a legal framework whereby customer and provider realize risks/benefits and provide remediation.

[click to continue…]

Share

{ 0 comments }

Shared Filesystems in the Cloud

February 11, 2009

Earlier this morning, Scott Lowe posed the following question:  What if hypervisors shared a file system? The concept here is that most hypervisors (notably VMware and [soon] Hyper-V) have a clustered file system that is used to extend the capabilities of a group of hypervisors into such things as dynamic resource sharing, failover/failback, HA, etc. […]

Share
<br />