-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
385 lines (256 loc) · 12.3 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
<!DOCTYPE html>
<!--[if IEMobile 7 ]><html class="no-js iem7"><![endif]-->
<!--[if lt IE 9]><html class="no-js lte-ie8"><![endif]-->
<!--[if (gt IE 8)|(gt IEMobile 7)|!(IEMobile)|!(IE)]><!--><html class="no-js" lang="en"><!--<![endif]-->
<head>
<meta charset="utf-8">
<title>John Eastman</title>
<meta name="author" content="John Eastman">
<meta name="description" content="The Storage Networking Industry Association (SNIA) has
produced a specification called CDMI (Cloud Data
Management Interface). CDMI provides an …">
<!-- http://t.co/dKP3o1e -->
<meta name="HandheldFriendly" content="True">
<meta name="MobileOptimized" content="320">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="canonical" href="http://jeastman.info/">
<link href="/favicon.png" rel="icon">
<link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet" type="text/css">
<script src="/javascripts/modernizr-2.0.js"></script>
<script src="/javascripts/ender.js"></script>
<script src="/javascripts/octopress.js" type="text/javascript"></script>
<link href="/atom.xml" rel="alternate" title="John Eastman" type="application/atom+xml">
<!--Fonts from Google"s Web font directory at http://google.com/webfonts -->
<link href="http://fonts.googleapis.com/css?family=PT+Serif:regular,italic,bold,bolditalic" rel="stylesheet" type="text/css">
<link href="http://fonts.googleapis.com/css?family=PT+Sans:regular,italic,bold,bolditalic" rel="stylesheet" type="text/css">
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-36987301-1']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
</script>
</head>
<body >
<header role="banner"><hgroup>
<h1><a href="/">John Eastman</a></h1>
</hgroup>
</header>
<nav role="navigation"><ul class="subscription" data-subscription="rss">
<li><a href="/atom.xml" rel="subscribe-rss" title="subscribe via RSS">RSS</a></li>
</ul>
<form action="http://google.com/search" method="get">
<fieldset role="search">
<input type="hidden" name="q" value="site:jeastman.info" />
<input class="search" type="text" name="q" results="0" placeholder="Search"/>
</fieldset>
</form>
<ul class="main-navigation">
<li><a href="/">Home</a></li>
<li><a href="/blog/archives">Archives</a></li>
<li><a href="/about">About</a></li>
</ul>
</nav>
<div id="main">
<div id="content">
<div class="blog-index">
<article>
<header>
<h1 class="entry-title"><a href="/blog/2012/12/17/cdmi/">CDMI</a></h1>
<p class="meta">
<time datetime="2012-12-17T08:00:00-06:00" pubdate data-updated="true">Dec 17<span>th</span>, 2012</time>
| <a href="/blog/2012/12/17/cdmi/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>The Storage Networking Industry Association (<a href="http://snia.org">SNIA</a>) has
produced a specification called <a href="http://snia.org/cdmi">CDMI</a> (Cloud Data
Management Interface). CDMI provides an
<a href="http://cdmi.sniacloud.org">interface specification</a> for accessing and
managing data in the Cloud. The CDMI specification was recently designated
an International Standard by the Joint Technical Committee 1 (JCT 1), a
joint effort of the
<a href="http://www.iso.org/iso/home.html">International Organization for Standardization</a>
(ISO) and the
<a href="http://www.iec.ch/">International Electrotechnical Commission</a> (IEC).</p>
<p>The standard designation by ISO has stirred up a considerable amount of
interest in CDMI. I also have a lot of interest in this specification and
it is a topic I will likely touch on in future posts, so I thought I would
cover some background information.</p>
<p>Cloud storage, in general, has seen a lot of press recently. Most of the
interest appears to be around the consumer based offerings for personal
online storage. These isolated services fill the need for individuals, but
offer very little in terms of interoperability and portability. Several
services provide APIs or developer SDKs, but they are very proprietary. The
more services you integrate into them and the more storage you use, the
harder it becomes to move off of them. If these online storage services
were to adopt a standard interface, it might be easier to migrate between
them from a service integration perspective. However, moving large amounts
of storage from one vendor to another would continue to be an issue.</p>
<p>CDMI attempts to address the first part of the problem, providing a
standard interface. The surface benefits of this to both the end user and
application vendor are easy to see. Vendors producing client applications
could simply write their application to the standard and provide support
for any service supporting the standard. End users could happily use their
chosen applications on the service of their choice. While CDMI provides a
mechanism for serializing data into and out of a particular vendor’s
storage service implementation, physics of bandwidth and data size get in
the way of this being practical.</p>
<p>There are a couple of features of CDMI that I particularly like:</p>
<ul>
<li><p>Capabilities</p>
<p> CDMI defines a capabilities model that allows client applications to
discover the capabilities of particular service. This gives client
applications the ability to determine if a particular service has the
features they require. The capabilities defined in the specification
cover all aspects of the service, including service levels. This
includes security features, throughput requirements as well as being
able to define higher level features like Restore Point and Restore
Time Objectives (RPO/RTO). The specification also provides a means for
the service to report back to the client actual values that the service
is able to achieve for these features. Having features like this
provides a programmatic means for client applications to actually
inspect the service level delivered.</p></li>
<li><p>Metadata</p>
<p> Client applications can store metadata as part of any object in
CDMI. While this is not unique, the metadata can actually have an
effect on an object. Most capabilities supported by the service have
corresponding metadata values that can be used to trigger or modify the
capability.</p></li>
<li><p>Management</p>
<p> CDMI provides a means of actually managing your data, not just storing
and retrieving it. The specification has a concept of containers, that
may be nested, acting like folders of a file system. Metadata can be
placed on containers and inherited by the objects it contains.</p></li>
<li><p>Non-CDMI access</p>
<p> It does not always make sense to access data stored in a service
through the CDMI interface. If a particular client (a web browser for
example) does not know how to construct nor interpret a CDMI request,
it should still be able to gain access to the content. The CDMI
specification actually covers these cases, thereby standardizing how
all clients access a service. This also allows one to use a CDMI
enabled service as something like a web server.</p></li>
</ul>
<p>The CDMI specification provides not only the basic requirements for a Cloud
Storage Service, but it also includes features that provide higher level
control over the stored data. These features allow for client applications
that go beyond simple file storage and enables them to support the
requirements of real businesses. While there is not anything that can
combat the physics of infrastructure, a standard interface for data
portability addresses a large set of the issues.</p>
<p>If you have not looked at the specification itself, head over to
<a href="http://cdmi.sniacloud.org">cdmi.sniacloud.org</a> to check it out. The “Overview of Cloud Storage” (Section 5) is well worth the read. Another good source of information on CDMI is the <a href="http://blogs.netapp.com/context/">Objects in Context</a>
blog which aggregates a number of CDMI sources from around the internet as
well as providing original content.</p>
</div>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2012/12/10/first-post/">Every Blog Has Its First Post…</a></h1>
<p class="meta">
<time datetime="2012-12-10T00:00:00-06:00" pubdate data-updated="true">Dec 10<span>th</span>, 2012</time>
| <a href="/blog/2012/12/10/first-post/#disqus_thread">Comments</a>
</p>
</header>
<div class="entry-content"><p>Hello, and welcome to my blog!</p>
<p>Everything has to start somewhere, and this blog starts here. I find that I
gather a lot of little bits and pieces of things that I tend to share with
people individually. I’ll be posting these things here to serve as a
reference and hopefully help some other people along the way. Expect to see
primarily articles about technology, personal optimization, and maybe some
code here and there.</p>
<p>I hope you’ll enjoy reading the things you find here.</p>
</div>
</article>
<div class="pagination">
<a href="/blog/archives">Blog Archives</a>
</div>
</div>
<aside class="sidebar">
<section>
<h1>Recent Posts</h1>
<ul id="recent_posts">
<li class="post">
<a href="/blog/2012/12/17/cdmi/">CDMI</a>
</li>
<li class="post">
<a href="/blog/2012/12/10/first-post/">Every blog has its first post…</a>
</li>
</ul>
</section>
<section>
<h1>GitHub Repos</h1>
<ul id="gh_repos">
<li class="loading">Status updating…</li>
</ul>
<a href="https://github.com/jeastman">@jeastman</a> on GitHub
<script type="text/javascript">
$.domReady(function(){
if (!window.jXHR){
var jxhr = document.createElement('script');
jxhr.type = 'text/javascript';
jxhr.src = '/javascripts/libs/jXHR.js';
var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(jxhr, s);
}
github.showRepos({
user: 'jeastman',
count: 2,
skip_forks: true,
target: '#gh_repos'
});
});
</script>
<script src="/javascripts/github.js" type="text/javascript"> </script>
</section>
<section>
<h1>Latest Tweets</h1>
<ul id="tweets">
<li class="loading">Status updating…</li>
</ul>
<script type="text/javascript">
$.domReady(function(){
getTwitterFeed("jeastman", 4, false);
});
</script>
<script src="/javascripts/twitter.js" type="text/javascript"> </script>
<a href="http://twitter.com/jeastman" class="twitter-follow-button" data-show-count="false">Follow @jeastman</a>
</section>
<section class="googleplus">
<h1>
<a href="https://plus.google.com/117421685675919152651?rel=author">
<img src="http://www.google.com/images/icons/ui/gprofile_button-32.png" width="32" height="32">
Google+
</a>
</h1>
</section>
</aside>
</div>
</div>
<footer role="contentinfo"><p>
Copyright © 2012 - John Eastman -
<span class="credit">Powered by <a href="http://octopress.org">Octopress</a></span>
</p>
</footer>
<script type="text/javascript">
var disqus_shortname = 'jeastman';
var disqus_script = 'count.js';
(function () {
var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
dsq.src = 'http://' + disqus_shortname + '.disqus.com/' + disqus_script;
(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
}());
</script>
<script type="text/javascript">
(function(){
var twitterWidgets = document.createElement('script');
twitterWidgets.type = 'text/javascript';
twitterWidgets.async = true;
twitterWidgets.src = 'http://platform.twitter.com/widgets.js';
document.getElementsByTagName('head')[0].appendChild(twitterWidgets);
})();
</script>
</body>
</html>