cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Will Stevens <wstev...@cloudops.com>
Subject Re: Using S3/Minio as the only secondary storage
Date Wed, 17 Jul 2019 10:58:52 GMT
Hey JF,
We use the Swift object store as the storage backend for secondary
storage.  I have not tried the S3 integration, but the last time I looked
at the code for this (admittedly, a long time ago) the Swift and s3 logic
was more intertwined than I liked. The CloudOps/cloud.ca team had to do a
lot of work to get the Swift integration to a reasonable working state. I
believe all of our changes have been upstreamed quite some time ago. I
don't know if anyone is doing this for the S3 implementation.

I can't speak to the S3 implementation because I have not looked at it in a
very long time, but the Swift implementation requires a "temporary NFS
staging area" that essentially acts kind of like a buffer between the
object store and primary storage when templates and such are used by the
hosts.

I think Pierre-Luc and Syed have a clearer picture of all the moving
pieces, but that is a quick summary of what I know without digging in.

Hope that helps.

Cheers,

Will

On Tue, Jul 16, 2019, 10:24 PM Jean-Francois Nadeau <the.jfnadeau@gmail.com>
wrote:

> Hello Everyone,
>
> I was wondering if it was common or even recommended to use an S3
> compatible storage system as the only secondary storage provider ?
>
> The environment is 4.11.3.0 with KVM (Centos 7.6),  and our tier1 storage
> solution also provides an S3 compatible object store (apparently Minio
> under the hood).
>
> I have always used NFS to install the SSVM templates and the install script
> (cloud-install-sys-tmplt) only takes a mount point.  How, if possible,
> would I proceed with S3 only storage ?
>
> best,
>
> Jean-Francois
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message