« VMworld 2008 - EMC Wrap-up - Part II | Main | Wow - all I can say is THANK YOU. »

November 10, 2008

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00e552e53bd28833010535e90386970c

Listed below are links to weblogs that reference What's the relationship between VMware vCloud and EMC Atmos?:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Christina Casten

I'd like to link to this particular blog from the SNIA XAM Public De velopers Portal
http://groups.google.com/group/xam-developers-group

Terry

Atmos sounds like a CDN, so COS is not really new...?
http://www.elasticvapor.com/2008/11/defining-cloud-optimized-storage.html

Would you agree?

What is the use case for Atmos in the VMware context?
Obviously it's for Content Delivery of ISO's, Templates and VM's at a global scale in whatever format you choose (OVF, VMDK, VHD, AMI, etc.) in this new cloud enabled world.

I do see in the future you are able to pull down a Mobile VM from the cloud via Web APIs (REST/SOAP) on your mobile device or access the content you have stored in the cloud from anywhere at anytime. Mobile Devices, VM's, Apps will change and be obsolete but your content will not (home movies, pictures, music, personal docs, etc) and this is what you want to keep secure and available. This is where I see the Atmos CDN. :P

John Webster

Virtual Geek:

There are a number of things that I'd like to explore here re: Atmos but let me start with the COS use case that implies a definition of COS. You list some COS attributes, but could some others also be included? Such as:

Security (perhaps "multi-tenancy" is "secure multi-tenancy?")
Object versioning
Object persistence
Scale to billions of users (as opposed to objects)
Local data caching


John Webster
Illuminata

Hossein

hello
i want to know vmmare Dos device usb
help me
Hossein

Former EMCDE

Small quibble: CAS and XAM both allow unlimited metadata. In fact, Centera allows more metadata than Atmos (which I believe has a limit of about 256 tags); Centera is limited to 100 MB of metadata. The metadata mentioned above is part and parcel of the object model but is a subset of the completely extensible metadata model.

BTW: XAM would make an exciting access method for Atmos. A prototype of this was developed in November, 2008 and DiskXtender (which has a XAM implementation) was demonstrated running on Atmos. I don't know what became of that effort.

The comments to this entry are closed.

  • BlogWithIntegrity.com

Disclaimer

  • The opinions expressed here are my personal opinions. Content published here is not read or approved in advance by EMC and does not necessarily reflect the views and opinions of EMC. This is my blog, it is not an EMC blog.

Enter your email address:

Delivered by FeedBurner