XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    • Profile
    • Following 0
    • Followers 1
    • Topics 3
    • Shares 0
    • Posts 91
    • Groups 0
    bvitnikB Online
    1. Home
    2. bvitnik
    3. Posts

    Posts

    Recent Best Controversial
    • RE: New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client

      @benapetr Yep. My message is based on 2 days old commit. I've compiled the latest one and the list at the bottom is collapsable now. I don't see the down arrow on "Organization" and "Saved searches" icons though like in your screenshot:

      image.jpeg

      The next few things:

      • Saved searches is empty. By default, there are some useful built in saved searches.

      image.jpeg

      • When you select a pool, on the info panel to the right the "Default SR" shows an OpaqRef instead of SR name. Reference should be dereferenced.
      • A little bit nitpicking. Vertical spacing of the elements in the tree view is a little bit higher compared to xenadmin. It could be made smaller to pack more stuff on the screen but this is just visual preference.
      posted in News
      bvitnikB
      bvitnik
    • RE: New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client

      @benapetr Here are some more bugs:

      • Templates are still not sorted correctly in the tree view. User templates (blue) should go first then built in ones (yellow). Each group should be sorted alpabetically (see the screenshot).
      • Icons are back for categories (under the tree view) but elements should be left aligned. They look ugly when centered (screenshot).
      • Categories are still not collapsable to a single icon like shown in previous screenshots.
      • With the addition of horizontal scrollbar, there seems to be an ugly regression in tree view itself. The tree view is refreshed each 30 sec but while doing so, the tree is collapsed and then expanded. It's a little bit hard to explain but the tree just "jumps" in front of the eyes. This is particularly annoying while doing something in the tree view.
      • The New VM dialog, template selection section, now seems to be functionally identical, not visually though.

      image.jpeg

      posted in News
      bvitnikB
      bvitnik
    • RE: New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client

      @benapetr The thing @clip is talking about is when the bottom panel (under the tree) is resized vertically, or better said squished vertically, the elements of the list (Infrastructure, Objects...) get replaced by a single horizontal icon at the bottom, one by one:

      image.jpeg

      and even more

      image.jpeg

      posted in News
      bvitnikB
      bvitnik
    • RE: New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client

      @benapetr Do you have some way or script to quickly iterate build->test workflow locally? That is without building a package, then installing on a system then testing. I'm running Debian based system.

      posted in News
      bvitnikB
      bvitnik
    • RE: New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client

      @benapetr Great. Thanks!

      posted in News
      bvitnikB
      bvitnik
    • RE: New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client

      @benapetr One of the things I've noticed during my initial testing is that there is a problem in how VM templates are handled compared to xenadmin. Here are my observations:

      • Built in templates are shown with yellow icons in the tree view (if enabled with View -> Templates) and this seems to work as expected.
      • User made templates are also shown with yellow icon in the tree view which is wrong. They should be shown with blue icon and sorted before any built in templates.
      • VM snapshots are shown as VM templates with blue icons in the tree view. They should not be shown at all in the tree view. Additionally, they are shown under a host instead of a pool compared to other templates.
      • New VM dialog does not show VM template icons at all so it is hard to distinguish if they are builtin or user created or snapshots (which can be used as VM templates too). Snapshots are not shown in the list at all.
      • New VM dialog also does not sort the templates by name nor group per type (builtin, user, snapshot) so it is hard to find what you need.

      If I get some extra time, I will add some screenshots for comparison.

      posted in News
      bvitnikB
      bvitnik
    • RE: cloud-init Cloud Config use of {name}

      @bug-meister Yeah, I would say the "mechanism" is deprecated too. Getting this mechanism to work, either by using ansible-pull or by some clever scripting during the first boot, requires Ansible to be preinstalled on your VM templates. That just makes your VMs messy and bloated with additional stuff you only use once. Also, managing Ansible versions becomes more complex. If Ansible is installed from distro repositories, you will have all different versions of Ansible across different distros. If you use pip to install Ansible, it can mess up your system if Ansible dependencies are installed on a system level. You can use Python virtual environments to prevent that but requires additional managing.

      It's much better and much more practical to have Ansible installed and used from a single place - Control Node. That way you have one place, one OS, one Ansible version to think about. You already have a machine you are accessing your VMs from? Use that as a control node... unless it is Windows?

      posted in Infrastructure as Code
      bvitnikB
      bvitnik
    • RE: cloud-init Cloud Config use of {name}

      @bug-meister My opinion is that cloud-init should be used only for the most basic stuff like initial network configuration, initial user creation and credentials injection. As soon as you gain the ability to access the VM, some more robust configuration management solution like Ansible should take over.

      ansible-pull mechanism is in today's day and age effectively deprecated. Just run Ansible after the VM has been provisioned to apply the configuration. If you need to call Ansible as soon as VM is provisioned without any manual invocation, you can have Terraform provision the VM and call Ansible right after that. You can even use pure Ansible for both - provisioning, with my community.general.xenserver_guest module, and configuration. You just invoke Ansible once and everything will be done in one go. The only drawback is that my module does not support cloud-init so you would need some trickery to do the stuff.

      posted in Infrastructure as Code
      bvitnikB
      bvitnik
    • RE: cloud-init Cloud Config use of {name}

      @bug-meister Ah. That's cloud-init's support for templating user-data. The issue is that with these templates you only have access to the info available inside the VM itself. No outside data can be used for templating unless it is somehow passed to the VM (inject a file, set xenstore values...)

      posted in Infrastructure as Code
      bvitnikB
      bvitnik
    • RE: cloud-init Cloud Config use of {name}

      @bug-meister Nope. This is not Jinja nor any other kind of templating engine. This is a simple search-and-replace kind of implementation and is limited to name and %, the later being VM index. From the docs:

      Xen Orchestra offers the ability to insert variables such as the virtual machine name {name} or a virtual machine index %. However, the expressive power is limited to the graphical interface. For instance, it is not possible to build a series of virtual machines with complex values or from external data.

      Reference:

      • https://docs.xcp-ng.org/guides/create-use-custom-xcpng-ubuntu-templates/

      In other words, there is no advanced templating of cloud-init configuration but you could probably template it outside XenOrchestra and apply it via Terraform:

      • https://registry.terraform.io/providers/vatesfr/xenorchestra/latest/docs/resources/vm
      posted in Infrastructure as Code
      bvitnikB
      bvitnik
    • RE: XCP-ng 8.3 updates announcements and testing

      @TeddyAstie Thanks

      posted in News
      bvitnikB
      bvitnik
    • RE: XCP-ng 8.3 updates announcements and testing

      @gleh said:

      Disable Viridian in the "Other install media" template by default. As a reminder, Windows VMs must use Windows templates.

      What is the rationale for disabling Viridian? Does it have any negative effects for non Windows VMs?

      posted in News
      bvitnikB
      bvitnik
    • RE: HA causes reboot of xcp-ng nodes

      @carloum70 I can't really help you with anything specific but I must make a note that when analyzing network setup you must also take into account the Open vSwitch. Looking at the classic Linux networking, bridging and routing facilities is not enough to get you the full picture.

      For example, if I remember correctly, Active-Active bonding (non LACP) is implemented by Open vSwitch with so called balance-slb mode. This mode is not available with classic Linux kernel bonding options. What you are seeing (duplicated IPs) is maybe perfectly normal for this kind of setup with Open vSwitch.

      I would search for the cause of the issue somewhere else like network congestion. Heart beats are very sensitive to network congestion and can easily fail if you do not dedicate network links for this kind of traffic. If you are sharing the links over which heart beats are sent with some high traffic stuff (storage maybe?), it can easily make problems.

      UPDATE: unfortunately I don't have access to these kind of bonded setups any more so I can't check if the configuration differs in any way from yours. My home lab thingies are single network interface only.

      posted in Management
      bvitnikB
      bvitnik
    • RE: How to reliably determine VDI format (vhd, qcow2, raw) via XAPI across versions

      @dthenot Thanks a lot for the information. I did some more testing on my end and I've now noticed differences in handling VDI format across different SR types (local LVM and EXT). Should I expect even more differences across remote SR types like LVMoHBA or NFS or are these differences more like block based vs file system based SRs?

      Any way, it looks like I have to consult the following keys:

      • image-format
      • vdi_type
      • type

      In my tests, local EXT SRs tend to have only one of them, while local LVM SRs tend to have first two or all three, depends which one was used when creating the VDI.

      posted in Development
      bvitnikB
      bvitnik
    • RE: How to reliably determine VDI format (vhd, qcow2, raw) via XAPI across versions

      @dthenot Aaaaah, so it even depends on the SR type. That also explains the difference I'm seeing in my lab with 8.1 vs 8.3. The first one uses LVM backed SR and the other one uses file system (ext) backed SR.

      I'll have to investigate this a little bit more.

      Was image-format key added by you (XCP-ng team) and is specific to XCP-ng or was it used at any point in XenServer also?

      posted in Development
      bvitnikB
      bvitnik
    • How to reliably determine VDI format (vhd, qcow2, raw) via XAPI across versions

      Hi,

      It has come to my attention that in recent times there was some change in how VDI format is tracked in XAPI database, especially with arrival of QCOW2 support, first in XenServer (GFS2 SRs only) and then in XCP-ng 8.3 (other SR types).

      Currently, I have access to XCP-ng 8.1 and 8.3 (with latest updates) and I'm seeing these differences:

      XCP-ng 8.1:

      $ xe vdi-param-list uuid=SOMEUUID
      ...
                     sm-config (MRO): vdi_type: vhd
      ...
      

      XCP-ng 8.3:

      $ xe vdi-param-list uuid=SOMEUUID
      ...
                     sm-config (MRO): image-format: vhd
      ...
      

      So it seems what was earlier vdi_type is now image-format key in the sm-config parameter of a VDI.

      On the other hand, some people are reporting having both keys present in sm-config, e.g.:

      ...
                     sm-config (MRO): image-format: vhd; vdi_type: vhd
      ...
      

      Neither are well documented and I can't find any official info on what keys in sm-config are supported and what is their purpose. Maybe devs can shed some light on this?

      To add to the confusion, official XenServer documentation mentiones a key called just type when creating raw VDIs:

      xe vdi-create sr-uuid=sr-uuid type=user virtual-size=virtual-size \
              name-label=VDI name sm-config:type=raw
      

      In my testing this transparently gets renamed to image-format in the latest version of XCP-ng.

      The reason this bothers me is that I was asked to implement reporting of VDI format in my Ansible modules for XCP-ng but now I'm not sure how to do it across all of the supported versions of XenServer and XCP-ng. Currently it looks like I should try to get vdi_type and fallback to image-format if the first one is not found but I'm not certain if these keys are interchangable and have the same purpose or they just happen to sometimes have the same value. Also, ISO image VDIs seems to be missing any format indication.

      Any info on this subject is well appreciated. Thanks.

      posted in Development
      bvitnikB
      bvitnik
    • RE: New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client

      @Tristis-Oris maybe a few comparative screenshots would help 🙂

      posted in News
      bvitnikB
      bvitnik
    • RE: New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client

      @benapetr just a small notice, at least in 0.0.5 version. When adding an NFS ISO library SR, there is no choice for NFS version (v3 and v4) like in XCP-ng Center. The XAPI then defaults to v3 which did not work in my environment.

      posted in News
      bvitnikB
      bvitnik
    • RE: Created VM from Fast Clone, Now How to Separate

      @hawkpro I believe it will be worse with continuous replication because your replica will be in a shut down state. When you decide to start it, you will have to shut down the original VM and start the replica. You will have a downtime during shut down and start up sequence.

      Downtime during VM migration is a necessity so there is nothing unexpected there. All types of migrations require a VM to be suspended for some time (usually seconds) during the switchover from one host or SR to the other host or SR.

      If you have extended downtimes of your VM migrations, then something is not quite right with your setup.

      posted in Xen Orchestra
      bvitnikB
      bvitnik
    • RE: Created VM from Fast Clone, Now How to Separate

      @hawkpro If you have multiple SRs, move the VM to some other SR.

      posted in Xen Orchestra
      bvitnikB
      bvitnik