A method for improving performance of a computer procurement application includes using the procurement control system computer, determining a peer group associated with a first entity; using a procurement control system computer, obtaining, from client computers respectively associated with the entities, configurations that instruct a procurement application how to perform procurement tasks for the respective entities of the entities in the peer group; using a procurement control system computer, obtaining, from a first client computer associated with the first entity, a first configuration that instruct the procurement application how to perform procurement tasks for the first entity; obtaining a desired end result from the first entity; using the procurement control system computer, using a machine learning algorithm, determining configurations of the peer groups that have a causal relationship to the desired end result; providing a description of the configuration value to the client computer associated with the first entity.

An example operation may include a method comprising one or more of receiving a VNFC module LCM request where the LCM request specifies a VNFC instance (VNFCI), a target VNFC module, and an LCM operation to be performed, comprising retrieving a VNFCI data entry, determining a target OS installation of the VNFCI, establishing a secure connection to a target OS on a VNFCI hosting VM/container, determining a default command for the LCM operation, adapting the default command to the target OS, executing the adapted command, normalizing a response code, and sending a response to the VNFC module LCM request.

Software configuration deployment techniques for disaggregated computing architectures, platforms, and systems are provided herein. In one example, a method includes presenting a user interface configured to receive instructions related to deployment of software to compute units, and receiving user selections of a software element for deployment to a compute unit comprising a processing element and a storage element. Responsive to the user selections, the method includes instructing a management processor of a communication fabric to deploy the software element for use by the compute unit by at least establishing a first partitioning in the communication fabric between the management processor and the storage element, deploying the software element to the storage element using the first partitioning, de-establishing the first partitioning, and establishing a second partitioning in the communication fabric between the processing element and the storage element comprising the software element, wherein the processing element operates using the software element.

A network device may obtain information concerning a virtual chassis that indicates that the network device and an additional network device are to be included in the virtual chassis. The network device may determine, based on the information concerning the virtual chassis, that the network device is connected to the additional network device, wherein the network device is connected to the additional network device via a link between a network interface of the network device and a network interface of the additional network device. The network device may cause the network interface of the network device to be converted to a virtual chassis interface and the network interface of the additional network device to be converted to a virtual chassis interface to enable the network device and the additional network device to be included in the virtual chassis to allow bootstrapping of the virtual chassis as a single logical device.

A policy driven zero touch provisioning (ZTP) system implements techniques for policy driven ZTP of network devices. One or more ZTP policies, configurations and/or boot images associated with one or more network devices are stored in a database. Upon execution of a boot sequence, a network device automatically sends a DHCP request including network device identification information to the policy driven ZTP system. The policy driven ZTP system identifies a matching ZTP policy having conditions that match the network device identification information. The ZTP system generates a DHCP response including IP leasing information, a boot configuration information by which a boot configuration may be automatically obtained, and/or boot image information by which a boot image may be automatically obtained as defined by the matching ZTP policy. The techniques allow ZTP policies to be defined with device-level granularity for boot configuration and/or boot images.

A network fabric deployment system includes a fabric deployment management system that is coupled to a DHCP server. The fabric deployment management system generates a cloud-based network fabric that is based on a network fabric topology file and that includes a plurality of cloud-based networking devices that are assigned a physical networking device identifier that identifies a corresponding physical networking device. The fabric deployment management system configures and validates each of the plurality of cloud-based networking devices causing each physical networking device identifier being mapped to an IP address at the DHCP server and then retrieves a deployment image file from each of the plurality of cloud-based networking devices that have been configured and validated, and stores each of the deployment image files in a database in association with the physical networking device identifier such that the corresponding physical networking device boots from that deployment image file.

In some examples, a method for data management, the method comprises booting a trusted diskless operating system image via a device firmware component, accessing a non-volatile storage of the device using the trusted diskless operating system image; and retrieving user data from the non-volatile storage of the device, and/or writing user data received from a remote location to the non-volatile storage of the device.

Disclosed herein are network elements for use in a transport network and methods of using the same. The network elements may comprise an embedded device having a processor, a communication device in communication with the processor, a first memory, a second memory, and a third memory. The third memory may store a hybrid boot sequence comprising computer-executable instructions that when executed by the processor of the embedded device cause the embedded device to: determine whether a first kernel image is stored on the first memory; responsive to the determination that the first kernel image is not stored on the first memory, obtain a second kernel image stored on a remote network element; store at least one of the first kernel image and the second kernel image on the second memory as a primary kernel image; and boot the primary kernel image stored on the second memory.

Disclosed herein are a method for establishing a remote work environment for ensuring the security of a user terminal for remote work and an apparatus using the method. The method, performed by the apparatus, includes acquiring media image creation information from a user; creating a certificate for VPN access based on the media image creation information and creating a media image using the media image creation information and the certificate for VPN access; and providing the media image to the user such that the user is able to create a medium for remote work. The user terminal for remote work is booted through the medium for remote work, thereby configuring a runtime environment for remote work in which security is ensured.

The present disclosure relates to systems and methods for deploying enterprise systems in cloud environments. In one implementation, a system for deploying an enterprise system in a cloud environment may include at least one processor configured to provide: one or more first containers hosting at least one application with at least one enterprise function; one or more second containers hosting at least one microservice configured to activate the at least one enterprise function; at least one application programming interface (API) between the at least one microservice and at least one client; and at least one gateway configured to manage access to the at least one API.