planning many workload domains

[elpampa]

good afternoon,

 i will have many (more than 24) workload domains, each will be a dedicated customers, so no common clusters etc...

which is the best way to archive that? i will like to keep mgmt domains at minimum, if every 24 wl domain i must deploy a mgmt domain it will be a big pain to manage...any idea to keep it simple?

thank you

config max to 24 wl domains

https://configmax.broadcom.com/guest?vmwareproduct=SDDC%20Manager&release=9.0.0&categories=17-0

-------------------------------------------

[Marek Zdrojewski]

Hi,

What is actually the use case here? This looks a lot like multi tenancy to me. Is that the case?

if it is, have a look at the VPC concept in VCF 9.

-------------------------------------------

[elpampa]

use case is me managing say 100 different workload domains with least possible effort of mangement vcenters and nsx managers and DONT want to deploy a new mgmt domain each 24 workload domains, thank you.

-------------------------------------------

[Viperman]

Why do you think that you need a separate Workload domain for each customer?  How many hosts do you feel that each customer will be using?  How many VMs?

-------------------------------------------

[elpampa]

because it's mandatory, i NEED separated workload, again, more than 100 wl doms, which is the better option to lesser mgmt vcenter and nsx managers?

thank you

-------------------------------------------

[Marek Zdrojewski]

I've got some follow-up questions:

1. "because it's mandatory" - This is a hard requirement if I understand correctly. What makes it mandatory?
2. "i NEED separated workload" - Why? What is the reason? Physical resource separation? Security?

Don't get me wrong, we are trying to understand your use-case here. It is not a simple matter of deploying a VCF Fleet and keep adding additional VCF Instances. There is a lot more to consider here.

This sounds like a complex design and I would strongly recommend involving Professional Services from Broadcom to help with the design.

-------------------------------------------

[Viperman]

Even if the need was for physical separation, you can have clusters within a workload domain which would provide physical separation.  So I would also have the same question, why the requirement for separate workload domains?  The only thing you really gain with the separate workload domains is a separate vCenter and potentially separate NSX managers, but you could also use Shared NSX managers as well.  NSX supports multitenancy so would like to understand why they would need separate workload domains.

-------------------------------------------

[idefix90]

I agree. We want to try to help, but simply saying that it is absolutely necessary is not enough to provide assistance and understanding of the background. I would also recommend bringing Broadcom Professional Services on board with the design.

-------------------------------------------

[Joffer77]

For each workload domain you will have a vCenter. Sounds like a nightmare managing 100+ vCenters.

Are you sure you can't use a separate physical sphere cluster as the physical restrain instead of workload domain? (also from what I've heard, the workload domain construct might go away in newer versions, but don't take my word on that). With NSX and automation, you can also have tenants, and separate VPCs so whatever you need to separate, you can, with way less workload domains and vCenter/NSX

-------------------------------------------