I understand the metadata service is not supported with VDS-only deployments. Does this mean that cloud-init and cloud-config do not work with VDS-only deployments?
I want to be able to use cloud-config when launching instances to point to a puppet master.
Thanks. Does this mean cloud-init and cloud-config are not supported in VDS-only mode?
Are you using the DVS plugin from vmware-nsx/vmware_nsx at master · openstack/vmware-nsx · GitHub? If so then cloud init is supported.
There were some bugs where the DHCP agent were not connecting to the correct OVS swicth. That was fixed in Newton.
Thanks. This looks like it needs to be used with NSX. Is that correct? Even if it can be used without NSX, looking at the links, I have no idea where to start. How do I install this plugin?
I tried using the following command but it didn't seem to work
nova boot --image ubuntu-cloud --flavor 2 ubuntu-cloud3 --config-drive=true --user-data ./mydata.txt --net-id fff67509-3269-4d50-b57e-381b2801cb22
I saw cloud-init was trying to reach 22.214.171.124 during instance boot, but the config-drive was never mounted (tried viewing with df and mount after boot). The file mydata.txt only had the following as a test:
echo "Hello World. The time is now $(date -R)!" >> /tmp/output.txt
I reviewed the cloud-init logs in /var/log but didn't see anything that looked like it tried to use or mount the config-drive.
I'm not convinced that cloud-init or config-drive are supported at all with a VDS-only VIO deployment. Can anyone say otherwise?