Vmware, Inc.

Mark Peek

Berndt Jung

Karol Stepniewski

Ivan Mikushin

Daniel James Beveridge

Sujata Banerjee

Yotam Harchol

Amarnath Raghunathan

Pranay Pareek

Steve Tilkens

Yuriy Georgiev

Xueyang Hu

Pontus Rydin

Ed Shmookler

Nicholas Tenczar

Mike O'Reilly

Pascal Laroche

Arjun Singhvi

Heath Reynolds

Sean Lambert

Systems and methods for setting virtual machines ('VMs') to desired configurations while the virtual machines are running. In some systems, 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.

Desired state configuration for virtual machines

Techniques for implementing event proxies in a Functions-as-a-Service (FaaS) infrastructure are provided. In one set of embodiments, a computer system implementing an event proxy can receive an event emitted by an event source, where the computer system is part of a first computing cloud including the FaaS infrastructure, and where the event source is a software service running in a second computing cloud that is distinct from the first computing cloud. The computer system can translate the event from a first format understood by the event source to a second format understood by a function scheduler of the FaaS infrastructure, where the function scheduler is configured to schedule execution of functions on hosts of the FaaS infrastructure. The computer system can then make the translated event available to the function scheduler.

Event proxies for functions-as-a-service (FaaS) infrastructures

The disclosure provides an approach for enabling network functions to be executed in serverless computing environments. One embodiment employs a per-packet architecture, in which the trigger for launching a serverless computing instance is receipt of a packet. In such a case, each received packet is packaged into a request to invoke network function(s) required to process the packet, and a serverless computing environment in turn executes the requested network function(s) as serverless computing instance(s) that process the packet and return a response. Another embodiment employs a per-flow architecture in which the trigger for launching a serverless computing instance is receipt of a packet belonging to a new traffic flow. In such a case, a coordinator identifies (or receives notification of) a received packet that belongs to a new sub-flow and launches a serverless computing instance to process packets of the sub-flow that are redirected to the serverless computing instance.

Network functions support for serverless and granular computing environments

Event proxies for functions-as-a-service (FAAS) infrastructures

Techniques for implementing curated image management in a Functions-as-a-Service (FaaS) infrastructure are provided. In one set of embodiments, a service component of the FaaS infrastructure can maintain one or more curated software lists defined by one or more administrators of the FaaS infrastructure, where the one or more curated software lists identify software that has been approved for use on the FaaS infrastructure. The service component can further receive, from an application developer, a selection of software from the one or more curated software lists, generate a custom image that incorporates the received selection of software, and store the custom image in a repository of the FaaS infrastructure.

Curated image management in a FaaS infrastructure

Techniques for scheduling and executing functions across a plurality of different Functions-as-a-Service (FaaS) infrastructures are provided. In one set of embodiments, a computer system can determine that a function has been invoked, where the computer system implements a spanning FaaS service platform that is communicatively coupled with the plurality of different FaaS infrastructures. In response, the computer system can retrieve metadata associated with the function, where the metadata includes criteria or policies indicating how the function should be scheduled for execution, and can retrieve information associated with each of the plurality of different FaaS infrastructures, where the information includes capabilities or characteristics of each FaaS infrastructure. The computer system can then select a FaaS infrastructure in the plurality of different FaaS infrastructures based on the retrieved metadata and the retrieved information and can schedule the function for execution on the selected FaaS infrastructure.

Scheduling and executing functions across different functions-as-a-service (FAAS) infrastructures

Growing community of inventors

Belmont, CA, United States of America

Mark Peek