The main requirement for Data Center Deployments
has the ability to multiple services or instances run on the same infrastructure. The end user application for this arises as to the definition of multi-tenancy. It is a requirement of many years and we were the first ADC provider is true and complete multi-tenant solution introduce NetScaler SDX platform.
NetScaler SDX defined multi-tenancy on the software and hardware layers of NetScaler ADC.
Particularly where running each instance of NetScaler VPX on its core defined storage and interface queues. In this model all NetScaler version is inde
dependent and could be various maintenance operations at the same time to run. So if you are looking for true multi-tenant solution, then SDX is your platform and today we have 80 VPX instances can be run on individual SDX platform.
Second form of multi-tenancy was in NetScaler defined traffic domains focusing on network layer.
ordering multi-tenancy has helped us to make the IP overlapping applications for different needs of enterprises. It helped create separate network paths and routing tables, so you regarding other tenants on the same machine hosting your traffic passes in isolation.
We have these solutions in place ... so why Admin. Partitions ???
While we got the 2 approaches explained, they were somehow two different extremes. Over the years we have learned that the customer software level want to make multi-tenancy that define simple, control, operate and manage, without getting into the hardware level details. Essentially you can where you can isolate ADC services as logical ADC configuration, organizations, network path, etc. without walling hard in hardware. Even as Citrix closely to replace with Cisco ACE operates in the devices, we needed a multi-tenant model, which was on the ACE context model very close. It follows the presentation of "Why"
When we use the core reason why we understand these new infrastructure, different customers have different basic and applications for Admin partitions. Let the most important applications look through it allows
Enterprise Use Cases .:
- IP overlapping
- Virtual Routing
- Entity space separation
- authentication and authorization
- 1 Admin - multiple partitions
service provider Use Cases
- Many companies use cases
- GUI / CLI / API separation
- monitoring and Statistics separation
- Unique configuration file for each partition
- audit logs for each partition
- Conn / throughput / memory limits
- External RBA for partition Access
cloud deployment use cases
- Many of the above defined
- API driven definition of partitions
- ability applications to partitions
- integration with orchestration layer
here's how to tie the current company NetScaler provides deployment without a partition, where the central administrator manages all applications including all by NetScaler be balanced load Apps.
The same application changes with each use individual admin partition in connection with their own administrators.
All = HEADCOMP administrators to clean manage this application-specific specific ~~ POS their own login UI and a way their app without worrying about the coexistence of other apps or administrators to know on the same device. Administrators can define their own SNMP manager and the remote management aspect for partitions. Configuration isolation is another important aspect, which is made as each partition file maintains its own ns.conf. Therefore, it is very easy to manage application deployment by partitions.
Admin partitions are defined in software
So we can define many other partitions, without getting into any hard limit. On the upper side you can configure 512 Admin partitions on each NetScaler appliance. When we say "any" we really mean it, how to use Admin partitions on each NetScaler appliance as MPX, VPX and VPXonSDX. The GA release for Admin partition is available at:
http://www.citrix.com/downloads/netscaler-adc/firmware/release-105e-build-521155e.html
There are many more interesting things around Admin partitions that we will cover in the next series of blogs. Provide us your feedback!
0 Komentar