We can migrate to Object storage from NFS. In this case the existing NFS
storage would act as a staging secondary storage. Whenever we use any
storage artifacts for the first time after adding S3 based object storage,
CS would be automatically move them to object storage.
Here is the FS for more details
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Migration+of+NFS+Secondary+Storage+to+Object+Store#


On Wed, Feb 3, 2016 at 3:47 PM, Nux! <n...@li.nux.ro> wrote:

> Hello Michael,
>
> S3-like can be used with Cloudstack, but do note you still need a NFS
> secondary storage for staging purposes, though no permanent data should be
> saved there.
>
> I am not using it myself, but I know there are a few people who do and
> they may be able to advise further. It's definitely a solution; not sure
> about the multiple bucket issue.
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> ----- Original Message -----
> > From: "Michael J McCafferty" <m...@m5hosting.com>
> > To: users@cloudstack.apache.org
> > Sent: Wednesday, 3 February, 2016 09:06:45
> > Subject: Object Storage as Secondary Storage
>
> > Hi All,
> >       We currently use NFS storage for Secondary Storage, but are going
> to be
> > adding Object Storage in our data centers. I am interested in the
> > possibility of putting the current secondary storage on a replicated
> > object storage for several reasons. I have questions:
> >
> >       Is there a migration path from using NFS based secondary storage to
> > using Object Storage. What is it? Is anyone using object storage for
> > secondary storage? Is anyone using Cloudian object storage specifically
> > or some other?
> >
> >       Any special consideration to be aware of when using object storage
> with
> > CloudStack?
> >
> >       Can snapshots and templates be in different buckets? (Want to apply
> > different replication rules for each)
> >
> >       Any experience that can be shared would be appreciated.
> >
> > Thank you!
> > Mike
> >
> > --
> > ************************************************************
> > Michael J. McCafferty
> > ************************************************************
>

Reply via email to