A brief description can be found in the agent.properties file # local storage path, by default, it's /var/lib/libvirt/images/ #local.storage.path=/var/lib/libvirt/images/
>From my experience this needs to be set before adding the host to cloudstack >(if not, remove it, change the setting and re-add it) This won't be overwritten, however cloudstack will use a shared pool if the zone is not set to use local storage Use of local storage in cloudstack can be controlled by the use.local.storage setting http://docs.cloudstack.apache.org/en/latest/installguide/configuration.html#configuration-parameters About the ssd and hdd scenario, If that's the case, the local.storage.path can point to either the ssd or hdd partition and tag the host and offerings accordingly ________________________________ From: Michael Brußk <m...@mib85.de> Sent: Wednesday, August 25, 2021 2:12 PM To: users@cloudstack.apache.org <users@cloudstack.apache.org> Subject: Re: How to add additional local storage pools on KVM 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
