Hi Bryan,
Am 03.12.2019 um 17:32 schrieb Bryan J Smith:
> On Tue, Dec 3, 2019 at 11:16 AM Bryan J Smith <[email protected]
> <mailto:[email protected]>> wrote:
> 
>     So, if anyone wants to take this off-list, I'm all ears.  I want to
>     understand Proxmox architecture and code better than I have been
>     exposed to.  Enterprise experience is key for me, and I don't like
>     to assume from just reading things, especially automating and
>     orchestrating a lot with other tooling the past, full decade-plus --
>     both VM and pre-LXC 'cartridges/gears' (i.e., early OpenShift
>     'pods,' if you will).
> 
> 
> So, just for my own info, I made time to look at some things in Proxmox
> I hadn't, like HA.  Sure enough, it's like OpenStack, using the
> Novell-Red Hat HA developments of corrosync, pacemaker, et al.
> 
> There's a reason I like oVirt (RH[E]V) more, especially self-hosting in
> 3.x, let alone v4.x in 2016+.  I mean, I haven't had to deal with this
> for anything 'raw' KVM like HA in almost a decade.

Proxmox has (at least in Europe) a substantial adoption in the SMB
segment. Working at one of the larger hosting providers (for dedicated
servers), we see significant use. These are primarily customers/people
who have no or very small IT departments. So basically Proxmox offers
them a free (as in beer) equivalent of VMware with a nice GUI that they
can install on top of Debian. It abstracts a lot of the internals
involved in setting up complex things like a Ceph cluster.
So from where I am standing, it is something like Plesk or
Virtualmin/Webmin/Cpanel/DirectAdmin/etc.

The major difference of Proxmox to the RH-world is its orchestration
called qemu-server that they use instead of libvirt:
https://github.com/proxmox/qemu-server


So while I think Proxmox has significance, I don't see it as a standard
like Docker. Also I can't think what kind of questions we would be
asking. The typical user/admin will hardly if ever use the console or be
required to understand how Proxmox works internally. So the coverage
could and should only be awareness and concepts.

Best regards,
Markus
_______________________________________________
lpi-examdev mailing list
[email protected]
https://list.lpi.org/mailman/listinfo/lpi-examdev

Reply via email to