Abstract: The technical solutions disclosed are directed to a multi-state reconciliation finite state automata operator framework. The system and methods can identify one or more states between an initial state and a final state of an application executed by a service and one or more parameters corresponding to timing of implementation of the one or more states. The systems and method can provide a model configured to manage progress corresponding to the one or more states of the application to determine, using a first matrix, a current state of the one or more states of the application and determine, using a second matrix, a parameter of the one or more parameters corresponding to a timing of implementation of the current state. The systems and method can provide to the service an indication of the progress of the application.

Abstract: A telemetry registration framework for dynamically synchronizing telemetry producers and consumers at runtime is described. A telemetry registration controller receives a telemetry producer protocol suite for a telemetry producer and assigns an ID to the telemetry producer. The telemetry registration controller receives a consumer request packet from a telemetry consumer that comprises a telemetry consumer protocol suite. The telemetry registration controller determines whether the telemetry producer protocol suite is compatible with the telemetry consumer protocol suite. In response to determining that the telemetry producer protocol suite is compatible with the telemetry consumer protocol suite, the telemetry registration controller transmits information comprising the telemetry producer ID and indicating the telemetry consumer can subscribe to telemetry data from a telemetry message broker that has been published to by the telemetry producer to the telemetry consumer.

Abstract: A telemetry producer sends a hello message to a telemetry registration interface. The interface returns a hello message. The producer sends a producer protocol suite to the interface. An acceptance of the protocol suite and an indication that the protocol suite has been forwarded to a telemetry registration controller is returned. The producer sends a hello message to the controller. The controller returns an acknowledgement and a producer identifier (ID). A second hello message and the producer ID is sent from the producer to the controller. The controller returns a second acknowledgement and the producer ID, indicating the producer registration. A telemetry consumer sends the controller a hello message. An acknowledgement with a consumer identifier (ID), is returned to the consumer. The consumer sends a consumer request packet to the controller. The controller sends the producer ID, and an indication of consumer registration to the consumer.

Abstract: A telemetry producer sends a hello message to a telemetry registration interface. The interface returns a hello message. The producer sends a producer protocol suite to the interface. An acceptance of the protocol suite and an indication that the protocol suite has been forwarded to a telemetry registration controller is returned. The producer sends a hello message to the controller. The controller returns an acknowledgement and a producer identifier (ID). A second hello message and the producer ID is sent from the producer to the controller. The controller returns a second acknowledgement and the producer ID, indicating the producer registration. A telemetry consumer sends the controller a hello message. An acknowledgement with a consumer identifier (ID), is returned to the consumer. The consumer sends a consumer request packet to the controller. The controller sends the producer ID, and an indication of consumer registration to the consumer.

Abstract: A method of tuning telemetry collection parameters may include, with a collector, receiving source data defining at least one application running on a plurality of nodes, the nodes utilizing a finite number of compute resources. With the collector, a number of score models within a scoring agent of the collector may be executed to define telemetry collection parameters used by the collector for source data collection. The method may also include computing, with the scoring agent, a number of scores based on disturbance features and adaptive feedback, and tuning, with the collector, the telemetry collection parameters based on the scores to obtain tuned telemetry collection parameters.

Abstract: A method is described and in one embodiment includes receiving at a network node of an Ethernet Virtual Private Network (“EVPN”) an unsolicited neighbor discovery (“ND”) neighbor advertisement (“NA”) message transmitted on behalf of a host; updating an ND cache of the network node with data included in the ND NA message; syncing the received ND NA message to a multihoming peer of the network node; and advertising by the network node the ND NA message to other nodes in the EVPN.