Observable feature configuration delivery
A system and a method for observable configuration delivery include receiving one or more configuration change requests (CCRs); storing the one or more CCRs in a database; signaling configuration send channels of target tenants of a plurality of tenants associated with the one or more CCRs to awaken; sending the one or more CCRs from the database to the target tenants through a headend service (HES); receiving asynchronous status messages from the HES as a result of sending the one or more CCRs; signaling the configuration send channels for a next set of CCRs based on the asynchronous status messages; and sending the next set of CCRs to one or more tenants of the target tenants.
1 . A method comprising:
receiving one or more configuration change requests (CCRs);
storing the one or more CCRs in a database;
signaling configuration send channels of target tenants of a plurality of tenants associated with the one or more CCRs to awaken;
sending the one or more CCRs from the database to the target tenants through a headend service (HES);
receiving asynchronous status messages from the HES as a result of sending the one or more CCRs;
signaling the configuration send channels for a next set of CCRs based on the asynchronous status messages; and
sending the next set of CCRs to one or more tenants of the target tenants.
2 . The method of claim 1 , wherein receiving the one or more CCRs includes receiving the one or more CCRs from an automated publisher service (APS) of a distributed intelligence (DI) cloud service.
3 . The method of claim 1 , wherein sending the one or more CCRs from the database to the target tenants through the HES includes sending the one or more CCRs by utilizing at least one of:
a broadcast,
a multicast,
a unicast, or
a unicast batch.
4 . The method of claim 3 , wherein sending the one or more CCRs by utilizing the unicast batch includes:
sending tenant operation context information corresponding to each unicast of the unicast batch including:
a corresponding target tenant, and
a corresponding operation identification (ID), and
sending an expected number of unicast changes within multiple unicasts of the unicast batch when there are multiple batches expected based on the one or more CCRs.
5 . The method of claim 1 , wherein the asynchronous status messages indicate at least one of:
successful fulfillment of the one or more of the CCRs by one or more tenants of the target tenants, or
failed fulfillment of the one or more of the CCRs by one or more tenants of the target tenants.
6 . The method of claim 5 , further comprising creating a subscription to the asynchronous status messages by authenticating a bearer token, obtained by an automated publisher service (APS) of a distributed intelligence (DI) cloud services, using service principal credentials of the bearer token.
7 . The method of claim 1 , wherein signaling the configuration send channels for the next set of CCRs includes:
signaling the configuration send channels with in-flight configurations, the in-flight configurations enabling the configuration send channels to initiate one or more additional cycles responsive to new CCRs being received.
8 . The method of claim 1 , further comprising:
finalizing results of configuration changes in device twin configurations, the device twin configurations storing configuration details for calculating the next set of CCRs.
9 . A system comprising:
one or more processors; and
memory coupled to the one or more processors, the memory storing thereon computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations, the operations comprising:
receiving one or more configuration change requests (CCRs);
storing the one or more CCRs in a database;
signaling configuration send channels of target tenants of a plurality of tenants associated with the one or more CCRs to awaken;
sending the one or more CCRs from the database to the target tenants through a headend service (HES);
receiving asynchronous status messages from the HES as a result of sending the one or more CCRs;
signaling the configuration send channels for a next set of CCRs based on the asynchronous status messages; and
sending the next set of CCRs to one or more tenants of the target tenants.
10 . The system of claim 9 , wherein receiving the one or more CCRs includes receiving the one or more CCRs from an automated publisher service (APS) of a distributed intelligence (DI) cloud service.
11 . The system of claim 9 , wherein:
sending the one or more CCRs from the database to the target tenants through the HES includes sending the one or more CCRs by utilizing at least one of:
a broadcast,
a multicast,
a unicast, or
a unicast batch; and
sending the one or more CCRs by utilizing the unicast batch includes:
sending tenant operation context information corresponding to each unicast of the unicast batch including a corresponding target tenant and a corresponding operation identification (ID), and
sending an expected number of unicast changes within multiple unicasts of the unicast batch when there are multiple batches expected based on the one or more CCRs.
12 . The system of claim 9 , wherein:
the asynchronous status messages indicate at least one of:
successful fulfillment of the one or more of the CCRs by one or more tenants of the target tenants, or
failed fulfillment of the one or more of the CCRs by one or more tenants of the target tenants; and
the operations further comprise creating a subscription to the asynchronous status messages by authenticating a bearer token, obtained by an automated publisher service (APS) of a distributed intelligence (DI) cloud service, using service principal credentials of the bearer token.
13 . The system of claim 9 , wherein signaling the configuration send channels for the next set of CCRs includes:
signaling the configuration send channels with in-flight configurations, the in-flight configurations enabling the configuration send channels to initiate one or more additional cycles responsive to new CCRs being received.
14 . The system of claim 9 , wherein the operations further comprise:
finalizing results of configuration changes in device twin configurations, the device twin configurations storing configuration details for calculating the next set of CCRs.
15 . A non-transitory computer-readable storage medium storing thereon computer-executable instructions that, when executed by one or more processors of a system, cause the one or more processors to perform operations, the operations comprising:
receiving one or more configuration change requests (CCRs);
storing the one or more CCRs in a database;
signaling configuration send channels of target tenants of a plurality of tenants associated with the one or more CCRs to awaken;
sending the one or more CCRs from the database to the target tenants through a headend service (HES);
receiving asynchronous status messages from the HES as a result of sending the one or more CCRs;
signaling the configuration send channels for a next set of CCRs based on the asynchronous status messages; and
sending the next set of CCRs to one or more tenants of the target tenants.
16 . The non-transitory computer-readable storage medium of claim 15 , wherein receiving the one or more CCRs includes receiving the one or more CCRs from an automated publisher service (APS) of a distributed intelligence (DI) cloud service.
17 . The non-transitory computer-readable storage medium of claim 15 , wherein:
sending the one or more CCRs from the database to the target tenants through the HES includes sending the one or more CCRs by utilizing at least one of:
a broadcast,
a multicast,
a unicast, or
a unicast batch; and
sending the one or more CCRs by utilizing the unicast batch includes:
sending tenant operation context information corresponding to each unicast of the unicast batch including a corresponding target tenant and a corresponding operation identification (ID), and
sending an expected number of unicast changes within multiple unicasts of the unicast batch when there are multiple batches expected based on the one or more CCRs.
18 . The non-transitory computer-readable storage medium of claim 15 , wherein:
the asynchronous status messages indicate at least one of:
successful fulfillment of the one or more of the CCRs by one or more tenants of the target tenants, or
failed fulfillment of the one or more of the CCRs by one or more tenants of the target tenants; and
the operations further comprise creating a subscription to the asynchronous status messages by authenticating a bearer token, obtained by an automated publisher service (APS) of a distributed intelligence (DI) cloud service, using service principal credentials of the bearer token.
19 . The non-transitory computer-readable storage medium of claim 15 , wherein signaling the configuration send channels for the next set of CCRs includes:
signaling the configuration send channels with in-flight configurations, the in-flight configurations enabling the configuration send channels to initiate one or more additional cycles responsive to new CCRs being received.
20 . The non-transitory computer-readable storage medium of claim 15 , wherein the operations further comprise:
finalizing results of configuration changes in device twin configurations, the device twin configurations storing configuration details for calculating the next set of CCRs.