FYI If you are looking for more info on the matter yourself ...
ver: 20.2-2 of the cloud-init is still the one with the bug mentioned by @olivierlambert earlier:
https://github.com/vatesfr/xen-orchestra/issues/4449
There is version 20.3 awaiting to be delivered but still awaiting to be packaged:
https://tracker.debian.org/pkg/cloud-init
I was able to find the reason XO is not working with cloud-init.
XO attaches iso with the cloud-config data as additional disk xvdb and it does not work.
But if you provide it as a cd? It will.
That is why - as for now you will need to create your own iso and attach it as a cd-rom.
You do that this way:
Get your files ready (meta-data network-config user-data). My examples below:
metadata:
instance-id: local-nocloud
local-hostname: myhost.example.com
network-config:
network:
version: 1
config:
- type: physical
name: eth0
subnets:
- type: static
address: 10.0.0.5/24
gateway: 10.0.0.254
- type: nameserver
address:
- 8.8.8.8
- 8.8.4.4
search:
- example.com
- type: physical
name: eth1
subnets:
- type: static
address: 192.168.0.5/24
user-data:
#cloud-config
### RUN CMD
runcmd:
- /usr/bin/apt -y install mc
- /usr/bin/date >> /root/testfile
# set system default user
system_info:
default_user:
name: testuser
gecos: Default Cloud User
# password auth - comment out if not using passwords
password: testpassword
ssh_pwauth: true
chpasswd: { expire: false }
# do some package management
#package_update: true
packages:
- iptraf
- mtr
- screen
- net-tools
- atop
Generate iso
genisoimage -output myiso.iso -volid cidata -joliet -rock user-data meta-data network-config
Upload iso to XO
home -> storage -> iso's -> disks -> new disk
Prepare VM/template
It will do whatever you need on the machine.
This is a great news as I will be able to have all my scripts written as of now and xo-cli in one place.
Thanks @olivierlambert
For those who are looking for direct instructions ... on Debian 10.x:
# install npm:
apt install npm
# install xo-cli:
npm install -g xo-cli
I was able to find the reason XO is not working with cloud-init.
XO attaches iso with the cloud-config data as additional disk xvdb and it does not work.
But if you provide it as a cd? It will.
That is why - as for now you will need to create your own iso and attach it as a cd-rom.
You do that this way:
Get your files ready (meta-data network-config user-data). My examples below:
metadata:
instance-id: local-nocloud
local-hostname: myhost.example.com
network-config:
network:
version: 1
config:
- type: physical
name: eth0
subnets:
- type: static
address: 10.0.0.5/24
gateway: 10.0.0.254
- type: nameserver
address:
- 8.8.8.8
- 8.8.4.4
search:
- example.com
- type: physical
name: eth1
subnets:
- type: static
address: 192.168.0.5/24
user-data:
#cloud-config
### RUN CMD
runcmd:
- /usr/bin/apt -y install mc
- /usr/bin/date >> /root/testfile
# set system default user
system_info:
default_user:
name: testuser
gecos: Default Cloud User
# password auth - comment out if not using passwords
password: testpassword
ssh_pwauth: true
chpasswd: { expire: false }
# do some package management
#package_update: true
packages:
- iptraf
- mtr
- screen
- net-tools
- atop
Generate iso
genisoimage -output myiso.iso -volid cidata -joliet -rock user-data meta-data network-config
Upload iso to XO
home -> storage -> iso's -> disks -> new disk
Prepare VM/template
It will do whatever you need on the machine.
This is a great news as I will be able to have all my scripts written as of now and xo-cli in one place.
Thanks @olivierlambert
For those who are looking for direct instructions ... on Debian 10.x:
# install npm:
apt install npm
# install xo-cli:
npm install -g xo-cli
following this xo-cli thread though - is there a possibility to install xo-cli on the server which is not a xen server? Or it has to be the one and even more - the one with xen-orchestra?
OK - found the problem.
I do not need to add CD I need to insert it.
xe vm-cd-insert vm=<name_of_your_vm> cd-name=<name_of_your_file.iso>
If xe will say that there is no empty cdrom - eject inserted media:
xe vm-cd-eject vm=<name_of_your_vm>
and then insert it ...
Thanks @olivierlambert - I will try that just to compare maybe it will give me results I need.
Hi all,
I am having issues with cd images attaching to the template created.
I need this for the cloud-init configuration.
There are 2 ways I try to accomplish that on freshly created Debian 10 template with cloud-init packages installed:
I create new vm in XO and boot it. I stop it on grub level, then I attach my cd image with cloud-init user, meta and network data in XO, continue with the boot - cloud-init works as expected.
I create vm in CLI:
xe vm-install new-name-label=<vm_name> template=Debian10_cloud-init_template
xe vm-cd-add vm=Debian10_cloud-init_template cd-name=nciso11.iso device=4
xe vm-start vm=Debian10_cloud-init_template
and cloud-init does not work, cd is not moutable as it says that there is noting to mount.
Only difference I see is that when I create VM in XO I got two cd devices:
CD 0 VBD:
uuid ( RO) : 7663f608-efdd-38e0-581a-87d2a21da3fc
vm-name-label ( RO): Debian_10_cloud_init_template
empty ( RO): false
userdevice ( RW): 3
CD 0 VDI:
uuid ( RO) : 105c96fb-0d1f-4df3-bf6e-e8edf51ee78a
name-label ( RW): nciso11.iso
sr-name-label ( RO): ISO's
virtual-size ( RO): 376832
When I create it in CLI I have 3 fore some reason:
CD 0 VBD:
uuid ( RO) : 3f18cca9-2630-0e2f-d146-ddd1f716ea65
vm-name-label ( RO): Debian_10_cloud_init_template
empty ( RO): false
userdevice ( RW): 4
CD 0 VDI:
uuid ( RO) : 105c96fb-0d1f-4df3-bf6e-e8edf51ee78a
name-label ( RW): nciso11.iso
sr-name-label ( RO): ISO's
virtual-size ( RO): 376832
CD 1 VBD:
uuid ( RO) : d28e5090-4e2c-cbaf-fbab-4ccbdd54c3ca
vm-name-label ( RO): Debian_10_cloud_init_template
empty ( RO): true
userdevice ( RW): 3
... and then coud-init does not work as cd is not mountable - no media (???).
Could someone explain to me why CLI creates additional and empty CD? Thanks!
Hey @p4-k4, thank you for the clarification. Appreciate it.
I've tested that last week based on your post but it does not work for me with or withough network config present for some reason. (DS not found either way).
I am thinking about preparing a vm template with manually patched cloud-init. I will be trying that approach this week. I will post if I'll find a temp solution for this.
Cheers!
FYI If you are looking for more info on the matter yourself ...
ver: 20.2-2 of the cloud-init is still the one with the bug mentioned by @olivierlambert earlier:
https://github.com/vatesfr/xen-orchestra/issues/4449
There is version 20.3 awaiting to be delivered but still awaiting to be packaged:
https://tracker.debian.org/pkg/cloud-init
Hey gents were you able to find the root cause for this issue?
I see the same problem on Debian 10.
I have checked systemd and cloud-init is enabled so all should run on the boot but for some reason it is not.
There are no log files as cloud-init is not able to find datasource:
[from /run/cloud-init/cloud-init-generator.log]
"cloud-init is enabled but no datasource found, disabling"
In my case there is no difference if the network text box in XO is empty or not or just first two lines are unhashaed.
I am using fully updated ver of debian 10 and XO 5.59.0
I assume Debian bug about not recognizing disk should be fixed already (?).
Cloud-init ver. 20.2-2.
Any tips on what am I missing?
Thanks
EDIT: looks like still bug was not fixed.
I have checked as mentioned in below manual and it's still marks /dev/xvdb wrong ...
https://www.gitmemory.com/issue/vatesfr/xen-orchestra/4449/614872988
ver: 20.2-2 is still the one with a bug. There is 20.3 awaiting to be delivered but still awaiting to be packaged:
https://tracker.debian.org/pkg/cloud-init
Great - thanks for the info @fohdeesha.