@bcatubig

I see this message on the console right after the VM is created. Could it be somehow helpful?

@bcatubig it didn't help. would you mind to share the config that is working for you?

@bcatubig yes I did. I've just followed your instructions above. Also the fact the cloud-init logs are present indicates that it is running, isn't it?

@bcatubig yes ConfigDrive and only ConfigDrive is enabled. My script does 3 things: SSH, set hostname, and touch some file. None of them is executed and the cloud-init logs doesn't show any trace of the execution.

#cloud-init

hostname: {name}%

ssh_authorized_keys:
  - ssh-rsa AAAA...kd mykey@myhost

runcmd:
 - [ touch, "/tmp/CLOUD_INIT_WAS_HERE", / ]
 - touch /tmp/CLOUD_INIT_WAS_HERE_1
 - touch "/tmp/CLOUD_INIT_WAS_HERE_2"

@olivierlambert done: https://github.com/terra-farm/terraform-provider-xenorchestra/issues/28
thanks!

moisei created this issue in terra-farm/terraform-provider-xenorchestra

closed add name_description for the disk #28

@bcatubig I've done all the magic but still my cloud init is not taken into account completely.
I can see the VM is created with 10 MB additional disk.
I can mount this device and see that it does contain my cloud-init script.
but the script is not executed and cloud-config logs don't contain any useful information.
Please advise what would be the right way to track this issue??

Would be nice to have an option to specify disk description in the terraform script.
Something like:

resource "xenorchestra_vm" "vm1" {
...
 disk {
    sr_id      = "111111111-22222-333-444-555555555"
    name_label = var.vm_name
    name_description = "MY DISK DESCRIPTION"
    size = 21474836480
  }
}

Thank you.