Vmware, Inc.

Snowflake Inc.

Brian Charles Forney

Derek William Beard

Mark Russell Johnson

Benoit Dageville

Thierry Cruanes

Jiaqi Yan

Gabriel Tarasuk-Levin

Igor Demura

Li Zheng

Zachary James Shepherd

Jaeyun Noh

Yujie Li

Jared Sean Rosoff

Mohammad Saber Mirzaei

Brian Rak

Ali Reza Alibhai

Weili Gu

Interleaved infrastructure can interleave fragment execution during query compilation. For example, compilation can be paused, and a plan fragment is executed. The results of the plan fragment can be fed back into the compiler, which can then restart the compilation and modify the compilation based on the results of the plan fragment execution. The interleaved workflow provides a flexible, robust infrastructure, which can enable and improve a variety of database features and query optimizations.

Interleaved execution infrastructure in database engines

An example virtualized computing system includes a host cluster having a virtualization layer executing on hardware platforms of hosts, the virtualization layer supporting execution of virtual machines (VMs), the VMs including pod VMs and native VMs, the pod VMs including container engines supporting execution of containers in the pod VMs, the native VMs including applications executing on guest operating systems; and an orchestration control plane integrated with the virtualization layer, the orchestration control plane including a master server having a pod VM controller to manage lifecycles of the pod VMs and a native VM controller to manage lifecycles of the native VMs.

Declarative VM management for a container orchestrator in a virtualized computing system

A method of handling a first input/output operation (IO) from a first virtual machine (VM), wherein the first VM is located in a first data center and the first IO is directed to a data store in a second data center, includes the steps of: connecting, by a proxy located in the first data center, to the data store; after connecting to the data store, caching, by the proxy, data of the first VM stored in the data store, wherein caching the data of the first VM comprises storing the data of the first VM in a cache located in the first data center; redirecting, by a redirection filter to the proxy, the first IO; and performing, by the proxy, the first IO on the cache in the first data center.

Data mobility for immobile storage services

An example method of checking compatibility of a guest cluster executing as a virtual extension of a host cluster having an orchestration control plane managing the guest cluster, the host cluster being part of a software defined data center (SDDC), is described. The method includes: receiving, at the orchestration control plane, a guest cluster infrastructure software (GCIS) compatibility document that specifies what a GCIS of the orchestration control plane requires and offers; receiving a request for a compatibility check on the guest cluster with respect to the GCIS; obtaining, at the orchestration control plane in response to the request, an SDDC compatibility documents for the SDDC and a guest cluster compatibility document for the guest cluster; computing, at the orchestration control plane, the compatibility check in response to the GCIS compatibility document, the SDDC compatibility document, and the guest cluster compatibility document; and transmitting a result of the compatibility check from the orchestration control plane to a virtual infrastructure (VI) control plane of the SDDC.

Software compatibility checking for managed clusters in a virtualized computing system

A virtual machine (VM) is migrated from a first data center that includes a data store for handling input/output operations (IOs) of the VM to a second data center that includes a proxy configured with connection information to connect to the data store to enable the proxy to handle IOs in place of the data store. The method of migrating includes installing a first redirection filter in the first data center to redirect IOs from the first VM, which are directed to the data store, to the proxy, migrating a memory state of the first VM to a second VM in the second data center, installing a second redirection filter in the second data center to redirect IOs from the second VM, which are directed to the data store, to the proxy, and after the migration has completed, deactivating the first VM and powering on the second VM.

Instructions to fork a source VM are received, and execution of the source VM is temporarily stunned. A destination VM is created, and a snapshot of a first virtual disk of the source VM is created. A checkpoint state of the source VM is transferred to the destination VM. The source VM has one or more virtual disks. One or more virtual disks associated with the destination VM are created and reference the one or more virtual disks of the source VM. Execution of the destination VM is restored using the transferred checkpoint state and the virtual disks of the destination VM in a way that allows the source VM to also resume execution. Forking VMs using the described operation provisions destination VMs in a manner that makes efficient use of memory and disk space, while enabling source VMs to continue execution after completion of the fork operation.

Parentless virtual machine forking

Growing community of inventors

Mountain View, CA, United States of America

Brian Charles Forney