Hello everyone,
I'm also a new contributer to XCP-ng!
For now I'll be working with @ronan-a on the SMAPIv3 plugins.
After that probably on open vSwitch.
Benjamin
Hello everyone,
I'm also a new contributer to XCP-ng!
For now I'll be working with @ronan-a on the SMAPIv3 plugins.
After that probably on open vSwitch.
Benjamin
Hi all!
After 4 months of effort we are very happy to provide a 1st test ISO with IPv6 support in XCP-ng dom0.
Read our devblog here: https://xcp-ng.org/blog/2021/02/09/ipv6-in-xcp-ng/
The ISO is available here and the corresponding SHA is: 177eade2efa8b6c989847c970e5cab3e6eb24de5a2eef153a0fc422071f9234b
.
Keep in mind this is a test ISO so do NOT use it in production and please report in this thread if you encounter any issue or if your tests are going well.
The devblog contains the known limitation of the ISO, updates will be provided in this thread when fixes and features are available.
I hope you'll have fun with it!
Good news, ISCSI shared storage already works in IPv6 with no package update!
An update will be released in the coming weeks for NFS support in the IPv6 case!
Has anyone play with the ISO? Any kind of feedback is very welcomed!
First update available!
The xsconsole rpm can be updated via: yum update --disablerepo='*' --enablerepo=ipv6 xsconsole
.
The issue fixed was that the DNS couldn't modified via XSConsole when configured in static IPv6, it's now possible.
Just realised the IPv6 rpm repo isn't configured in the ISO... ^^'
so just add:
[xcp-ng-ipv6]
name=XCP-ng IPv6 Repository
baseurl=http://mirrors.xcp-ng.org/8/8.2/ipv6/x86_64/ http://updates.xcp-ng.org/8/8.2/ipv6/x86_64/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-xcpng
in /etc/yum.repo.d/xcp-ng.repo
.
Hi!
In your Pool view there's a network tab where you can rename your networks by clicking on their name and enter a new one.
Regards.
The issue has been fixed on this branch, it'll be merged into master soon.
Perfect, see you on monday on the support ticket then!
Meanwhile, have a nice week end
Hello,
The DNS names of the master (and nodes also with a pattern) should be configurable for the user indeed. We'll add it in a next version of the recipe.
Thanks for the feedback!
Hi!
The fix is available on master
.
You should be able to generate certificate now.
Just realised the IPv6 rpm repo isn't configured in the ISO... ^^'
so just add:
[xcp-ng-ipv6]
name=XCP-ng IPv6 Repository
baseurl=http://mirrors.xcp-ng.org/8/8.2/ipv6/x86_64/ http://updates.xcp-ng.org/8/8.2/ipv6/x86_64/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-xcpng
in /etc/yum.repo.d/xcp-ng.repo
.
@mathiashedberg good to know.
So you can wait for the fix or remove the xo:resource:xva:id
from the other_configs
of the snapshots or remove the snapshots
Okay so a fix is coming soon, i'll update here once released.
@olivierlambert should I also check that is-a-snapshot
is false?
@mathiashedberg the snaphots might be indeed the problem.
When looking for the template, the recipe looks for a VM with xo:resource:xva:id=<template uuid>
in its other-config
, a snapshot of the template VM would probably have this field se and it should not.
Can you check if it's the case? and if the is-template
field is true
.
I do not understand how the wrong templates can be used by the recipe.
Weird, which templates appear in your Hub view?
Your VM should have 2G of RAM. Base on our Debian 10 template.
This is really weird.
That's weird, I've just ran the recipe and everything went fine.
Do you have any network issues explaining the installation problem?
debian@master:~$ sudo systemctl status cloud-final.service
ā cloud-final.service - Execute cloud user/final scripts
Loaded: loaded (/lib/systemd/system/cloud-final.service; enabled; vendor preset: enabled)
Active: active (exited) since Mon 2021-02-15 09:47:38 EST; 14min ago
Process: 558 ExecStart=/usr/bin/cloud-init modules --mode=final (code=exited, status=0/SUCCESS)
Main PID: 558 (code=exited, status=0/SUCCESS)
Latest XOA is 5.55.1, can you try with this version?