Questions on zfs-local-dataset driver with Nomad

1. Is it possible to supply ZFS properties for dataset when creating a volume? I see it can be done with zfs-ephemeral driver (using volume_context and property.<name>) but have not found I way to do that with zfs-local-dataset
2. How can I specify on which host dataset should be created? It seems that now volume is created on the Nomad client that receives the call to create a volume.

Deletion also doesn’t seem to work when request to delete lands on node that doesn’t have a dataset. What I mean is that if I have nodes node-01 and node-02, when I create a volume with NOMAD_ADDR=node-01:4646 nomad volume create test.hcl dataset will be created at node-01 and when I run NOMAD_ADDR=node-02:4646 nomad volume delete test volume will be deleted from Nomad but dataset will stay at node-01.

[nahsi]

Thank you for very detailed anwser! I understand. I will experiment with democratic-csi on Nomad, based on what I’ve learned from you, and will share the result here. And perhaps will update the docs later if all is nice.

[travisghansen]

Those are https://handlebarsjs.com/ templates so you may be able to do something like this:

{{#if someval}}{{ someval }}{{else}}{{"default"}}{{/if}}

The code should probably detect empty values generally and ignore them but that could end up hiding issues that operators would like to see.