Overview
This document will act as an EPC “Standards Guide” to aid in the deployment and support of EPC. The Infrastructure, Naming conventions and other standard processes will be summarized here.
These items are subject to change. Below you will find a cheat sheet on setting up a new MSP. As an MSP these conventions will ensure new EP’s are placed into the appropriate Test Group automatically.
Make sure the resource group name is - <DXPTenantName>
Make sure the test groups are named - <DXPTenantName-Users> and <DXPTenantName-Hubs>
User Group named: <DXPTenantNameGrpAdmin>
Domain Name: <DXPTenantNameUSProd>
Test Names : DXPTenantName-P2P-15Min or DXPTenantName-VOIP-
Creating MSP in Controller - Nectar Steps
Nectar Step | Notes |
Create a new “User-Group” for the MSP. | Use appropriate naming convention. |
Create a new “Domain” for MSP. | The domain will be tied to the User Group. |
Create a new “Service” for MSP. | The service is what houses the tests. |
Create Tests for the new MSP | Create one P2P and one VOIP test |
Creating Customer in Controller - MSP Steps
MSP Steps | Notes |
Create new Users. | The MSP admin can create new users. |
Create new “Resource Group” | A Resource Group is a Tenant (Customer) |
Add new Test groups | Test groups are what house the test points to run tests against. |
Add new test points | The test points will run tests in groups or individual |
Add new OrgID and GroupID | The Org and Grp ID’s will dictate what license and resource group the TP will be added. |
Run tests Manually/Automatically | Tests can be run automatically or manually. |
Add necessary license pool | This can be an MSP pool or individual tenant pool.Create new Users. |