Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

At boot time the CCSP components register and advertise their supported capabilities to the Component Registry. They may also choose to subscribe for device profile change events. The following table is a simple illustration of what Component Registrar contains.

Component Name

Version

D-Bus Path

Namespace

Successfully

Registered

Component Name

Version

D-Bus Path

Namespace

Successfully

Registered

com.cisco.spvtg.ccsp.PAM

1

"/com/cisco/spvtg/ccsp/PAM"

Device.DeviceInfo.Manufacturer

Device.DeviceInfo.ManufacturerOUI

Device.DeviceInfo.SerialNumber

Device.DeviceInfo.SoftwareVersion

True

com.cisco.spvtg.ccsp.SSD

1

"/com/cisco/spvtg/ccsp/SSD"

Device.SoftwareModules. DeploymentUnitNumberOfEntries

Device.SoftwareModules.DeploymentUnit.{i}.UUID

Device.SoftwareModules.DeploymentUnit.{i}.Name

Device.SoftwareModules.DeploymentUnit.{i}.UAlias

True
 com.cisco.spvtg.ccsp.PSM1 "/com/cisco/spvtg/ccsp/PSM"

com.cisco.spvtg.ccsp.command.factoryReset

True
 com.cisco.spvtg.ccsp.TDM1 "/com/cisco/spvtg/ccsp/TDM"

“Device.IP.Diagnostics.”

True


The Registry is used by applications to perform Service Discovery based on capabilities. The Protocol Agents in the CCSP control plane, for instance, queries the CR based on capabilities and data model namespace supported and routes messages to those components.

Below figure illustrates the features of Component Registry and how it is used by other internal components and client applications.

...