Abstract: Computer-implemented methods, media, and systems for automating secured deployment of containerized workloads on edge devices are disclosed. One example computer-implemented method includes receiving, by a software defined wide area network (SD-WAN) edge device and from a remote manager, resource quotas for a compute service to be enabled at the SD-WAN edge device. Pre-deployment sanity checks are performed by confirming availability of resources satisfying the resource quotas, where the resources are at the SD-WAN edge device. In response to the confirmation of the availability of resources satisfying the resource quotas, one or more security constructs are set up to isolate SD-WAN network functions at the SD-WAN edge device from the compute service at the SD-WAN edge device. The compute service is attached to a SD-WAN network by the SD-WAN edge device. An acknowledgement that the compute service is enabled at the SD-WAN edge device is sent to the remote manager.

Abstract: Examples described herein include systems and methods for setting virtual machines (“VMs”) to desired configurations while the virtual machines are running. In one example, a user can select a VM and a desired configuration. An agent can then set an attribute of the virtual machine to indicate that on guest operation system (“OS”) reboot of the VM, the VM will enter BIOS mode. The agent can also store the desired configuration in the database based on authenticating the user. When the VM reboots at a future time, the attribute can cause the VM to enter BIOS setup. The agent can be notified and can retrieve the desired configuration from a database using an identifier for the VM. Then the agent can apply the desired configuration to the VM during BIOS setup with a system process that does not require further user authentication.

Abstract: Examples described herein include systems and methods for setting virtual machines (“VMs”) to desired configurations while the virtual machines are running. In one example, a user can select a VM and a desired configuration. An agent can then set an attribute of the virtual machine to indicate that on guest operation system (“OS”) reboot of the VM, the VM will enter BIOS mode. The agent can also store the desired configuration in the database based on authenticating the user. When the VM reboots at a future time, the attribute can cause the VM to enter BIOS setup. The agent can be notified and can retrieve the desired configuration from a database using an identifier for the VM. Then the agent can apply the desired configuration to the VM during BIOS setup with a system process that does not require further user authentication.

Abstract: Assessing the need for disaster recovery (DR) protection for a virtual application may include accessing resource consumption history for constituent VMs that support the virtual application. The resource consumption history may include usage metrics corresponding to resources used by each VM. A change in a cost of downtime of the given virtual application may be produced and used to assess criteria or rules. The given virtual application may be designated for DR protection based on an assessment of the criteria. DR protection may be activated for the designated virtual applications. The DR protection may automatically expire after a period of time.

Abstract: Assessing the need for disaster recovery (DR) protection for a virtual application may include accessing resource consumption history for constituent VMs that support the virtual application. The resource consumption history may include usage metrics corresponding to resources used by each VM. A change in a cost of downtime of the given virtual application may be produced and used to assess criteria or rules. The given virtual application may be designated for DR protection based on an assessment of the criteria. DR protection may be activated for the designated virtual applications. The DR protection may automatically expire after a period of time.