incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Tutkowski <mike.tutkow...@solidfire.com>
Subject Storage Subsystem 2.0 Questions
Date Tue, 05 Mar 2013 05:21:57 GMT
Hi,

I'm working on implementing a storage plug-in for CS 4.2.

I'm looking at the following Wiki page for guidance, but have some
questions:

https://cwiki.apache.org/CLOUDSTACK/storage-subsystem-20.html

One interface that needs to be implemented is PrimaryDataStoreDriver.  I'm
not sure what is expected for all of the following methods:

* grantAccess:  It looks like this is called in an attempt to confirm that
the host which desires access to the volume in question is allowed to do
so.  I suspect this is where CHAP credentials might be provided?  In my
situation, there are a couple ways I'd like to restrict access:  1) CHAP or
2) allow a subset of IQNs to access the volume in question.  Is this kind
of information provided to me here?  Do I simply return the IQN of the
volume as a successful response from this method?  What if the access sent
is not sufficient?  How do I deny access?

* revokeAccess:  I don't really understand when this method would be called
or why.  Perhaps I can simply implement it to return true (or false)?  In
my situation, when a volume is dynamically created for a hypervisor of a
cluster, I'd want to allow access to it from all hosts in the app cluster
in question.  Maybe this method is called before the volume is deleted or
something?

* listObjects:  I don't really understand when this method would be called
or why.

* createAsync:  I believe this is where I place my code to create a volume
(LUN) on our SAN.

* deleteAsync:  I believe this is where I place my code to delete a volume
(LUN) on our SAN.

Thanks for any guidance here!

-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message