Disclosed embodiments are directed at systems, methods, and architecture for operating a control plan of a microservices application. The control plane corresponds with data plane proxies associated with each of a plurality of APIs that make up the microservices application. The communication between the data plane proxies and the control plane enables automatic detection of service groups of APIs and automatic repair of application performance in real-time in response to degrading service node conditions.

Disclosed embodiments are directed at systems, methods, and architecture for operating a control plan of a microservices application. The control plane corresponds with data plane proxies associated with each of a plurality of APIs that make up the microservices application. The communication between the data plane proxies and the control plane enables automatic detection of service groups of APIs and automatic repair of application performance in real-time in response to degrading service node conditions.

A federation with distributed edge configuration management including multiple data centers, each including an infrastructure, at least one storage, and a configuration platform. The infrastructure includes physical resources including at least one computer server. The storage stores state information indicative of a current state of the infrastructure and configuration information of the infrastructure. The configuration information includes composed immutable content incorporating automation tasks and instructions to effectuate state changes of the infrastructure. The configuration platform includes a network interface and a configuration processor that configures the infrastructure by generating and executing a workflow that includes a sequence of operations to effectuate a change of state of the infrastructure. The composed immutable content may include catalog units of subcomponents each including one or more declarative instructions. Catalog units or subcomponents may be grouped into version sets managed by a version set manager.

A disclosed method for managing a multi-node, HCI cluster provisions a central manager of the HCI cluster with an event listening service. The service is then registered with an agent in each HCI node. The service, when triggered by a management network configuration event, causes the agent to modify a management network configuration of the node in accordance with the event. Disclosed methods may respond to successfully applying a management network configuration change by sending a success notification to the central manager and awaiting a confirmation from the central manager. If confirmation is not received within a timeout interval, a timeout occurs and the management network configuration is rolled back to a last known good configuration. If the configuration change cannot be successfully applied, a failure notification is sent to the central manager and the configuration of the node is rolled back to a last known good configuration.

Disclosed embodiments are directed at systems, methods, and architecture for operating a control plan of a microservices application. The control plane corresponds with data plane proxies associated with each of a plurality of APIs that make up the microservices application. The communication between the data plane proxies and the control plane enables automatic detection of service groups of APIs and automatic repair of application performance in real-time in response to degrading service node conditions.

Systems and methods for rollback of model-based provisioned network device configuration including a memory capable of storing a model-based provisioned data template that includes a data template sequence. Data associated with a request to transmit a target object request message are received and transmitted following a retrieval message that determines pre-configuration data of the target device. The pre-configuration data is stored and the target object request message is sent specifying CRUD semantics. A notification is received indicating an outcome of the execution and, if the execution outcome is unsuccessful, a rollback stack is retrieved that specifies CRUD semantics and the pre-configuration parameters are retrieved to restore the target device to a pre-request state. If the execution outcome is successful, a second target object request message is retrieved from a list of target devices.

In one embodiment, a method includes determining a first configuration information for configuring a user plane device of the first network slice associated with the control plane device, generating a first configuration identifier based on the first configuration information, sending, to the user plane device of the first network slice, the first configuration identifier and the first configuration information, receiving, from the user plane device of the first network slice, a second configuration identifier, wherein the second configuration identifier is generated by the user plane device of the first network slice based on the first configuration information received from the control plane device, and verifying, by comparing the first configuration identifier and the second configuration identifier, that the user plane device of the first network slice is configured using the first configuration information.

Disclosed are various implementations of approaches for continuous delivery of management configurations. In some examples, a management configuration delivery workflow is retrieved from a source environment. The management configuration is transmitted to a destination environment specified in the management configuration delivery workflow. The destination environment us updated to apply the management configuration.

Disclosed embodiments are directed at systems, methods, and architecture for operating a control plan of a microservices application. The control plane corresponds with data plane proxies associated with each of a plurality of APIs that make up the microservices application. The communication between the data plane proxies and the control plane enables automatic detection of service groups of APIs and automatic repair of application performance in real-time in response to degrading service node conditions.

Physical assets in a network are graphically modeled and controlled using a monitoring and control interface. Prior to committing configuration changes to the physical assets, the draft configuration changes are analyzed to determine if they violate any logical configuration change rules. The logical configuration rules can be model-based according to target physical asset(s) for the draft configuration changes. A logical configuration change rule violation can be graphically displayed on the monitoring and control interface. The configuration changes can be stored to debug the physical assets and to roll back the configuration of the physical assets to a prior state.