Envoy for multi-tenant compute infrastructure

US12147693B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12147693-B2
Application numberUS-202217892920-A
CountryUS
Kind codeB2
Filing dateAug 22, 2022
Priority dateJun 14, 2018
Publication dateNov 19, 2024
Grant dateNov 19, 2024

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A data management and storage (DMS) cluster of peer DMS nodes manages data of a tenant of a multi-tenant compute infrastructure. The compute infrastructure includes an envoy connecting the DMS cluster to virtual machines of the tenant executing on the compute infrastructure. The envoy provides the DMS cluster with access to the virtual tenant network and the virtual machines of the tenant connected via the virtual tenant network for DMS services such as data fetch jobs to generate snapshots of the virtual machines. The envoy sends the snapshot from the virtual machine to a peer DMS node via the connection for storage within the DMS cluster. The envoy provides the DMS cluster with secure access to authorized tenants of the compute infrastructure while maintaining data isolation of tenants within the compute infrastructure.

First claim

Opening claim text (preview).

The invention claimed is: 1. A method for pulling a snapshot for a first virtual machine hosted in a multi-tenant cloud compute infrastructure, the method comprising: deploying an envoy in the multi-tenant cloud compute infrastructure, wherein the envoy comprises a second virtual machine, the second virtual machine one of a plurality of virtual machines allocated to a tenant in the multi-tenant cloud compute infrastructure, the second virtual machine connected with the plurality of virtual machines of the tenant including the first virtual machine via a virtual network of the tenant, wherein: the envoy is operative to interface with the multi-tenant cloud compute infrastructure and the plurality of virtual machines using a first virtualization protocol; the multi-tenant cloud compute infrastructure restricts access by a data management and storage (DMS) system to the virtual network of the tenant and to an infrastructure network connecting physical machines including a physical machine that hosts the first virtual machine of the tenant; and the infrastructure network and the virtual network use different network layers and share a physical layer; establishing, by the envoy, a connection between the envoy and the DMS system; generating the snapshot of the first virtual machine of the tenant; storing the snapshot of the first virtual machine of the tenant in a data store of computing resources provided by the multi-tenant cloud compute infrastructure; and sending, via the envoy, the snapshot to the DMS system. 2. The method of claim 1 , wherein the DMS system comprises a distributed data store implemented across a cluster of peer DMS nodes, and the method further includes storing the snapshot of an application in the distributed data store. 3. The method of claim 2 , wherein the envoy is a peer DMS node of a plurality of DMS nodes. 4. The method of claim 1 , wherein establishing the connection with the DMS system includes sending a secure socket layer (SSL) certificate to the DMS system. 5. The method of claim 1 , further comprising: prior to sending the snapshot from the first virtual machine to the DMS system, encrypting the snapshot. 6. The method of claim 1 , further comprising: generating another snapshot of another virtual machine in parallel with generating the snapshot of the first virtual machine; and sending the parallel snapshot to the DMS system. 7. The method of claim 1 , further comprising: generating a data fetch job for the first virtual machine; placing the data fetch job in a job queue accessible to the envoy to schedule the data fetch job; retrieving the data fetch job from the job queue; and in response to retrieving the data fetch job, generating the snapshot of the first virtual machine. 8. The method of claim 7 , wherein a peer DMS node generates the data fetch job and places the data fetch job in the job queue stored in a distributed database of the DMS system. 9. The method of claim 8 , wherein the envoy retrieves the data fetch job from the job queue. 10. The method of claim 8 , wherein: the envoy retrieves the data fetch job from the job queue; and the method further includes, in response to retrieving the data fetch job, sending a request to a virtualization module of the first virtual machine via the envoy to generate the snapshot of the first virtual machine. 11. A multi-tenant compute infrastructure, comprising: a first virtual machine of a tenant of the multi-tenant compute infrastructure; and an envoy deployed in the multi-tenant compute infrastructure, wherein the envoy comprises a second virtual machine, the second virtual machine one of a plurality of virtual machines allocated to the tenant in the multi-tenant compute infrastructure, the second virtual machine connected with the plurality of virtual machines of the tenant including the first virtual machine via a virtual network of the tenant, wherein: the envoy is operative to interface with the multi-tenant compute infrastructure and plurality of virtual machines using a first virtualization protocol; the multi-tenant compute infrastructure restricts access by a data management and storage (DMS) system to the virtual network of the tenant and to an infrastructure network connecting physical machines including a physical machine that hosts the first virtual machine of the tenant; the infrastructure network and the virtual network use different network layers and share a physical layer; and the envoy is configured to: establish a connection between the envoy and the DMS system; generate a snapshot of the first virtual machine of the tenant; store the snapshot of the first virtual machine of the tenant in a data store of computing resources provided by the multi-tenant compute infrastructure; and send, via the envoy, the snapshot to the DMS system. 12. The multi-tenant compute infrastructure of claim 11 , wherein the DMS system comprises a distributed data store implemented across a cluster of peer DMS nodes, and the envoy is further configured to store the snapshot of an application in the distributed data store. 13. The multi-tenant compute infrastructure of claim 12 , wherein the envoy is a peer DMS node of a plurality of DMS nodes. 14. The multi-tenant compute infrastructure of claim 11 , wherein establishing the connection with the DMS system includes sending a secure socket layer (SSL) certificate to the DMS system. 15. The multi-tenant compute infrastructure of claim 11 , wherein the envoy is operative to, prior to sending the snapshot from the first virtual machine to the DMS system, encrypt the snapshot. 16. The multi-tenant compute infrastructure of claim 11 , wherein the envoy is operative to: generate another snapshot of another virtual machine in parallel with generating the snapshot of the first virtual machine; and send the parallel snapshot to the DMS system. 17. The multi-tenant compute infrastructure of claim 11 , wherein the DMS system is operative to: generate a data fetch job for the first virtual machine; and place the data fetch job in a job queue accessible to the envoy to schedule the data fetch job; and wherein the envoy is operative to: retrieve the data fetch job from the job queue; and in response to retrieving the data fetch job, generate the snapshot of the first virtual machine. 18. The multi-tenant compute infrastructure of claim 17 , wherein a peer DMS node is operative to generate the data fetch job and place the data fetch job in the job queue stored in a distributed database of the DMS system. 19. The multi-tenant compute infrastructure of claim 18 , wherein the envoy is operative to retrieve the data fetch job from the job queue. 20. The multi-tenant compute infrastructure of claim 18 , wherein the envoy is operative to: retrieve the data fetch job from the job queue; and in response to retrieving the data fetch job, send a request to a virtualization module of the first virtual machine via the envoy to generate the snapshot of the first virtual machine.

Assignees

Inventors

Classifications

  • Error detection or correction of the data by redundancy in operations (error detection or correction of the data by redundancy in hardware G06F11/16) · CPC title

  • Entity profiles · CPC title

  • I/O management, e.g. providing access to device drivers or storage · CPC title

  • above the transport layer · CPC title

  • using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263) · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12147693B2 cover?
A data management and storage (DMS) cluster of peer DMS nodes manages data of a tenant of a multi-tenant compute infrastructure. The compute infrastructure includes an envoy connecting the DMS cluster to virtual machines of the tenant executing on the compute infrastructure. The envoy provides the DMS cluster with access to the virtual tenant network and the virtual machines of the tenant conne…
Who is the assignee on this patent?
Rubrik Inc
What technology area does this patent fall under?
Primary CPC classification G06F9/45558. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Nov 19 2024 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 9 related publications on this page (citations in our corpus or others sharing the same primary CPC).