Indeed, shared mount point storage works best, but still ugly by its workaround nature)
ср, 25 авг. 2021 г., 18:37 Michael Brußk <m...@mib85.de>: > Hi Ivan, > > well, we have already aligned internal, that we will implement handling > for additional local storage pools (not now, but in near future). > We have also already thought about a very similar workaround as you have > described, but with SharedMountPoint (instead of NFS) in > Single-Node-Clusters ... those the storage-pool would be direct used as > local filesystem/folder by the host ^^ > > regards, > Michael > > 25. August 2021 11:05, "Ivan Kudryavtsev" <i...@bw-sw.com > <i...@bw-sw.com?to=%22ivan%20kudryavtsev%22%20%3ci...@bw-sw.com%3E>> > schrieb: > > Hi, you cannot have multiple local storages for a single host (however it > would be great if it is supported, but not yet). > There is one real-life workaround basically: > 1. you add a single host to a single cluster (e.g. C1) > 2. you export storage pools from the host as NFS filesystems with scope > "Cluster" to the same cluster (e.g. C1) > 3. tag them appropriately like SSD, HDD, etc. > it works, but it's ugly and it has overhead which is introduced by NFS. > Multiple local storage pools would be great to have... > On Wed, Aug 25, 2021 at 3:43 PM Michael Brußk <m...@mib85.de> wrote: > > Hi Davide, > > thanks for replay. > Is there some documentation available about this setting? > When should this be set - before or after the host has been added to CS? > If before, how to make sure this will not be overwritten by the agent > setup process? > > > some of the hosts could mount the ssd and the rest the hdd and assign > tags to the host and the service offerings. > This is not possible, since each host has one local SSD- and one HDD-raid, > those it can't be mounted from/to other hosts (maybe via NFS, but this > would result in a weird design) > Regards, > Michael > -----Ursprüngliche Nachricht----- > Von: David Jumani <david.jum...@shapeblue.com> > Gesendet: Mittwoch, 25. August 2021 09:01 > An: users@cloudstack.apache.org > Betreff: Re: How to add additional local storage pools on KVM > > Hi, > > You can specify the path to a local directory on the host (which can be > mounted) in the agent.properties file > > local.storage.path=/mnt/path > > As for multiple storage locations on a single host, I'm not sure whether > it is supported As a workaround, some of the hosts could mount the ssd and > the rest the hdd and assign tags to the host and the service offerings. > > CloudStack will match those tags and bring up the VM on the appropriate > host ________________________________ > > From: Michael Bru?k <m...@mib85.de (mailto:m...@mib85.de)> > > Sent: Tuesday, August 24, 2021 7:55 PM > > To: users@cloudstack.apache.org (mailto:users@cloudstack.apache.org) < > users@cloudstack.apache.org (mailto:users@cloudstack.apache.org)> > > Subject: How to add additional local storage pools on KVM > > Hi, > > how is it possible to add additional local storage pools to KVM hosts? > > As per documentation (and observations) when adding a new KVM host to a > zone, where "use local storage for client vms" is enabled, CS automatically > creates a new filesystem based local storage pool under > /var/lib/libvirt/images. > > We would like to use two additional local storages for different purposes > (ssd-raid for realtime/hot data and hdd-raid for archive data) on each host > (cluster with upto 8 hosts). > > We are aware of that live migrations are not functional when using local > storage, but we want to use already existing CloudStack installation (and > all our processes around) for this special project. > > Regards, > > Michael > > > >
