<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>Good point. I missed that.</div><div>i) My thought was that 1.6 will follow 1.2, ie create and then attach. </div><div> In which case it should be a PUT /servers/id/disks/id</div><div>ii) And, if we want to do a create/attach as a single operation, then POST /servers/id/disks is fine too.</div><div>Cheers</div><div><k/><br></div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size: 10pt; color: black; font-family: verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [Openstack] Block storage management API (Cloud Disks API)<br>
From: Jay Pipes <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>><br>
Date: Tue, January 18, 2011 6:18 am<br>
To: <a href="mailto:ksankar@doubleclix.net">ksankar@doubleclix.net</a><br>
Cc: Vangelis Koukis <<a href="mailto:vkoukis@cslab.ece.ntua.gr">vkoukis@cslab.ece.ntua.gr</a>>,<br>
<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>, <a href="mailto:cven@cslab.ece.ntua.gr">cven@cslab.ece.ntua.gr</a><br>
<br>
On Mon, Jan 17, 2011 at 8:50 PM, <<a href="mailto:ksankar@doubleclix.net">ksankar@doubleclix.net</a>> wrote:<br>
> Couple of quick observations on the REST semantics :<br>
> a) What is the context of calls in 1.1 ? A user ? Looks like you are<br>
> assuming the context of a user/group that will own both VMs and disks, which<br>
> is fine. Just wanted to make sure that what it is. You might want to<br>
> consider the case for disk sharing (not simultaneously) where a use creates<br>
> a data set and then others attach it<br>
> b) Looks like there is always RW; no RO disks<br>
> c) You could also extend this for volumes; don't think there is any<br>
> difference between a block device and a volume for the kinds of operations<br>
> listed here<br>
> d) yep, 1.4 PUT /servers/id/disks/id is redundant. No need and it is<br>
> error prone<br>
> e) I think 1.6 requires an id ie POST /servers/id/disks/id<br>
> f) Have you looked at OCCI ?<br>
<br>
All good points, with one tiny exception. e) POST /servers/id/disks<br>
should not have a trailing id, as a POST call creates the disk's ID,<br>
at least for most REST interfaces. The PUT call, however, would<br>
include the id...<br>
<br>
Cheers!<br>
jay<br>
</div>
</blockquote></span></body></html>