THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
Managing Guest Network with Pre-Provisioned devices (VPX/MPX) in NCC:
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 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 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 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.
...
HA for VPX/MPX/SDX managed by NCC
When NCC deploys VPX, 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 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 host)
Out of Scope
- KVM, HyperV, and Bare metal hypervisor specific changes
- HA offering for the auto provisioned VPX
...
For auto provisioning VPX in CS
- XenServer (POC is done to pass NS IP details to VPX while booting up to setup NSIP)
- 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 )
UI Flow
- Change in Network Offering to show the service packages when Managed NS is selected as Service Provider
- New Wizard to Add NCC Manager
- Placer holder in the UI to show/list registered NCC Manager
- New tab/box to show auto provisioned NS Vpx in CS Fleet
Upgrade
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.
- Add NS devices with the same interface information like public/private interface VLANs should be appropriately configured in NetScaler ControlCenter.
- Upgrade the network offering of a network.
For upgrading a network which is using dedicated instance on SDX.
...
Overview
Content Tools
Apps