« A Quick Note On Primary Data Dedupe and I/O Density | Main | I Want To Hear About EMC's Storage Strategy »

September 29, 2009

TrackBack

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

Listed below are links to weblogs that reference Cloudy Discussions:

Comments

Christofer Hoff

Thanks, Chuck.

Good post.

Steve Todd reminded me that FastScale has a play here in re: to the Bloat problem and I'm glad you brought it up.

Great comments.

/Hoff

Evan

Hi Chuck,

Been looking on keenly in regards to developments with the "cloud" and the possibilities it brings forth, a lot of technologies have taken shape over the last couple of years which make the hole concept of infrastructure as a service in its current and future state a very exciting prospect.

With all these mechanisims now emerging through the revelation of virtualisation (be it storage/server/infrastructure) and ever increasing bandwidth speeds, data/resource mobility could be such that ultimately if an end user decided to utilise an IAAS offering in the future, his data could effectively reside in a data centre in any given country. In terms of compliance/ownership/etc.. this brings forth the question, if something should happen to that customers data... the rule of law in which country should apply in regards to his rights and the IAAS providers responsibility to that customer? There may be something in place already or something in the works to regulate companies offering such a service.. but its not something I've seen. Are you aware of anything ?

Chuck Hollis

The "rule of law" is a work in progress when it comes to these topics. The laws are poorly written, enforcement is virtually non-existent, and some are impossible and/or unrealistic to consider.

That being said, enforcing data location policy is becoming a rather straightforward proposition if the system is designed for it.

For example, Cisco networks can enforce policy routing *if the data is appropriately tagged*, i.e. feel free to route this file packet, as long as it doesn't leave the country.

EMC's Atmos can do the same thing at an object metadata level, i.e. this object is not allowed in this country, or can't leave that country, or must be encrypted a certain way.

The problem, of course, is legacy. File systems and ordinary networks don't understand information logistics concepts. These people can use DLP approaches that are driven by content awareness, but usually most auditors frown on even the remote possibility that something is missed, and exposure is created.

Great discussion -- thanks for the comment!

The comments to this entry are closed.

Chuck Hollis


  • Chuck Hollis
    Chief Strategist, VMware SAS BU
    @chuckhollis

    Chuck has recently joined VMware in a new role, and is quite enthused!

    Previously, he was with EMC for 18 years, most of them great.

    He enjoys speaking to customer and industry audiences about a variety of technology topics, and -- of course -- enjoys blogging.

    Chuck lives in Holliston, MA with his wife, three kids and four dogs when he's not travelling. In his spare time, Chuck is working on his second career as an aging rock musician.

    Warning: do not buy him a drink when there is a piano nearby.
Enter your Email:
Preview | Powered by FeedBlitz

General Housekeeping

  • Frequency of Updates
    I try and write something new 1-2 times per week; less if I'm travelling, more if I'm in the office. Hopefully you'll find the frequency about right!
  • Comments and Feedback
    All courteous comments welcome. TypePad occasionally puts comments into the spam folder, but I'll fish them out. Thanks!