Subcategories

• Management

  VMs, hosts, pools, networks and all other usual management tasks.
  487 Topics

  4k Posts

  T

  @carloum70 Sorry, that option was deprecated. You may need to be more specific in the reset, something like the following with is just an example: xe-reset-networking -m IP_of_Master --device=eth0 --mode=static --ip=192.168.1.50 --netmask=255.255.255.0 --gateway=192.168.1.1 --dns=192.168.1.254 Check the options and see which ones you actually need in your case. Worst case, you could possibly dissolve the bond, redo the PMI and then re-create the bond. WHy eth4 shows up is hard to guess. I have seen before that on some hosts in a pool that the NIC order was not the same, even though the hardware and OS versions were identical. In that case, you have to shut down the NICs and use interface-rename to reassign specific NIC names to the corresponding MAC addresses.
• Advanced features

  ACLs, Self-service, Cloud-init, Load balancing...
  106 Topics

  870 Posts

  D

  I ran into the same problem with DR replicas. Ignoring VMs by tag would solve the problem, but so would excluding the ip address information.
• Backup

  All XO backup features: full and incremental, replication, mirrors...
  534 Topics

  6k Posts

  J

  Wonderful !
• REST API

  Everything related to Xen Orchestra's REST API
  88 Topics

  654 Posts

  P

  Pretty cool, @samuelolavo, thanks for clarifying!
• Infrastructure as Code

  Terraform, Packer or any tool to do IaC
  52 Topics

  488 Posts

  C

  New release ! Cloud Controller Manager v1.2.0 https://github.com/vatesfr/xenorchestra-cloud-controller-manager/releases/tag/v1.2.0 Adds a new cloud-node-out-of-service controller that applies the node.kubernetes.io/out-of-service=nodeshutdown:NoExecute taint to the nodes whose Xen Orchestra VM is halted or has been deleted. More about this feature in the documentation or #90