Posts made by BenjiReis

@gskger Thanks for the report! This is greatly appreciated!

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.

Hi all!

A new ISO is available here to test IPv6 in dom0.
Whats new:

• aligned patches with Citrix upstream merges
• fix regardings tunnels, Sriovs network, VLAN and bonds when creating from IPv6 PIF
• netinstall support in IPv6 (netinstall repo info coming soon)
• NFS support in an IPv6 Pool

Do not use this in production this is an experimental feature!

What to test?

• upgrade from an already configured IPv6 host
• netinstall when a repo will be available
• what you'd normally do with an xcp-ng host

For fresh installs, do not forget to add the ipv6 rpm repo for future updates:

[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

For existing IPv6 hosts, yum update --disablerepo=* --enablerepo=xcp-ng-ipv6

@gskger Thanks for the report!

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.

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?

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!

A new version has been released last week or so that solves issues in the recipe.
Did you encounter any issue with latest xoa?

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.

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!

@pnunn Yeah please open a ticket and a tunnel, I'll have a look.

Please make sure to add the xoa ssh key to the VMs so I can ssh to the nodes and master.