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!

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.

@Fungusware Hi!

Yes this feature is supported at XAPI level, the VM.snapshot method now has a ignore_vdis field which is a list of VDI ref to not include in the snapshot.
This also available through xe:

xe vm-snapshot vm=... ignore-vdi-uuids=uuid1,uuid2...

Regards

Hi all!

8.2.1 IPv6 ISO available!

Here's a new ISO for IPv6 based on XCP-ng 8.2.1!
The ISO can be used to upgrade an existing server installed with the previous IPv6 test ISO or install a brand new XCP-ng 8.2.1 with IPv6 support on management interface.

A non-IPv6 8.2.0 would remain non-IPv6 after an upgrade as it's not possible to edit the management interface's primary adress type.

An 8.2.0 IPv6 hosts can also be upgraded via yum: yum upgrade --enablerepo=xcp-ng-updates,xcp-ng-ipv6.

What's new

• All 8.2.1 fixes
• Better DNS management in the case of both IPv4 and IPv6 configured on a PIF
• Partial support of IPv6 DHCP and autoconf

What to test

• Your daily uses of XCP-ng but with IPv6
• DHCP and autoconf (I have reached the limits of my knowledge so help from the community with more IPv6 expertise would be very VERY VERY helpful! :D)
  The goal of this ISO release is mainly to get help and leads about what's missing in DHCP and Autoconf.

Any issue encountered (and what works fine also) can be reported in this thread.

Usual warning

This a test ISO with an experimental feature still in development.
IPv6 on management interface is not officially supported by XCP-ng yet and so, we do not recommend to use it for a production environment.

Thanks a lot for the help and I hope the ISO will work well for everyone.

New xsconsole fix to test for 8.2

New update candidate are available for testing and due to be released as official updates.

Original topic:

• https://xcp-ng.org/forum/topic/3886/xcp-ng-8-2-dns-settings-gone-after-reboot
• https://xcp-ng.org/forum/topic/3277/dns-config-on-8-1-hosts-disappearing

yum clean metadata --enablerepo=xcp-ng-testing
yum update xsconsole --enablerepo=xcp-ng-testing
systemctl restart xsconsole.service 

What to test

Changing the DNS settings from the XSConsole and the change is retain after a reboot.

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.

@AtaxyaNetwork thanks for the report.

I reproduced the issue, for some reason at first boot XCP-ng launch an IPv4 dhclient request (even though IPv4 is not configured on the management interface...) which overrides the DNS set after the request is replied to.

Hi all! Long time no see ^^

I'm glad to say i'm back on IPv6 and will (soon-ish) provide a new IPv6 iso to test XCP-ng with an IPv6 management interface.
I've made some fixes to DNS management.

Before the new ISO i'd like to support ideally DHCPv6 and autoconf.
For now I managed to :

• sometimes have an IP with DHCPv6 and sometimes a DNS - no gateway but it's exepected with stateless DHCPv6.
• Have an IP with Autoconf - No Gateway & no DNS

I'm looking for help as my field of expertise is more ocaml dev than IPv6.
I'm thinking especially of @AtaxyaNetwork and @bnerickson that I know have more knowledge than me for IPv6. Any help from a forum users would be greatly appreciated.

For DHCPv6 this is the conf of dhclient:

interface "xenbr0" {
  send fqdn.fqdn = gethostname();
  request subnet-mask, broadcast-address, time-offset, host-name, interface-mtu, dhcp6.nis-servers, dhcp6.nisp-servers, nis-domain-name, nisp-domain-name, dhcp6.sntp-servers, dhcp6.fqdn, routers, dhcp6.domain-search, dhcp6.name-servers;
}

For Autoconf here's what's done:

/sbin/sysctl -q -w net.ipv6.conf.xenbr0.autoconf=1
/sbin/sysctl -q -w net.ipv6.conf.xenbr0.accept_ra=1

Am I missing something obvious? I can provide more info if requested.
Also I can made available a test iso before the real one but it'd be really a experimental ISO.

Thanks!

a little recap of the thread for anyone who'd like to help us by testing the feature.

XCP-ng IPv6 recap

A test ISO is available to test a new feature: having your XCP-ng hosts with an IPv6 management interface.

To have an IPv6 host, you must either install a new host or upgrade one with the test ISO.

More info on the dedicated blogpost
Please give any feedback in this thread!

Known limitations

• IPv6 Static only for now
• HA not tested yet
• Dual stack (both IPv4 and IPv6) can lead to DNS issues and the host will use IPv4 for its XAPI operations.

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.

Thanks!

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

in /etc/yum.repo.d/xcp-ng.repo.

@kiu I reproduced your issue.

The issue comes from a lib used by xscontainer as a SSH Client which use a deprecated algo ssh-rsa so all modern (>=8.7) OpenSSH reject the connexion.

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.

Yes it's 5396b90695fbe2c7a5f56d72a94a208517b2d517 but its not its only modification so it can't just be reverted.
This is a really quick fix I can push a branch today and it can be used waiting for the merge.