Friday, July 24, 2009

test version of VbsNimbusService deployed

We have got a basically working version of VBS integrated with Nimbus,
and I have deployed a test version of the integrated web service,
VbsNimbusService, to
http://cglc.uits.iu.edu:8080/axis2/services/VbsNimbusService?wsdl.
Some basic features include:

1) It is deployed under axis2, not globus; without any security
mechanisms or user management yet. So you can actually call it freely
with EPR http://cglc.uits.iu.edu:8080/axis2/services/VbsNimbusService/
.

2) It provides the same interface as EBS with SOAP binding. Note that
it accepts Nimbus workspace instance id numbers, such as 39 or 44, not
the handle names returned by the Nimbus cloud client.

3) The "progress" property of snapshot creation and "force" argument
of volume detach operation are not implemented yet. The snapshot
creation process is usually quick so you should be able to see the
status of a snapshot updated to "created" soon after the
createSnapshot operation returns. The "availabilityZone" property of a volume is meaningless in current VBS implementation, but we are keeping the information in the metadata database of the volumes.

4) For volumes newly created based on snapshots, there are 4 possible status: available, in-use, pending, and failed. "Available" means that the volume has been created successfully, and is available for attachment. "In-use" means that the volume is currently attached to some VM instance. "pending" means that the new volume is just being created by copying data from a given snapshot, and "failed" means that the volume has been created but the system didn't successfully copy data from the given snapshot to it. Note that in "pending" and "failed" status, the volume is actually also available for attachment; the status names are just an indication of information related to the snapshot-copy operation. It is not recommended to attach a "pending" volume to any VM instance, because operations from the instance may corrupt the copy process and lead to incorrect information written or read.

No comments: