If you were at Synergy Anaheim 2013, “Mobility” as the reigning theme was quite self-evident. What was a little more subtle was how far the adoption of enterprise clouds has come. The questions, discussions, and directions that we saw our customers take made it clear that large numbers are in the throws making their clouds work with production grade applications. As they take these steps, the discussion of SDN grew considerably based on first-hand experience of wanting to build a more flexible network as well as the discussion of creating MSP-like services for providing resources for devices like the NetScaler.
Managed Service Providers (MSPs) offer their services in a manner that is distinct from Cloud Service Providers (CSPs) in that MSPs have a single administrative group managing shared resources where they require a global view of configurations and resources. This is necessary to insure that it is possible to meet SLAs given the global load. This is especially important to insure that a single tenant doesn’t drive a change in the configuration such that other tenants are adversely affected. CSPs by comparison drive true resource segmentation such that SLAs can be kept despite individual tenant changes and requirements along the way.
When we introduced the NetScaler SDX, we addressed the requirements of the CSP use case extremely well. Each tenant had a truly segmented set of resources for networking, network, namespace, and even guaranteed performance levels. In essence, guaranteeing the SLA of the tenant no matter how the tenant changed their configuration or network. It was an ideal solution for the vision of moving to a delegated control where application owners could manage their own resources without creating risk for other tenants.
What we found over time was that some organizations ended up changing directions along the way towards a CSP model and opted to use an MSP model with shared resources. This allowed them to achieve a higher density of tenants that could leverage a shared management and traffic plane. This made for less than perfect isolation, but based on the organizational needs, this proved to be an acceptable trade-off for the increase in application density.
Starting with NetScaler 10.1 introduced today, we are pleased to introduce our answer to the MSP model: Traffic Domains. Traffic Domains give network-level isolation so that individual tenants can have overlapping IP addresses that are segmented by VLAN, but a true shared management and resource domain (e.g., shared CLI, GUI, CPU, throughput, etc.) to make management simple and clean for the site-level manager. With this new feature, NetScaler is distinct in offering a true CSP model (NetScaler SDX and VPX), MSP model (NetScaler with Traffic Domains on MPX, SDX, or VPX), or classic single tenant model on all of our platforms. Combined with TriScale for Scale-Up, Scale-In, and Scale-Out, enterprises and service providers have the most flexible ADC available in the market.
Take a look at the choices and make your own decision based on business requirements. You’ll find the greatest flexibility right here.