Slavka, By your description it seems best to either backup those snapshots to secondary on deletion of the VM or to delete them with the VM. leaving it to the driver is ok, as long as the functionality is clear to the user. In addition, we would want to keep behaviour as consistent as possible across drivers. In this case there is a limitation to that. I'd say make an extra option that defines behaviour on delete so the operator can decide.
On Tue, Sep 14, 2021 at 9:20 AM Slavka Peleva <slav...@storpool.com.invalid> wrote: > Hi all, > > There is a problem with snapshots kept only on primary storage for > non-managed drivers, and I've opened an issue request #5433 > <https://github.com/apache/cloudstack/issues/5433> > The problem is when we delete a volume with more than one snapshot kept > only on primary with the option snapshot.backup.to.secondary to false. And > the behaviour is different for most of the non-managed drivers. > My question is which is the best way to handle this? > For me the better option is each driver to handle this (if there is need to > delete the snapshots from DB/storage or they could live without the volume) > > Thanks for the help! > > > Best regards, > Slavka > -- Daan
