...

1. Cloud Admin should be able to manage all types of NS devices using NCC

2. Cloud Admin can choose what kind of an NS offering can be used using Service Package from NCC.

3. Admin can leverage service package to use different versions of Netscaler devices.
4. Admin can leverage service package to use Netscaler devices in Shared or Dedicated mode
5. Admin can choose to provision of NS VPX in CS
6. Admin can choose to provision of NS VPX with different Compute offerings
7. CS Accounts and Users should be able to provision these network offerings - which should in-turn provision the Netscaler VPX/SDX instances without any admin intervention - including license application. 
8. CS Accounts and Users should be able to upgrade from one VPX network offering to another which could be another VPX / SDX / MPX offering
9. CS Accounts and Users should be able to setup Netscaler VPX in HA Pairing mode

Benifits of Using NCC in CloudStack

Capacity pooling across all NetScaler infrastructure. NetScaler Control Center is designed to efficiently pool and manage capacity across all NetScaler appliances including physical (MPX), virtual (VPX), and multi-tenant (SDX) form factors

End-to-end automation across all NetScaler appliances. Using NetScaler Control Center, the complexity of provisioning and deploying ADC functions on a large pool of NetScaler appliances is completely hidden from both the cloud provider and the cloud tenant

Guaranteed SLAs through service aware resource allocation. Cloud providers need to guarantee performance and availability SLAs to different cloud tenants. NetScaler Control Center provides granular control over ADC resource allocation policies, giving the provider flexibility in creating differentiated SLAs for cloud tenants based on their application’s needs. A simple and intuitive workflow to construct “service packages” for different tenant tiers simplifies the SLA creation process. Service packages can be defined with the following parameters and are customizable per tenant:

• Appliance type. The target appliance type on which a logical NetScaler instance for the tenant is created.
• Isolation type. Option to choose between fully dedicated instances and shared instances.
• Resource allocation. The amount of CPU, memory, and SSL capacity to be allocated for each tenant’s dedicated instance.
• Software versions. The specific version of NetScaler firmware for each tenant’s dedicated instance—allows for version and upgrade independence between tenants.

Functional requirements

1. Support of creation of LB rules on Netscaler devices (VPX or MPX)
2. Support creation of LB HealthChecks policies on Netscaler devices
3. Support creation of LB Stickiness policies on Netscaler devices.
4. Support creation of AutoScaler policies on Netscaler devices.
5. Support creation of GSLB rules on Netscaler devices.
6. Support metering of public IP usage in Netscaler devices
7. Support SSL Termination (SSL termination framework is implemented by Apache Cloudstack community for LB on NS devices). Here is the link for the FS https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSL+Termination+Support
8. Support of deploying guest networks with Managed NetScaler Devices( VPX, MPX, SDX) from NCC.
9. Support of deploying Auto provisoning NS VPX in CS supported only if the guest network requires Dedicated Mode NetScaler device. NCC will request CloudStack to deployNSVpx in CloudStack only if the network requires dedicated NS VPX 
   

...