A profile in PDMS-E is a named set of 1 or more device configuration parameters. A profile can either be created explicitly by a PDMS-E administrator or can be a standard profile that Poly provides. There are four different types of profiles in PDMS-E:
- Polycom Standard
- User Defined (explicitly created by administrator)
- User Imported - created when device configuration is imported by admin via csv
- Automatic - profiles generated automatically for new software
A profile does not have an equivalent concept in Lens.
Profile deployment is the mechanism used in PDMS-E to associate a configuration profile with one or more devices. Profiles can be associated with 5 different levels of configuration (Global, Group, Model, Site, Device) and are applied from least specific (Global) to most specific (Device). Multiple profiles and profile types can be associated with the same configuration level and are merged according to priority, so if the same parameter exists in multiple profiles the value in the highest priority profile "wins".
Mapping PDMS-E Data Models to Poly Lens
Mapping PDMS-E Configuration to Poly Lens
A profile deployment in PDMS-E maps to a policy in Poly Lens, although there are some differences:
- Poly Lens does not support global configuration level in PDMS-E.
- In PDMS-E it is possible to specify configuration parameters that are device agnostic (e.g., a specified parameter may not apply to all the endpoint models). Currently that is not possible in Poly Lens so when configuration is imported from PDMS-E it will be automatically split out into the appropriate model specific policies.
- Configuration precedence in PDMS-E is different than it is in Poly Lens (see Precedence Rules below for details).
For all configuration levels in PDMS-E the resulting entry includes the result of merging parameters from three out of the four different types of profiles: user imported, user defined, and polycom standard. Auto-generated profiles (e.g., used for software versions) are not be included in the export since they can't easily be mapped on import into Poly Lens. Specifying software versions in Poly Lens needs to be done manually by the Poly Lens admin.
Group and model precedence is swapped between PDMS-E and Poly Lens. Specifically (from least specific to most specific precedence):
- PDMS-E: Global Group Model Site Device
- Poly Lens: Model Group Site Device
Device configuration in PDMS-E is exported as as single entry per device, which maps directly to device policies in Poly Lens.
Site Topology Mapping
Sites in PDMS-E are equivalent to sites in Poly Lens (although PDMS-E does not support the concept of rooms), so mapping site topology from PDMS-E to Poly Lens should be a one-to-one mapping.
Site Configuration Mapping
The exported csv contains a single entry per site that specifies the merged parameters for the site along with the list of models associated with the site. Site configuration in PDMS-E maps to model + site polices in Poly Lens.
Group and Model Mapping
Groups are exported as a single entry per group. Each entry contains the merged parameters for the group along with the list of models that are contained in the group.
PDMS-E will automatically generate a "fake" group for any model with model level configuration defined (e.g., Model3Group for Model 3). Each group should be split into the appropriate model + group polices on import into Poly Lens.
Global parameters are exported as a single entry in the csv file. Global configuration in PDMS-E will map to model polices in Poly Lens, one for each model that exists in the E tenant.