...
Cloudstack to leverage NCC and use NCC for managing all NS devices. Provison Provision NS VPX in CS Computing Fleet when NCC requests for deploying new VPX
...
Jira | |||||||
---|---|---|---|---|---|---|---|
| |||||||
Jira | |||||||
server | issues.citrite.net | ||||||
serverId | 65f8ef43-6ff2-3325-bec4-0a0c61d2a717 | key | CS-41077|||||
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Glossary
...
Cloud Admin can choose what kind of an NS offering can be used using Service Package from NCC.
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:
...
...
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 jsonJSON, NCCResource will convert the response assocated to associated with 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.
...
As the Admin creates the service package in NCC, the title of the Service Package will tell the Capabilities of the Service Package
When the guest network is implemented with above created Network offering, then for the network, NCC device will be mapped.
...
Admin has to login to NCC and check checks the Network to Device Mapping.
Discussion Notes:
Admin creates a guest network with network offering using NS as Service provider and chooses appropriate Service Package. When the guest network is to be implemented for LB service, NetscalerElement will be called. NetScaler element will check the network offering and see if the service package is present then it will delegate the call to registered NCCManager. NCC Manager will try to implement the network by reserving a pre-existing or already registered device in NCC. Once NCC able to allocate a device for the Network it will send Implement Network as true else it will send false. For the True response from NCC, NetscalerElement will send True and NetworkOrchestrator will continue to implement other network services or it will fail the Network Implementation if the response is false.
Discussion Notes:
In the 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 an 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.
Work Flow:
For this case, NCC will register the NS VPX image with cloudstack CloudStack by call RegisterTemplateApi. In this case, when NCC has to implement the network call, NCC will send a request to the CloudStack to deploy NetScaler VPX with already registered NS VPX image in CS. CS wil will provision the NS VPX in either XenServer or VMWare hypervisor. CS will create 3 NICs (Management, public, private), reserves a management IP from the pod and pushes it to get configured in management nic in NS Device.
Once the VPX is provisoned provisioned CS will mark the status of Service VM as running. NCC keeps polling the job of deploying VPX in CS. Once the job is completed and Successful, NCC will allocate the device to the guest network and returns Implement Network true. if deploy vpx VPX job fails then NCC will return False to the implement implemented network and CS will fails fail the Network implementation and shutdowns the network When CS deploys VPX, it will deploy without HA at the point of this writing. if the VPX goes down for any reason Admin has to take care of recovering the VPX and get it running. Live Migration of VPX running its compute Compute fleet is supported only if the NS VPX image is supported on Vmware/XenServer.
...
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.
...
if the response is true, then it's LB rule creation is successful else it failed to created create the LB rule.
if the LB rule creation is failed, details of the failure will be logged in MS log.
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.
...
When NCC deploys VPX, ccp CCP won't enable the HA when deploying the VPX. HA for the services in VPX will be taken care by the NCC. If NC deploys VPX, and for any reason, if the VPX goes down in CCP Admin has to take care of troubleshooting it.
HA will be offered by NCC for the VPX/MPX/Vpx on SDX by Active-Passive mode of HA nodes.
When NCC requests to deploy the VPX in CloudStack for HA mode, the HA node will be deployed in the Same Pod.
When deploying (NS-VPX) HA Node, deployNSVpx will have a param which tell tells the first Vpx. CloudStack will find the deployment of the first VPX and deploys the HA node in the same pod (but not in the same same host)
...
registerNetscalerServicePackage - This new api API will be used to register the new service packages created Admin in NC
...
deleteNetscalerServicePackage : This api API is to delete the service package registered in CS
...
Parameter | Type | Optional/Required | Comment |
---|---|---|---|
zoneid | String | Required | zone id |
podid | String | Required | id of the pod |
createNetworkOffering apiAPI: new param is added to createnetworkoffering apiAPI.
Parameter | Type | Optional/Required | Comment |
---|---|---|---|
servicepackageid | String | Optional | id of the service package, default value is empty/null |
deployNsVpx : this api API will deploy the NS VPX in cloudstackCloudStack. This api API will take the same params as deployvirtualmachine api 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.
Parameter | Type | Optional/Required | Comment |
---|---|---|---|
id | String | Required | id of the NSVpx |
stopNSVpx: This api API will stop the NS Vpx given the id of the NS Vpx by admin.
Parameter | Type | Optional/Required | Comment |
---|---|---|---|
id | String | Required | id of the NSVpx vm |
destroyNSVpx: This api API will destroy the NS Vpx given the id of the NS Vpx by admin only if the NSVpx is in stopped state (running vpx VPX means its providing the service. if admin manually stops and destroy the vpxVPX. Its It's Admin choice to do it. When NsVpx is not available then admin should try to re-provision the vpx VPX as part of troubleshooting)
Parameter | Type | Optional/Required | Comment |
---|---|---|---|
id | String | Required | id of the NSVpx vmVM |
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
...
For auto provisioning VPX in CS
Seamless The seamless upgrade is not part of this release.
...
For a customer wants to upgrade an existing Nitro based implemented network to NCC based network offering they have the do the following.
License: "Standard"
Memory: 2GB
ThroughPut: 1000;
Packets per second: 1000000;
SSL Cores: 0;
...