THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
- NCC should provide Rest API to add NCC details to CS.
- NCC should understand CloudStack request for discovering the NCC capabilities.
- NCC's management network should be reachable from CS.
- There will be a single NCC for an entire CloudStack deployment.
Work Flow
Pre-setup
- Install NCC and Configure NCC.
- NCC management IP should be reachable to CS.
- CS should be able to reach NCC Manager (NCC manager is up and running).
...
- Can't see the service packages in the Create Network Offering wizard
- Either NCC Admin didn't create any Service Packages or issues in API of Listing the services packages in CS.
- Verifying the LB rules created in guest network
- Find the network id, go to NCC UI and find the device allocated to the network and verify LB configurations can be seen in the device
- Guest Network creation is failed on NetscalerElement
- NCC was not able to allocate a device matching to the requirements of services package to the network.
- LB Rule creation Failed
- Login to NCC and check the NCC log to find the log for the LB rule creation
- Auto Provision VPX in CS is failed
- Admin can check the reason for failure in management log.
- Reasons could be
- Template not available to use
- Insufficient capacity exception (computeCompute, IP address etc were not available).
...
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 key, and secret key
Admin registers NCC Manager with CloudStack with NCC IP, username, and password.
...
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.
Managing Guest Network with Auto Provisioning VPX devices on SDX managed in NCC:
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.
...
Managing Guest Network with Auto Provisioning VPX devices in CS and manage in NCC:
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.
...
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.
...
HA for VPX/MPX/SDX managed by NCC
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 same same host)
Out of Scope
- KvmKVM, HyperV and Baremetal Bare metal hypervisor specific changes
- HA offering for the auto provisioned VPX
...
registerNetscalerServicePackage - This new api API will be used to register the new service packages created Admin in NC
...
NSVPX Life Cycle Management API's
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)
...
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 will list Vpx(which VMs running on CloudStack Managed Hypervisors) which are auto-provisioned by CloudStack on NCC request in CloudStack
...
For upgrading a network which is using dedicate dedicated instance on SDX.
- Create a ServicePackage with the following spec and create a network offering with the SDX service package.
- Upgrade the network offerings of the existing network to SDX based network offering.
For upgrading a network which is using shared instance on SDX.
- Create SDX instances manually on the SDX or can add the existing instances.
- Create a Servicepack and add these manually created instances.
- Upgrade the network offering of the existing network to SDX based network offering.
...
Overview
Content Tools
Apps