Running Your vSphere Management Cluster on Hyper-V
This article is a stub. You can help The Open Homelab project by expanding it.
Today i was thinking about a scenario, where i was thinking to put vSphere infra components (Like vCenter server, syslog, AD, DNS, DHCP etc.) above Hyper-V Cluster.
I know what you're thinking, what absurd thing i'm talking about, what is the need of separate management cluster, Hyper-V is not mature enough to host vSphere Management infra., VMware and Hyper-V don't go Hand-in-Hand etc. and i accept that, because before conceiving this concept i had same thoughts but later I cross questioned myself i.e. what are the pros/cons about this design and how this is going to help customers. So, I'm sharing the pros/cons about this design with you, if you any comments whether good or bad, i'm all ears.
Pros and Cons
Pros or advantages:-
- Dual Hypervisor strategy with a twist.
- Most of the vSphere infra components require windows OS (yeah,i know about VCSA).
- Utilize "Virtualization-Safe" feature introduced in win2012 (VM-GenerationID, avail. with Hyper-V v3), make SSO robust.
- License cost reduced (at least for management cluster and OS license).
- Utilize existing hardware and windows OS license.
- vCenter server supported on virtual platform (kb10087), nothing mentioned about Hyper-V
Cons or disadvantages:-
- Requires multi-talented engineers to manage.
- Support-issues from both vendors (support engineer love this sport, Volley-ball).
- Some Third-party software issues (i don't know which, but included it).
- Hard to convince CIO/CTO's (biggest threat to such designs)
|Original article||Original article - has been syndicated by the original author.|