Managing Type 1 Hyper Visors
-
XCP-ng with XO is another option that works well and is under rather consistent development.
XO sets up a web server we're you'd get gui access, back ups, health stats all from a single pain of glass.
-
We use xenserver and xcp-ng hosts but we use the Windows client, aka Xencenter, to manage the hosts.
Xencenter is to xenserver/xcp-ng what virt-manager is to KVM - but Xencenter is more advanced and powerful.
It talks directly to the hosts on the hosts management interface using the embedded web service (xml-rpc) inside the host so no management VMs or anything is required. We access the hosts management interface over VPN.
The client itself is just a user interface and doesn't store anything so you can run multiple clients connected to the same hosts at the same time.
Xencenter client -> hostYou can also combine it with Xen Orchestra which is a web application for managing the host and give additional functionality.
Web browser -> XO server -> host -
As soon as Cockpit can 100% manage a host, I will most likely use KVM exclusively. I still use Hyper-V Server for most deployments. It does everything I have ever needed and no licenses to deal with.
-
@brandon220 said in Managing Type 1 Hyper Visors:
As soon as Cockpit can 100% manage a host,
It can now. We switched to it two weeks ago because it is finally ready.
-
@scottalanmiller said in Managing Type 1 Hyper Visors:
@brandon220 said in Managing Type 1 Hyper Visors:
As soon as Cockpit can 100% manage a host,
It can now. We switched to it two weeks ago because it is finally ready.
Can you clone through cockpit yet?
-
@stacksofplates said in Managing Type 1 Hyper Visors:
@scottalanmiller said in Managing Type 1 Hyper Visors:
@brandon220 said in Managing Type 1 Hyper Visors:
As soon as Cockpit can 100% manage a host,
It can now. We switched to it two weeks ago because it is finally ready.
Can you clone through cockpit yet?
Don't think so. In the SMB MSP space, that never comes up. Most customers have only 1-3 VMs, and never anything alike.
-
@stacksofplates said in Managing Type 1 Hyper Visors:
@scottalanmiller said in Managing Type 1 Hyper Visors:
@brandon220 said in Managing Type 1 Hyper Visors:
As soon as Cockpit can 100% manage a host,
It can now. We switched to it two weeks ago because it is finally ready.
Can you clone through cockpit yet?
I don't see that option specifically on a running VM (lab), Fedora 31. Are you discussing to another host or just an export?
-
I like the ability to clone - especially in my lab. The obvious reason is to have a few server (minimal) VMs patched and ready to deploy.
-
@brandon220 said in Managing Type 1 Hyper Visors:
I like the ability to clone - especially in my lab. The obvious reason is to have a few server (minimal) VMs patched and ready to deploy.
Also on production when upgrades don't go as planned. While you can revert the production VM back to the pre-upgrade snapshot, you can use clones to troubleshoot on.
-
@scottalanmiller said in Managing Type 1 Hyper Visors:
@stacksofplates said in Managing Type 1 Hyper Visors:
@scottalanmiller said in Managing Type 1 Hyper Visors:
@brandon220 said in Managing Type 1 Hyper Visors:
As soon as Cockpit can 100% manage a host,
It can now. We switched to it two weeks ago because it is finally ready.
Can you clone through cockpit yet?
Don't think so. In the SMB MSP space, that never comes up. Most customers have only 1-3 VMs, and never anything alike.
So you just install the OS from the install screen every time you build a VM?
-
@DustinB3403 said in Managing Type 1 Hyper Visors:
@stacksofplates said in Managing Type 1 Hyper Visors:
@scottalanmiller said in Managing Type 1 Hyper Visors:
@brandon220 said in Managing Type 1 Hyper Visors:
As soon as Cockpit can 100% manage a host,
It can now. We switched to it two weeks ago because it is finally ready.
Can you clone through cockpit yet?
I don't see that option specifically on a running VM (lab), Fedora 31. Are you discussing to another host or just an export?
No just a template to clone from. Like you apply any base configurations to the template and then just clone that.
-
Proxmox
-
-
@DustinB3403 Why?
-
@DustinB3403 said in Managing Type 1 Hyper Visors:
@VoIP_n00b said in Managing Type 1 Hyper Visors:
Proxmox
It's not that bad.
-
@stacksofplates said in Managing Type 1 Hyper Visors:
@DustinB3403 said in Managing Type 1 Hyper Visors:
@VoIP_n00b said in Managing Type 1 Hyper Visors:
Proxmox
It's not that bad.
But it's not as good or better than any of the alternatives.
-
@DustinB3403 said in Managing Type 1 Hyper Visors:
But it's not as good or better than any of the alternatives.
What do you mean?
-
@DustinB3403 said in Managing Type 1 Hyper Visors:
@stacksofplates said in Managing Type 1 Hyper Visors:
@DustinB3403 said in Managing Type 1 Hyper Visors:
@VoIP_n00b said in Managing Type 1 Hyper Visors:
Proxmox
It's not that bad.
But it's not as good or better than any of the alternatives.
It's KVM....so it's the same
-
@VoIP_n00b said in Managing Type 1 Hyper Visors:
Proxmox
Proxmox is just KVM. But we generally avoid it because we've run into some serious ethics and professionalism problems with the company over on
community. Super sketchy business practices, very scammy and I'd never let their software or support into my shop.The idea is weird.. KVM and LXC on the same box with all this extra layers that are just asking for things to go wrong when you get all the features really without Proxmox involved.
-
@scottalanmiller said in Managing Type 1 Hyper Visors:
Super sketchy business practices, very scammy
Care to explain?
