Please, describe the problem here and provide additional information below (if applicable) …
I am attempting to follow the instructions to integrate a ProxMox node as a resource in OpenNebula.
A list of QEMU package dependencies that can not be installed. The opennebula-node-kvm.deb relies on several dependencies, but the QEMU dependencies attempt to kick ProxMox-VE out, effectively killing Proxmox. I attempted to manually add the dependent packages manually one by one. Anything QEMU-* related attempts to kick out PmoxVE from the system.
Proxmox OS is a heavily modded version of a debian distro. As a result, it is not a supported platform for KVM nodes. Why would you even want a Proxmox node being controlled by an OpenNebula frontend ? If for some reason you think this is a good idea, you can try hacking it by installing OpenNebula from source, avoiding all of the package metadata limitations.
Hi, I think it could be great to have proxmox integration through api, like vmware for example.
(proxmox don’t use libvirt)
A big missing feature in proxmox, is when you have multiple proxmox clusters (as you can’t have more than 20~30 nodes in a proxmox cluster), to have a central location.
Another great feature of opennebula is that is more focused client portal ““cloud”” with multi-tenancy and other ““cloud”” features.
They are a multi-cluster management feature on the roadmap on proxmox, but no date/year.
(I known a lot of proxmox users requesting it)
I’m myself a proxmox dev contributor since 2010, using it in my hosting company.
But I’m a poor ruby developper.
@dclavijo - Basically, the familiar front-end can stay, and leaving one VM platform for another en masse is the goal. Like @Alexandre_Derumier said, and API component would be an absolute gift.
Please note that we support distros like:
Ubuntu, Debian, AlmaLinux, RockyLinux, Oracle Linux.
Other distros (Arch, for example) are not supported, and you won’t be able to install OpenNebula on them, unless you install it as mentioned above.