Hello, I am a systems engineer for a mid sized ISP. I have been mostly a VMware/Vsphere admin going back to 2007 back in my enterprise days. Even played with XEN project a bit prior to jumping into ESX. I started using xcp-ng in my personal lab to prototype cloud-init scripts, Ansible playbooks and other IaC toolstacks, and to have a solid reliable virtualization stack to run my hosted apps, email, and websites. Thanks to the xcp-ng team for such a stable and easy to use system! The support is top notch!
Dj
Best posts made by dj423
-
RE: Introduce yourself!
-
Cloud-init success
I thought I would share some success with cloud-init. I know it has been a pain for others to get working. Please disregard if this is old news.
Just for fun, I wanted to see if I could just use the stock/prebuilt Ubuntu 22.04-LTS cloud ready images I have used in production. Almost like magic it worked fantastic. I expected hours of pain and debugging like others have had to suffer. However to it took me about 2 minutes to spin up a fully configured Ubuntu VM with all my PKI keys, users, updates, packages, configs, etc.
So here is what I did, just in case this is helpful for any other noobies like myself getting acquainted with XO and using cloud-init.
So I used the prebuilt cloud image for Ubuntu found here: https://cloud-images.ubuntu.com/jammy/current/
Step 1:
I selected the "jammy-server-cloudimg-amd64.ova" stock file for vmware/virtual box and downloaded.Step 2:
Then in XO, I imported the file as a VM - import - VM.Step 3:
Then I went into settings, and created a new cloud config with my usual user, ssh, packages, and other custom settings as I normally use in the lab for testing prior to rolling into production. I just copy/pasted my full config, and saved it.Step 4:
Then I converted the cloud image VM I imported in step 2 into a template.Step 5:
Then I created a fresh VM, using this new template, making sure to select my cloud-init config by checking the "Custom config" selection under Install settings.Step 6:
Then I opened the console to watch for FAIL errors. Everything looked good. Then I logged in with my ansible account configured in the cloud-init. Then I tested from my ansible control node, and logged in. I inspected /var/log/cloud-init.log for any errors, and finally I ran "cloud-init query userdata" to see how it rendered the config settings. Everything works as it should.Next I will try the cloud-init config with jinja2 template directives and see if the jinja engine works as well, so I can use one config for all distros I will be using. Then test network config settings. Then test on Centos, Rocky, RHEL cloud-ready images and report back if I run into any snags on those.
-
RE: Virtualbox OVA import an option?
@olivierlambert
Yes. It should be said, that XCP-ng FAR exceeds my expectations! No matter what I throw at it, it just works fantastic. -
RE: Virtualbox OVA import an option?
Update: In case anyone runs across this OVA/app, It imported fine, with no issues at all. I did not end up running it since the apps fell short of my expectations, but the process of importing it worked flawlessly.
Have a great day!
-
RE: Virtualbox OVA import an option?
@olivierlambert
Ok thanks Oliver! I will report back how it goes. -
RE: Backup - Error: Lock file is already being held
@olivierlambert
Got it, sorry I glossed right over the updates. Ran the updates and everything is green with success. Thanks for taking the time to answer my noob questions!