RunX: tech preview
-
if this helps....
yum install --enablerepo=epel -y qemu-dp xenopsd xenopsd-cli xenopsd-xc xcp-ng-xapi-storage runx Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register. Loading mirror speeds from cached hostfile * centos-ceph-nautilus: mirror.as29550.net * centos-nfs-ganesha28: mirrors.vinters.com * epel: mirror.freethought-internet.co.uk Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-linstor: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-runx: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org Package 2:qemu-dp-2.12.0-2.0.5.xcpng8.2.x86_64 already installed and latest version Package xenopsd-0.150.12-1.2.xcpng8.2.x86_64 already installed and latest version Package xenopsd-cli-0.150.12-1.2.xcpng8.2.x86_64 already installed and latest version Package xenopsd-xc-0.150.12-1.2.xcpng8.2.x86_64 already installed and latest version Package xcp-ng-xapi-storage-1.0.2-3.0.0.runx.1.xcpng8.2.x86_64 already installed and latest version Package runx-2021.1-1.0.0.runx.1.xcpng8.2.x86_64 already installed and latest version Nothing to do -
Please, Please, Please make this document itself with bash variables when it comes to the various UUIDs:
[XCP-ngHostX]# SRuuid=$(xe sr-list name-label="Local storage" --minimal) [XCP-ngHostX]# RunXdebTemplateName="My RunX Template based on Deb10" [XCP-ngHostX]# RUNXdebTEMPLATEuuid=$(xe vm-install template="Debian Buster 10" new-name-label="${RunXdebTemplateName}" sr-uuid=${SRuuid} --minimal) [XCP-ngHostX]# echo ${RUNXdebTEMPLATEuuid} [XCP-ngHostX]# xe vm-param-set uuid=${RUNXdebTEMPLATEuuid} HVM-boot-policy="" [XCP-ngHostX]# xe vm-param-set uuid=${RUNXdebTEMPLATEuuid} PV-args="" [XCP-ngHostX]# xe vm-param-set uuid=${RUNXdebTEMPLATEuuid} VCPUs-max=2 [XCP-ngHostX]# xe vm-param-set uuid=${RUNXdebTEMPLATEuuid} VCPUs-at-startup=2 [XCP-ngHostX]# xe vm-disk-remove device=0 uuid=${RUNXdebTEMPLATEuuid} [XCP-ngHostX]# xe template-param-set is-a-template=true uuid=${RUNXdebTEMPLATEuuid} [XCP-ngHostX]# xe template-list name-label="${RunXdebTemplateName}" [XCP-ngHostX]# xe template-list uuid=${RUNXdebTEMPLATEuuid} -
is this tech preview available on 8.3 alpha release?
any idea how can i set RunX on 8.3 release? -
-
@jchua We currently don't have a test version planned for XCP-ng 8.3. Only 8.2 is supported for the moment.
-
@ronan-a would it be too much to ask for a version for 8.3?
I'm testing the alpha since publication and I would like to be able to use RunX
-
@Finallf It's been a while since we've been actively working on this subject, that doesn't mean that this project is abandoned, but it's not our priority target.
Currently it is rather this project that we are trying to move forward: https://xen-orchestra.com/blog/announcing-project-pyrgos/Sorry but it's not so soon that we will have a new runx update.
-
Yes, and it's not impossible that RunX will be used in Pyrgos at some point
-
@olivierlambert Is there any updates on the RunX and Pygros ?
Any tutorials one can find? Docs or other forum threads?
I'm currently running XCP-NG 8.3 beta for my homelab. I'm interested in having kubernetes or Docker runtime using RunX or Pygros.Thanks in advance
-
Pyrgos is working, you can already use it directly from your XOA. We are now working on doing lifecycle improvements (like updating a cluster) as a next feature for Q1.
RunX is a bit different, it's still a test thing, for now we consider Pyrgos more important (delivering a k8s cluster in a turnkey fashion).
-
just a personal opinion I'm leaving here, no follow-up needed.
If I want to run containers I use OKD.
I've always seen all the comments about keeping the dom0 controller to a minimum, docker alone adds a 2GB overhead to it, no more problems in adding stuff to it.
