@olivierlambert

The purpose of the exercise is to get the new host updated with identical packages/updates to match the pool master

Am I correct in saying that when "Install all patches" is selected on the new host, it will resolve the db_schema mismatch and still be able to successfully join the pool?

Unless the new host has more updates afterwards than the pool master and won't be able to join the pool?

@lawrencesystems
Thank you for the reply!
I considered BHC in the past, wasn't sure to how big to make the SR for the restores

BTW Love your XCP YT content, helped me understand so many features and best practices

I suppose this is just a general question regarding Backup Health Checks

The BHC enabled on a delta backup (rough process):
Delta/Full Backup > restore VM >check for guest tools > shutdown >delete the VM

The restored VM is deleted after each test or are all deleted after the entire delta backup completes?

@olivierlambert

Hahaha you got it! Thank you

Good day everyone

Hope y'all are well

A reseller of ours want to download their VM snapshot and they lack the necessary permissions

Currently their group and user are assigned to their VMs with the Operator role in ACL

I am aware I can pass along the download link to them from my side, they'd prefer to do it themselves as needed

Is there a way to create another user/group/role or edit existing ones with that permission

Thank you!

Hi there Gsrfan

Apologies for the delayed response, I had to shelf this passion project to focus on other work
So far managed to get the host, static IP, packages, users & their keys/password etc sorted with the init

I was working last on lvm partitions, to grow them and that ended up a bit of a mess

I might return to this at a later stage but I found your help and advice invaluable to getting the config to where it is now

Thank you so much

@rajudm
Hi there

We just need some more info from your side
What error did you get?
Which distro are you using to deploy the VMs?

@gsrfan01
Good day Gsrfan

I have managed to get the network going using your example network init, thank you it helped a bunch!

So far I can't access the test VM, the default ubuntu user and my custom user don't accept the credentials.
I have seen online it's possible to define the ssh keys in the init, is it a simple enough alternative to Github?

Thank you

@gsrfan01
Hi there!

Thank you for taking the time to reply, I will try out your example inits

I initially went with setting up my own template since I have several golden disks to use

So you only use those above inits and don't modify cloud.cfg at all?

I appreciate the help!

Good day

Hope everyone is well

I have begun to look into using Cloud Config to make it a simpler process to push out new VMs

This is for Ubuntu 22.04, the only variables I'd want to input would be the hostname, a static IP, disk space and install specified packages

So far I managed to get the config template to install the VM with the custom hostname
I still have trouble getting the network config working and having the new VM make use of the entire assigned disk space. The new VM will only use the original template VM's disk space (10GBs) and not extend the volume with entered disk space value

My current network template:

#network:
  version: 1
config:
  - type: physical
    name: eth0
    subnets:
      type: static
      address: 129.232.201.212/26
      gateway: 129.232.201.193
dns_nameservers:
  - 8.8.8.8
  - 1.1.1.1

Current user config

#cloud-config
hostname: TEST
growpart:
    mode: 'on'
resize_rootfs: true
package_update: true
packages:
  - htop
  - whois

My process for creating the template:

1. Install Ubuntu 22.04
2. Install Guest tools
3. apt update && sudo apt upgrade
4. Reboot
5. apt purge cloud-init cloud-initramfs-dyn-netconf cloud-initramfs-copymods -y
6. rm -rf /etc/cloud/; rm -rf /var/lib/cloud/
7. apt update && apt full-upgrade -y
8. apt install cloud-initramfs-dyn-netconf cloud-initramfs-copymods cloud-initramfs-growroot -y
9. cloud-init clean

Remove/Clear the following:
10.a rm /etc/cloud/cloud.cfg.d/99-installer.cfg
10.b rm /etc/cloud/cloud.cfg.d/subiquity-disable-cloudinit-networking.cfg
10.c rm /etc/netplan/00-installer-config.yaml
10.d rm -rf /tmp/* && rm -rf /var/tmp/*
10.e rm -f /etc/ssh/ssh_host_*
10.f truncate -s 0 /etc/hostname && truncate -s 0 /etc/machine-id

11. Edit cloud.cfg
    Here I only commented out the default users, as the users I set won't need to change

12. apt autoremove && apt clean

13. cloud-init clean && cloud-init clean --logs

Shutdown and convert to template

I believe my error is the disk and network are not defined in cloud.cfg

Would anyone be able to assist with examples or suggest how to correctly define the volumes and network interface

I will happy to provide any additional information or logs

Thank you