This topic (below) is actually much more relevant to people than I initially thought it would be (hence why I just sent it to Edison in the first place).
Please feel free to provide comments and suggestions. Thanks! On Tue, Sep 2, 2014 at 11:54 PM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > Actually, if we add such a "capability," that could even streamline the > process of taking a snapshot in the first place. > > I think this is going to be something that several SAN vendors would be > interested in, too. > > > On Tue, Sep 2, 2014 at 11:51 PM, Mike Tutkowski < > mike.tutkow...@solidfire.com> wrote: > >> Hi Edison, >> >> I was hoping to off-list brainstorm with you about something. >> >> I want to support SolidFire snapshots in CloudStack, but the current >> CloudStack model of snapshots is a bit difficult to fit within (the fact >> that a CloudStack snapshot is really a backup and is stored on secondary >> storage). >> >> I currently have my storage plug-in implemented to support takeSnapshot, >> canCopy, and copyAsync in order to create a SolidFire snapshot when the >> user wants to take a CloudStack snapshot of a volume that's backed by a >> SolidFire volume. This works just fine. >> >> The problem comes in with deleting the snapshot. >> >> When I try to delete the snapshot, CloudStack calls the secondary storage >> plug-in to do this; however, my snapshot is not on the storage system that >> the secondary-storage plug-in represents (my snapshot is on the SolidFire >> SAN only). >> >> Do you see my issue here? >> >> I don't want to have to add SolidFire as secondary storage in order to >> take a snapshot on the SolidFire SAN (for one, SolidFire only supports >> iSCSI and FC...not NFS). >> >> What do you recommend I do here? I was thinking I could add a >> "capability" to the SolidFire plug-in (returned via the getCapabilities >> method) that would tell CloudStack that this primary-storage plug-in is >> what needs to have deleteAsync invoked in order to delete the snapshot. >> >> What do you think about that possible approach? >> >> Thanks! >> >> -- >> *Mike Tutkowski* >> *Senior CloudStack Developer, SolidFire Inc.* >> e: mike.tutkow...@solidfire.com >> o: 303.746.7302 >> Advancing the way the world uses the cloud >> <http://solidfire.com/solution/overview/?video=play>*™* >> > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the cloud > <http://solidfire.com/solution/overview/?video=play>*™* > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud <http://solidfire.com/solution/overview/?video=play>*™*
