Yes, I know Suresh :) but our plugin isn't in CS; there is one check in CS
if the volumes are in RAW format to set as Hypervisor OVM, which limits the
whole functionality. (this a workaround)
if (format == ImageFormat.RAW) {
// Currently, KVM only suppoorts RBD images of type RAW.
// This results in a weird collision with OVM volumes which
// can only be raw, thus making KVM RBD volumes show up as OVM
// rather than RBD. This block of code can (hopefuly) by checking to
// see if the pool is using either RBD or NFS. However, it isn't
// quite clear what to do if both storage types are used.
If the image
// format is RAW, it narrows the hypervisor choice down to
OVM and KVM / RBD or KVM / CLVM
// This would be better implemented at a cluster level.
List<StoragePoolVO> pools =
s_storagePoolDao.listByDataCenterId(dcId);
ListIterator<StoragePoolVO> itr = pools.listIterator();
while(itr.hasNext()) {
StoragePoolVO pool = itr.next();
if(pool.getPoolType() == StoragePoolType.RBD ||
pool.getPoolType() == StoragePoolType.CLVM) {
// This case will note the presence of non-qcow2
primary stores, suggesting KVM without NFS. Otherwse,
// If this check is not passed, the hypervisor type
will remain OVM.
type = HypervisorType.KVM;
break;
}
}
and my guess is that the other block storage plugins like SolidFire, I
don't know if nexenta/datera/cloudbyte are working like this - will
have the same problem.(don't know if there are other plugins like our
not in CS)
Best regards,
Slavka
On Fri, Jul 16, 2021 at 1:03 PM Suresh Anaparti <
[email protected]> wrote:
> May be, you can set the volume format to 'RAW' (which is the actual
> format) when using StorPool plugin, and retry the operation.
>
> Regards,
> Suresh
>
> On 16/07/21, 2:10 PM, "Slavka Peleva" <[email protected]>
> wrote:
>
> Hi, Suresh, Sven,
>
> Yes, based on code and I think that it's QCOW2, but wanted to be sure
> :)
> There is a problem with shrinking the volumes for the block storage
> plugins
> (like StorPool) which are keeping the volumes' format as QCOW2 but the
> actual format is RAW. That's why I'm trying to find out if the rest
> have
> the same issue.
>
> Best regards,
> Slavka
>
>
>
>
>
>
> On Fri, Jul 16, 2021 at 10:39 AM Sven Vogel <[email protected]> wrote:
>
> > Hi Slavka,
> >
> > We use it. Talk about slack.
> >
> > Cheers
> >
> > Sven
> >
> > __
> >
> > Sven Vogel
> > Senior Manager Research and Development - Cloud and Infrastructure
> >
> > EWERK DIGITAL GmbH
> > Brühl 24, D-04109 Leipzig
> > P +49 341 42649 - 99
> > F +49 341 42649 - 98
> > [email protected]
> > www.ewerk.com
> >
> > Geschäftsführer:
> > Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
> > Registergericht: Leipzig HRB 9065
> >
> > Support:
> > +49 341 42649 555
> >
> > Zertifiziert nach:
> > ISO/IEC 27001:2013
> > DIN EN ISO 9001:2015
> > DIN ISO/IEC 20000-1:2018
> >
> > ISAE 3402 Typ II Assessed
> >
> > EWERK-Blog<https://blog.ewerk.com/> | LinkedIn<
> > https://www.linkedin.com/company/ewerk-group> | Xing<
> > https://www.xing.com/company/ewerk> | Twitter<
> > https://twitter.com/EWERK_Group> | Facebook<
> > https://de-de.facebook.com/EWERK.Group/>
> >
> >
> > Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
> >
> > Disclaimer Privacy:
> > Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter
> Dateien) ist
> > vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> > bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> > Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt.
> Bitte
> > informieren Sie in diesem Fall unverzüglich den Absender und löschen
> Sie
> > die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem
> System.
> > Vielen Dank.
> >
> > The contents of this e-mail (including any attachments) are
> confidential
> > and may be legally privileged. If you are not the intended recipient
> of
> > this e-mail, any disclosure, copying, distribution or use of its
> contents
> > is strictly prohibited, and you should please notify the sender
> immediately
> > and then delete it (including any attachments) from your system.
> Thank you.
> >
> > ________________________________
> > Von: Suresh Anaparti <[email protected]>
> > Gesendet: Friday, July 16, 2021 9:24:56 AM
> > An: [email protected] <[email protected]>
> > Betreff: Re: Question about SolidFire plugin with KVM hypervisor
> >
> > HI Slavka,
> >
> > Based on the code, it would be 'QCOW2' format for KVM, did you
> notice any
> > discrepancies there.
> >
> > Regards,
> > Suresh
> >
> > On 15/07/21, 10:14 PM, "Slavka Peleva" <[email protected]
> >
> > wrote:
> >
> > Hi all,
> >
> > Is there someone of you who uses the CS 4.15.1.0 or latest with
> > SolidFire
> > primary storage over a KVM hypervisor? If there is someone, is it
> > possible
> > to share the volumes' format in the DB?
> >
> > Probably more questions will appear after this :)
> >
> > Best regards,
> > Slavka
> >
> >
> >
> >
> >
>
>
