On 10-09-15 12:17, Andrija Panic wrote: > We are testing some [dirty?] patch on our dev system and we shall soon > share it for review. > > Basically, we are using external python script that is invoked in some part > of code execution to delete needed CEPH snapshots and then after that > proceeds with volume deleteion etc... >
That shouldn't be required. The Java bindings for librbd and librados should be able to remove the snapshots. There is no need to invoke external code, this can all be handled in Java. > On 10 September 2015 at 11:26, Andrija Panic <andrija.pa...@gmail.com> > wrote: > >> Eh, OK. Thx for the info. >> >> BTW why is 16 snapshot limits hardcoded - any reason for that ? >> >> Not cleaning snapshots on CEPH and trying to delete volume after having >> more than 16 snapshtos in CEPH = Agent crashing on KVM side...and some VMs >> being rebooted etc - which means downtime :| >> >> Thanks, >> >> On 9 September 2015 at 22:05, Simon Weller <swel...@ena.com> wrote: >> >>> Andrija, >>> >>> The Ceph snapshot deletion is not currently implemented. >>> >>> See: https://issues.apache.org/jira/browse/CLOUDSTACK-8302 >>> >>> - Si >>> >>> ________________________________________ >>> From: Andrija Panic <andrija.pa...@gmail.com> >>> Sent: Wednesday, September 9, 2015 3:03 PM >>> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org >>> Subject: ACS 4.5 - volume snapshots NOT removed from CEPH (only from >>> Secondaryt NFS and DB) >>> >>> Hi folks, >>> >>> we enounter issue in ACS 4.5.1 (perhaps other versions also affected) - >>> when we delete some snapshot (volume snapshot) in ACS, ACS marks it as >>> deleted in DB, deletes from NFS Secondary Storage but fails to delete >>> snapshot on CEPH primary storage (doesn even try to delete it AFAIK) >>> >>> So we end up having 5 live snapshots in DB (just example) but actually in >>> CEPH there are more than i.e. 16 snapshots. >>> >>> More of the issue, when ACS agent tries to obtain list of snapshots from >>> CEPH for some volume or so - if number of snapshots is over 16, it raises >>> exception (and perhaps this is the reason Agent crashed for us - need to >>> check with my colegues who are investigatin this in details). This number >>> 16 is for whatever reasons hardcoded in ACS code. >>> >>> Wondering if anyone experienced this, or have any info - we plan to try to >>> fix this, and I will inlcude my dev colegues here, but we might need some >>> help at least for guidance or- >>> >>> Any help is really apreaciated or at list confirmation that this is known >>> issue etc. >>> >>> Thanks, >>> >>> -- >>> >>> Andrija Panić >>> >> >> >> >> -- >> >> Andrija Panić >> > > >
