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.
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:
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!
New update candidate are available for testing and due to be released as official updates.
yum clean metadata --enablerepo=xcp-ng-testing yum update xsconsole --enablerepo=xcp-ng-testing systemctl restart xsconsole.service
Changing the DNS settings from the XSConsole and the change is retain after a reboot.
Experimental feature: select a network to evacuate an host
A new feature is available in our testing repo: select a network for host evacuation, this would allow to evacuate an host on any (faster) given network instead of the management one.
To access the feature, on all your hosts (always starting with master when in a pool):
yum update --enablerepo=xcp-ng-testing xapi-core-1.249.5-1.1.0.evacnet.1.xcpng8.2.x86_64 xapi-xe-1.249.5-1.1.0.evacnet.1.xcpng8.2.x86_64 xapi-tests-1.249.5-1.1.0.evacnet.1.xcpng8.2.x86_64
And restart your hosts.
WHAT TO TEST
Host evacuation not on the management network (probably a 10G storage network to go faster!)
You can run
xe host-evacuate host=<host_uuid> network-uuid=<network_uuid>
Or a XAPI client can call
host.evacuate with a
network ref parameter.
Host evacuation without the optionnal new parameter should behave as before the update.
Please report here if anything goes wrong (or right hopefully ) and if you spot a regression as well.
Edit: there are no plans for now to add this feature in 8.2 LTS, the package will probably stay in the testing repo for 8.2 and will be available in 8.3. It means that the package would be erased at next xapi update.
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
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!