Mapping customers

The MSP wants to map Acronis customers to ticketing customers/clients, and see information about them.

Preconditions

• MSP has enabled the CyberApp.

Basic flow

1. The vendor’s ticketing interface must fetch the data about the MSP’s Acronis tenants using public API and provide a way to manage the mapping between MSP’s ticketing customers and Acronis customers.

   The mapping interface must:

   1. Indicate which MSP’s ticketing customers are mapped.

   2. Allow MSP to create a mapping of their existing ticketing customers and Acronis customers.

      This will create a link between both systems and start their data synchronization.
   3. Allow MSP to remove the mapping between their ticketing customers and Acronis customers.

      This will break the link between both systems and stop their data synchronization.
2. Once the customer mapping is done, MSP must be able to see the information about the mapping.

   For example:

   1. Customer name in ticketing system.

   2. Acronis customer tenant name.

   3. Mapping status.

3. It should be possible to filter and sort the values.

4. MSP should be able to perform:

   1. Workload registration in the corresponding customer tenant.

   2. Monitoring workload statuses.

   3. Ticketing.

   4. Usage reporting and quota management.

API endpoints

Map to existing customers

• Fetch tenants batch.

  Suggested with parameter/s: * GET /api/2/tenants?parent_id= * GET /api/2/tenants?subtree_root_id=

Scenario for fetching workload statuses

• Fetch a list of all resources.

  Suggested with parameter/s: * GET /api/resource_management/v4/resources?type=resource.machine&include_attributes=true