Posts made by mietek

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

• Install Debian 10.6 with xo-tools
• install cloud-init and cloud-initramfs-growroot
• remove all network configuration leave just "allow-hotplug ethxxx"
  (network config will be added in /etc/network/interfaces/50-cloud-init. It will not overwrite yours)
• shutdown the machine and create the template if you want or just restart VM.
• DO NOT LET IT BOOT! - keep it in grub.
• attach your iso
• let it run

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:

1. 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.

2. 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

flipsa created this issue in vatesfr/xen-orchestra

open Cloud-init NoCloud block device has wrong dosfslabel --> cloud-init can't find datasource and exits #4449

Hey gents were you able to find the root cause for this issue?
I see the same problem on Debian 10.

• I can see XO providing xvdb with all of the data. I can mount it and see all the info as expected.
• I am able to start cloud init (systemctl start cloud-init) and all changes from user-data provided are done to the system not from network though (but that might be an expected behaviour as the system is running already?)
• That being said - nothing happens on the VM boot.

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.

Gents [ @olivierlambert @fohdeesha], let me reply to both of you and finish this unfortunate (part of) the discussion.
It took this drastic downturn and I am not enjoying it at all [!] as both you as well.

Your active engaged in community forum is admirable and I mean it! (especially because of your position, Olivier).
I was directed to XO project because of very favorable opinions about the support and robust community.

That being said - please do not hold it against me though that I am disappointed that I received answers which were not helpful.
You do not have to have malicious intent to do so and that is - unfortunately - my experience.
I can see though how my post might be read this way - I could phrase it better - my bad! I am sorry - that inappropriate.

To end up this negative chain - I respect you guys and it was not my intention to make it such a sour experience for everyone.
If I may propose one thing though - If you reply to the post with X number of questions try to reply to all of them.
Even if that would be just one sentence that would put requestor on the right path. That would be very appreciated.

Going back to the cloud-init itself.
Explanation that it caused a lot o issues in the past very well explains my experience with it and feel that I got from XO and cloud-init implementation of it.

1. is default config for NoCloud "should" make VM responsive to it or there are some additional steps I should go through?
   (I will be going back to testing with CentOS before trying Deb 10 just to be sure I am working on something that I may expect to work)
2. do you support or plan to support Ignition or another project that would do the trick of on-the-fly config for cloud purposes?
3. (if you do) is there any documentation for it?

Thanks for help and have a good one, Gents!

@fohdeesha Thanks for the answer. I will test is with the new Deb 10 version.

@olivierlambert

1. First of all Thanks for the link to the Xen Documentation it is helpful.
2. ".. You aren't alone in the world"
   From what I see is that you have replied to me for the first time the same day I have posted my question. Although your answered just one question regarding cloud image - nothing about creating it from scratch. Even though I continued asking about it it took you another 6 days to reply. Then when you provided me with the link to the Debian bug I found that you knew about that issue being involved in discussions about it for almost a year now.
   To summarise

• you knew I will be struggling - because of the Debian bug
• you never provided me with the data sources even though I asked about it explicitly
• after that you directed me to Debian 8 manual which is irrelevant to Debian 10 (even though you knew there is a bug in Debian 10)
• and as a cherry on the top you've told me to "google it".
• you have provided me with the link to the Debian bug 9 days after my initial question only when I raised my concern and disappointment.

From my point of view you were deliberately not answering my questions which just proves that you never wanted to help quite the contrary ... and this IS truly disappointing my friend!

Is there anyone who is able to answer my questions?

• You are referring me to outdated, unusable and even misleading dock
  [as far I can see Xen changed cloud-init datasource from "OpenStack Config Drive" to "NoCloud" at lease as a main one:
  https://xen-orchestra.com/forum/topic/1315/cloud-init-from-templates-do-not-read-local-datasource

• XEN documentation is unavailable [404]:
  https://xen-orchestra.com/docs/cloudinit.html

• I hope the network issues were resolved:
  https://xcp-ng.org/forum/topic/2256/cloudinit-network-config-is-being-saved-in-the-config-drive-but-its-not-being-applied/4

• To hear this kind of comment on the official forum is just pure gold:
  "but most of what's require to do is available on Google"

You gents need a proper manual/documentation because as of now it's just a slipshod work.
All of this is just so disappointing ...

@fohdeesha : may I ask you to provide me with the answers to my questions (see above) / prequisits regarding preparing Debian 10 VM for template for cloud-init please?

Thanks Olivier. I will wait for @fohdeesha then as my list of questions is based on that blog post which unfortunately does not apply to Debian 10.

I have XO that is why I have no access to it (I have an option to upgrade it though) - thanks @tony .

Still my question remains - is there a manual to do it from scratch or at least requirement list?

• packages (obviously) : cloud-init and cloud-initramfs-growroot
• sources:
  • "OpenStack Config Drive"? (as mentioned here: https://xen-orchestra.com/blog/debian-cloud-template-for-xenserver/)
    So OpenStack or Config Drive (now there are separate)
    https://cloudinit.readthedocs.io/en/latest/topics/datasources/configdrive.html
  • NoData - or NoData as I have seen somewhere
• dpkg-reconfigure cloud-init is giving you nothing in Debian 10 so you will have to set it up manually I guess.
  Are there any tips on that then?
• should cloud-init run as a demon? (enabled and running via systemd)
• anything else?

That would be very helpful to have this sorted as probably I am not the only one who for whatever reason is not able or wants to use XOA.

Thanks for help.

Hey Olivier,
Thanks for the info. I have access to free plan although I cannot find HUB category there. Is this only for non-free plans?

Is there a manual how to prepare Debian 10 template from the scratch to make it work with XO?

Gents,

1. where can I find a debian 10 cloud ready template for XO
2. is there a manual for creating it from scratch?

I am trying to build customs VMs with XO but it fails to pass any config data to the new VM (created from template) probably because of configuration mistakes when preparing VM for template.

Thanks for help

PS. I found this but it needs to be updated for debian 10 and newer version on XO and links do not work anymore:
https://xen-orchestra.com/blog/full-cloudinit-power-in-xenserver/