This two APIs are not used currently. You can use whatever column in volumes table to store the additional information(e.g. The chap) about the volume, and send down the information to hypervisor resource, along with attachvolumecmd.
Sent from my Windows Phone ________________________________ From: Mike Tutkowski<mailto:mike.tutkow...@solidfire.com> Sent: 4/16/2013 12:45 PM To: Edison Su<mailto:edison...@citrix.com>; cloudstack-...@incubator.apache.org<mailto:cloudstack-...@incubator.apache.org> Subject: grant/revokeAccess Question Hi Edison, I forgot to ask you about these methods when we talked yesterday. :) It is my understanding that grant/revokeAccess will be called to grant access to a host or revoke access from a host for a volume. Our SAN has two ways of allowing access to volumes from hosts: 1) If the necessary CHAP credentials are in place on the host, the host can access the volume. 2) If CHAP is not in use, the host's IQN needs to be listed in what we call a Volume Access Group for the given volume. I might be able to "get away" with just supporting number 2. Is grant/revokeAccess the place where I would either talk to the hypervisor to provide it with CHAP credentials or talk to our SAN to place the host's IQN in the Volume Access Group for the volume? If so, I assume it is OK for these methods to take a little time to execute as a call would need to go out to the hypervisor or the SAN. Thanks! -- Mike Tutkowski Senior CloudStack Developer, SolidFire Inc. e: mike.tutkow...@solidfire.com<mailto:mike.tutkow...@solidfire.com> o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>™
