If you remove it, it will break the following APIs: createPool createVolumeOnFiler createLunOnFiler AssociateLun
Here's how it is used: The steps are 1. create a volume pool using the createPool <http://download.cloud.com/releases/3.0.6/api_3.0.6/user/createPool.html> API (algorithm can be "leastfull" or "roundrobin") 2. add volumes to the pool using the createVolumeOnFiler <http://download.cloud.com/releases/3.0.6/api_3.0.6/user/createVolumeOnFile r.html> API. This requires the IP address of the NetApp filer and its credentials 3. create LUNs in the volume pool using createLunOnFiler <http://download.cloud.com/releases/3.0.6/api_3.0.6/user/createLunOnFiler.h tm> API. Depending on the algorithm for the pool, CloudStack will choose the NetApp Volume to create the LUN. Once a bare metal host / vm has booted up, you need to determine its ISCSI initiator iqn and then use the AssociateLUN <http://download.cloud.com/releases/3.0.6/api_3.0.6/user/associateLun.html> API set the LUN mask on the filer for that LUN. Then the ISCSI initiator on the bare metal host / vm can login to the LUN. On 9/23/13 10:32 AM, "Chip Childers" <chipchild...@apache.org> wrote: >On Mon, Sep 23, 2013 at 04:44:51PM +0000, SuichII, Christopher wrote: >> I'd like to get a final word on this - is it OK to be removed? Is there >>someone who is knowledgable with what it will take to remove it and/or >>is comfortable removing it? I don't know how tied into the rest of the >>codebase it is. > >I'm +1 to remove, but there are artifacts all over the place (UI, DB, >code). It might require some careful work to extract it cleanly. > >Any takers? > >-chip
