...

1. NCC Admin will create Service Package in NCC.
2. After Creating Service Package, Admin will register services packages in CS by calling registerServicePackage api API 

Registering NS VPX Template

1. When Service package is created in NCC, NS VPX image will be associated to with the SP. 

2. When NCC Admin registers ServicePackage in CS, NCC will upload the associated VPX Image to the CS via RegisterTemplate API and this template will be cross zones.

...

Integration with NCC is via RestAPI with JSON payload.

When cmd has to be send sent to NCC, NCCResource will convert the java cmd to JSON payload and send the request as RestAPI with json JSON payload.

When NCC sends the response it will send the response in json, NCCResource will convert the response assocated to java type Answer and uses it.

...

Admin registers CloudStack in NCC with CS IP, api API key and secret key

Admin registers NCC Manager with CloudStack with NCC IP, username, and password.

When NCC is registered in CS, NCCResource will be created and configured with details.

Admin can delete the NCC if  no no guest network is using NCC.

...

In case of VPX auto provisioning in SDX through NCC, when the implement call comes to NCC to allocate a device to the guest network, NCC will auto provision a NS VPX on the SDX box configured in NCC. 

Once the NS VPX is successfuly successfully provisioned and configured with network details then NCC will send True for the Implement network call or else it will send False and the Network Implementation will result in failure.

...

Admin/User creates LB rule, then NetScaler will receive CreateLoadBalancerCmd. NetScaler will delegate the cmd to the registered NCC.

when NCC will receives receive the cmd, it will find the device allocated for the network where LB rule is getting created.

...

Admin can look at the log and find the issue. If the failure/issues is are at NCC, Admin can login to NCC and check the details for the Root cause for failure.

...

1. Advance Zone Isolate Network (VLAN Isolation)
   1. Remaining services should be looked at priority. (LB, healthcheckshealth checks, autoscale )
   2. GSLB low priority 
2. Advance zone VPC Public Tier (in the tier where Netscaler is supported as external LB)
3. Advance Zone Shared Network (stretch goal)
4. Basic Zone EIP/ELP ( this is stretch goal)
5. NS (VPX, MPX, VPX on SDX) will be supported with VLAN configuration only.

...

deleteNetscalerServicePackage : This api API is to delete the service package registered in CS

...

createNetworkOffering apiAPI: new param is added to createnetworkoffering apiAPI.

...

 deployNsVpx : this api will deploy the NS VPX in cloudstack. This api will take the same params as deployvirtualmachine  api expect the network details (will update more details about params)

 startNSVpx:  This api API will Start the NS Vpx given the id of the NS Vpx by admin.

stopNSVpx: This api API will stop the NS Vpx given the id of the NS Vpx by admin.

...

listNSVpx :

This api API will list Vpx(which VMs running on CloudStack Managed Hypervisors) which are auto provisoned -provisioned by CloudStack  on NCC request in CloudStack

...

1. 1. XenServer (POC is done to pass NS ip IP details to VPX while booting up to setup NSIP)
   2. VmWare VMware (No POC is done. KB article available on how to pass the info. depending on this KB article http://support.citrix.com/article/CTX128250 )
      
      

...

1. 1. Change in Network Offering to show the service packages when Managed NS is selected as Service Provider
   2. New Wizard to Add NCC Manager
   3. Placer holder in the UI to show/list registered NCC Manager
   4. New tab/box to show auto provisioned NS Vpx in CS Fleet

Upgrade

              Seamless The seamless upgrade is not part of this release.

...

• • • Add NS devices with the same interface information like public/private interface VLANs should be appropriately configured in NetScaler ControlCenter.
    • Upgrade the networkoffering network offering of a network.

...