Skip to content

Latest commit

 

History

History
17 lines (13 loc) · 2.03 KB

IamDomainGroup.md

File metadata and controls

17 lines (13 loc) · 2.03 KB

IamDomainGroup

Intersight services are mapped to three different categories of services for scaling purpose. Three categories are defined: Partition1/Partition2/Partition3. Topics for each category are created with a specific number of partitions. For each cloud environment these numbers will be different.

Properties

Name Type Description Notes
name str The name of the domain-group. [optional] [readonly]
partition1 int The partition number domain group related messages are produced for 'Partition1' category service topics. [optional] [readonly]
partition2 int In a cloud environment this parameter will indicate to which partition number domain group related messages are produced for 'Partition2' category service topics. [optional] [readonly]
partition3 int In a cloud environment this parameter will indicate to which partition number domain group related messages are produced for 'Partition3' category service topics. [optional] [readonly]
partition_key str Partition key used for producing messages to Kafka partitions. By default Domain-group id will be used as parition key. For Domain-groups belonging to Early adopters domain-group id will be prefixed with 'H' and used as partition key, such partition key will be treated differently and messages will always be produced to partition 0. [optional] [readonly]
usage int The number of devices in the domain-group. Device registration notifications are processed to update the usage of the domain-group. The on-boarding account will have multiple domain-groups, and during the device registration least used domain-group will be selected for the device. [optional] [readonly]
account IamAccount [optional]

[Back to Model list] [Back to API list] [Back to README]