This is what I did but it looks like there is a better way to run kolla-ansible on a specific role/service. I have added nova_instance_datadir_volume; /mnt in global.yml and run following command $ kolla-ansible -i all-in-one deploy Above command took 20 minute to finish because it went through each role. but i think i am missing something in documentation to run the above task in a limited way to just push out to a specific container/role or service. In my case it's nova_compute. kolla looks good but the documentation isn't great, especially related maintenance and daily operations. On Tue, Jan 4, 2022 at 3:55 PM Satish Patel <satish.txt@gmail.com> wrote:
Thank you,
so just add this override in globals.yml correct? Do I need to destroy and recreate the container?
On Tue, Jan 4, 2022 at 3:39 PM Radosław Piliszek <radoslaw.piliszek@gmail.com> wrote:
You want to override "nova_instance_datadir_volume" to point to your mount path, in this case /mnt
-yoctozepto
On Tue, 4 Jan 2022 at 21:31, Satish Patel <satish.txt@gmail.com> wrote:
Folks,
Recently I have started playing with the Openstack Kolla Project because of some requirements. I want to integrate kolla with GlusterFS for nova vm backend storage.
I have functional Glsuter storage and want to mount on compute node to use for vm backend but not sure how do i do that because i am new to containers
I can see kolla use following to bind volume with nova_compute container
{ "Type": "volume", "Name": "nova_compute", "Source": "/var/lib/docker/volumes/nova_compute/_data", "Destination": "/var/lib/nova", "Driver": "local", "Mode": "rw", "RW": true, "Propagation": "" }
If I can mount GlusterFS in /mnt directory then how do I tell docker to use /mnt to create volume for nova_compute?