Systems and methods for configuring a virtual compute instance in different cloud computing environments
US-2024078124-A1 · Mar 7, 2024 · US
US12596541B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12596541-B2 |
| Application number | US-202318382293-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 20, 2023 |
| Priority date | Oct 20, 2023 |
| Publication date | Apr 7, 2026 |
| Grant date | Apr 7, 2026 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Cloning a cloud-agnostic deployment is described herein. One example method includes receiving modifications to an existing deployment created using a blueprint in a virtualized environment, and performing a deployment clone operation responsive to receiving a request to clone the deployment. The deployment clone operation can include creating an image associated with a virtual computing instance (VCI) of the deployment, creating a snapshot associated with a disk of the deployment, generating a clone blueprint based on the image and the snapshot, and deploying the clone blueprint in the virtualized environment.
Opening claim text (preview).
What is claimed is: 1 . A method of cloning a cloud-agnostic deployment, comprising: receiving modifications to an existing deployment created using a blueprint in a first virtualized environment; and performing a deployment clone operation responsive to receiving a request to clone the deployment, wherein the deployment clone operation includes: creating an image associated with a virtual machine of the deployment; creating a snapshot associated with a disk of the deployment; generating a clone blueprint based on the image of the virtual machine and the snapshot of the disk; and deploying the clone blueprint in a second virtualized environment that is different from the first virtualized environment. 2 . The method of claim 1 , wherein the method includes providing an interface associated with customizing the clone blueprint. 3 . The method of claim 2 , wherein the method includes receiving, via the interface, an indication of a preference for using a same network configuration for the clone blueprint as a network configuration used for the blueprint. 4 . The method of claim 2 , wherein the method includes receiving, via the interface, an indication of a preference for using a different network configuration for the clone blueprint than a network configuration used for the blueprint. 5 . The method of claim 1 , wherein the method includes deploying the existing deployment on a first datacenter and deploying the clone blueprint on a second datacenter. 6 . The method of claim 1 , wherein receiving modifications to the existing deployment includes executing day-two actions associated with the existing deployment. 7 . The method of claim 1 , wherein receiving modifications to the existing deployment includes receiving updates to configuration files associated with the existing deployment. 8 . A non-transitory machine-readable medium having instructions stored thereon which, when executed by a processor, cause the processor to carry out a method of cloning a cloud-agnostic deployment, the method comprising: receiving modifications to an existing deployment created using a blueprint in a first virtualized environment; and performing a deployment clone operation responsive to receiving a request to clone the deployment, wherein the deployment clone operation includes: creating an image associated with a virtual machine of the deployment; creating a snapshot associated with a disk of the deployment; generating a clone blueprint based on the image of the virtual machine and the snapshot of the disk; and deploying the clone blueprint in a second virtualized environment that is different from the first virtualized environment. 9 . The medium of claim 8 , including instructions to provide an interface associated with customizing the clone blueprint. 10 . The medium of claim 9 , including instructions to receive, via the interface, an indication of a preference for using a same network configuration for the clone blueprint as a network configuration used for the blueprint. 11 . The medium of claim 9 , including instructions to receive, via the interface, an indication of a preference for using a different network configuration for the clone blueprint than a network configuration used for the blueprint. 12 . The medium of claim 8 , including instructions to deploy the existing deployment on a first datacenter and deploy the clone blueprint on a second datacenter. 13 . The medium of claim 8 , wherein the instructions to receive modifications to the existing deployment include instructions to execute day-two actions associated with the existing deployment. 14 . The medium of claim 8 , wherein the instructions to receive modifications to the existing deployment include instructions to receive updates to configuration files associated with the existing deployment. 15 . A system comprising processing and memory resources that are configured to carry out a method of cloning a cloud-agnostic deployment, the method comprising: receiving modifications to an existing deployment created using a blueprint in a first virtualized environment; and performing a deployment clone operation responsive to receiving a request to clone the deployment, wherein the deployment clone operation includes: creating an image associated with a virtual machine of the deployment; creating a snapshot associated with a disk of the deployment; generating a clone blueprint based on the image of the virtual machine and the snapshot of the disk; and deploying the clone blueprint in a second virtualized environment that is different from the first virtualized environment. 16 . The system of claim 15 , wherein the processing and memory resources are further configured to provide an interface associated with customizing the clone blueprint. 17 . The system of claim 16 , wherein the processing and memory resources are further configured to receive, via the interface, an indication of a preference for using a same network configuration for the clone blueprint as a network configuration used for the blueprint. 18 . The system of claim 16 , wherein the processing and memory resources are further configured to receive, via the interface, an indication of a preference for using a different network configuration for the clone blueprint than a network configuration used for the blueprint. 19 . The system of claim 15 , wherein the processing and memory resources are further configured to deploy the existing deployment on a first datacenter and deploy the clone blueprint on a second datacenter. 20 . The system of claim 15 , wherein receiving modifications to the existing deployment includes executing day-two actions associated with the existing deployment.
Distribution of virtual machine instances; Migration and load balancing · CPC title
Creating, deleting, cloning virtual machine instances · CPC title
Hypervisor-specific management and integration aspects · CPC title
Image based installation; Cloning; Build to order · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.