Some organizations have a deployed and functional “controllerless” EVPN VxLAN Fabric in their data centers. Eventually, however, the organization may deploy a controller within the network. In one example, this disclosure describes a method that includes configuring a controller to communicate with each of a plurality of elements in a network; determining, by the controller, an initial operational state of the network; translating, by the controller, the initial operational state of the network to an intent-based configuration; pushing, by the controller, the intent-based configuration to the network to reconfigure each of the plurality of elements in the network in a manner consistent with the intent-based configuration; determining, by the controller and after pushing the intent-based configuration, an updated operational state of the network; and comparing, by the controller, the initial operational state of the network with the updated operational state of the network.

Various embodiments are generally directed to techniques for network strengthening, such as by detecting issues with one or more network components and reconfiguring one or more upstream or downstream network components to preempt issues with the one or more upstream or downstream network components, for instance. Some embodiments are particularly directed to a tool (e.g., strengthening agent) that implements pre-scripted or dynamic hardening of up and downstream dependencies of a network component in response to an issue identified with the network component. In many embodiments, up and downstream components of a network component may be reconfigured while the issue with the network component is being addressed to preempt issues with the up and downstream components.

Various embodiments are generally directed to techniques for network strengthening, such as by detecting issues with one or more network components and reconfiguring one or more upstream or downstream network components to preempt issues with the one or more upstream or downstream network components, for instance. Some embodiments are particularly directed to a tool (e.g., strengthening agent) that implements pre-scripted or dynamic hardening of up and downstream dependencies of a network component in response to an issue identified with the network component. In many embodiments, up and downstream components of a network component may be reconfigured while the issue with the network component is being addressed to preempt issues with the up and downstream components.

A persistent version-controlled is provided the enables automated configuration of VNFs/CNFs following deployment or re-deployment of VNF/CNF instances throughout the life cycle of the VNFs/CNFs. Immutable copies of NF configurations for a VNF/CNF are stored in the version controlled data storage 100. Multiple versions of a NF configuration can be associated with a common configuration reference (e.g., URL). Metadata associated with the different versions of a NF configuration indicates which of two or more different versions is the current version. The collection of different versions of a NF configuration associated with the same stable reference provide a complete history of the NF configuration, thus allowing rollback to any previous version of the NF configuration by simply modifying the metadata to mark that version as the current version. If a VNF/CNF needs to be re-deployed, the same configuration reference used during the initial deployment is used to download the most recent version of the NF configuration based on the metadata.

A persistent version-controlled is provided the enables automated configuration of VNFs/CNFs following deployment or re-deployment of VNF/CNF instances throughout the life cycle of the VNFs/CNFs. Immutable copies of NF configurations for a VNF/CNF are stored in the version controlled data storage 100. Multiple versions of a NF configuration can be associated with a common configuration reference (e.g., URL). Metadata associated with the different versions of a NF configuration indicates which of two or more different versions is the current version. The collection of different versions of a NF configuration associated with the same stable reference provide a complete history of the NF configuration, thus allowing rollback to any previous version of the NF configuration by simply modifying the metadata to mark that version as the current version. If a VNF/CNF needs to be re-deployed, the same configuration reference used during the initial deployment is used to download the most recent version of the NF configuration based on the metadata.

A method for configuring multiple electronic devices in a batch, is described. The method can include initializing, by a first computing device a communication network based on a pre-defined configuration parameter. The pre-defined configuration parameter is associated with a first instance of an application on the first computing device. Further, the method includes identifying, by the first computing device, an initialization of a second instance of an application at a second computing device. In response to identifying the initialization of the second instance of the application at the second computing device, the method includes, sending, by the first computing device configuration settings for the second computing device over a secured communication network. In this regard, the configuration settings can comprise at least the pre-defined configuration parameter for configuring the second computing device.

A method for configuring multiple electronic devices in a batch, is described. The method can include initializing, by a first computing device a communication network based on a pre-defined configuration parameter. The pre-defined configuration parameter is associated with a first instance of an application on the first computing device. Further, the method includes identifying, by the first computing device, an initialization of a second instance of an application at a second computing device. In response to identifying the initialization of the second instance of the application at the second computing device, the method includes, sending, by the first computing device configuration settings for the second computing device over a secured communication network. In this regard, the configuration settings can comprise at least the pre-defined configuration parameter for configuring the second computing device.

Embodiments described herein are directed to configuring managed computing devices utilizing containerized applications. For instance, a mobile device manager may provide configuration settings to a computing device via, for example, an enterprise network. A host operating system (OS) executing on the computing device determines and applies the settings that are applicable to the host OS. The configuration settings are stored for configuring containerized applications executing on the computing device. For instance, as new containerized applications are launched by the host OS, the containerized applications retrieve the configuration settings and determine and apply the settings that are applicable to the containerized applications. Results of applying the configuration settings to the host OS and the containerized applications are merged and sent to the mobile device manager. The host OS and the containerized application may, for example, implement the settings in order to be compliant with an enterprise's policy.

Embodiments described herein are directed to configuring managed computing devices utilizing containerized applications. For instance, a mobile device manager may provide configuration settings to a computing device via, for example, an enterprise network. A host operating system (OS) executing on the computing device determines and applies the settings that are applicable to the host OS. The configuration settings are stored for configuring containerized applications executing on the computing device. For instance, as new containerized applications are launched by the host OS, the containerized applications retrieve the configuration settings and determine and apply the settings that are applicable to the containerized applications. Results of applying the configuration settings to the host OS and the containerized applications are merged and sent to the mobile device manager. The host OS and the containerized application may, for example, implement the settings in order to be compliant with an enterprise's policy.

Next generation network architectures enable instantiation of network slices in which traffic may be transported via one or more virtual networks overlaying the physical network infrastructure. To enable a slice management system to be able to obtain information on virtual networks of instantiated network slices, such as utilization data indicative of at least one of: a bandwidth capacity, computing capacity and storage capacity of one or more physical links via which traffic of the virtual networks is routed, an interfacing system is provided. The interfacing system may establish an interface between the slice management system operating in the domain of network slices and the network management system operating in the domain of physical network equipment, and thereby enable the slice management system to take into account such utilization data in its slice management operation.