That API will be easy to be added, and yes, I'll add it next week. In the last email, I just give zone-wide primary storage as an example, and I thought your storage box will be zone-wide? As you can see, createstoragepoolcmd api is quite flexible, it can be used for zone-wide/cluster storage, so do the storage plugin.
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] Sent: Friday, March 08, 2013 4:09 PM To: Edison Su Cc: cloudstack-dev@incubator.apache.org Subject: Re: Making use of a 4.2 storage plug-in from the GUI or API OK, cool - thanks for the info, Edison. When you say, "One API is missing," does that mean you're still working on implementing that functionality? Also, it sounds like these plug-ins are associated with Zone-wide Primary Storage. I thought Zone-wide Primary Storage wasn't available for all hypervisors? This is from a different e-mail you sent out: "Xenserver and vmware doesn't support zone wide primary storage, currently, this feature is only for NFS/Ceph in KVM. And I think it should be useful for your storage box? I am thinking per data volume per LUN for xenserver." I'm not sure how my plug-in would work with XenServer, VMware, etc. if it has to be Zone-wide. Can you clarify this for me? Thanks! On Fri, Mar 8, 2013 at 4:33 PM, Edison Su <edison...@citrix.com<mailto:edison...@citrix.com>> wrote: One API is missing, liststorageproviderscmd, which will list all the storage providers registered in the mgt server. When adding a zone wide storage pool on the UI, the UI will have a drop-down list to show all the primary storage providers. Then user will choose one of them, and select some other parameters for the storage user wants to add. At the end, UI will call, createstoragepoolcmd, with provider=the-storage-provider-uuid-returned from liststoageprovidercmd, scope=zone, and other input parameters. Mgt server will then call corresponding storage provider based on provider uuid, to register the storage into cloudstack. From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com<mailto:mike.tutkow...@solidfire.com>] Sent: Friday, March 08, 2013 2:46 PM To: cloudstack-dev@incubator.apache.org<mailto:cloudstack-dev@incubator.apache.org> Cc: Edison Su Subject: Making use of a 4.2 storage plug-in from the GUI or API Hi, As you may remember, I'm leveraging Edison's new (4.2) storage plug-in framework to build what is probably the first such plug-in for CloudStack. I was wondering, does anyone know how to make the system aware of the plug-in? I believe once the plug-in is ready (i.e. usable) that the intent is to be able to select it when creating Primary Storage (instead of having to select a pre-existent iSCSI target). I'm curious how to get this working (i.e. select my plug-in) in the GUI and via the API. Thanks! -- Mike Tutkowski Senior CloudStack Developer, SolidFire Inc. e: mike.tutkow...@solidfire.com<mailto:mike.tutkow...@solidfire.com> o: 303.746.7302<tel:303.746.7302> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>(tm) -- 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>(tm)
