Forum Discussion
NimbostratusBest Practices For Deploying a Multi-Tenant Enviroment on a 10K running 11.2
Greetings,
I am working on a new requirement that calls for running a multi-tenant environment on our active/standby deployed 10K's. As part of the requirement, we need separate administrative context for each customer, which should hide each customer's VIP's, pool, nodes, and etc. from each other when they login to the web ui. There also a requirement to segregate each customer's traffic over the inside and outside trunks. Each customer will use different vlan id numbers. The customer count will be small, it will pretty much be supporting some partner type application. We will start with 4 separate customers and probably not exceed more than 20.
I have done some research and found that separate partitions and route groups will support most, if not all, of the above requirements. But I wanted to reach out to the community to get some feed back on personal experiences with deploying this type of application, as well as recommendations and est practices.
Any feedback provided will be greatly appreciated.
Cheers, Jaime
2 Replies
PeteWhiteEmployee
Pretty simple to do and works well. As you say, separate users can manage objects in their own partition and traffic is kept segregated. My best suggestion is to create simple naming rules and stick to them. Probably worth implementing remote roles/user auth to differentiate users.
silvajai_01_131Thanks. I apologize for the late response but been sick for the past few days.
