Cloud-based virtual machines and offices

• US 10,284,437 B2
• Filed: 11/23/2016
• Issued: 05/07/2019
• Est. Priority Date: 09/30/2010
• Status: Active Grant

• Current Assignee: eFolder, Inc.
• Original Assignee: eFolder, Inc.
• Inventors: Scallan, Todd, Yelisetti, Shravya, Modh, Saurabh, Ananyev, Vlad, Kornilenko, Leonid, Edwards, William Scott
• Primary Examiner(s): Yohannes, Tesfay
• Application Number:
  US15/360,836
• Publication Number:
  US 20170075719A1
• Time in Patent Office: 895 Days
• Field of Search: 709203, 709220, 709222, 370260, 370200
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1484 involving virtual machines
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: G06F 11/203 using migration
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 2201/85 Active fault masking without idle spares active fault masking without idle spare hardware where processing functionality is redundant G06F11/2035
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5051 Service on demand, e.g. definition and deployment of services in real time
• CPC Class Codes: H04L 41/5058 Service discovery by the service manager
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

Cloud-based virtual machines and offices are provided herein. Methods may include establishing a cloud-based virtual office using a runbook that is pre-configured with computing resource settings for VMs as well as VM dependencies and sequences that create the virtual office or virtual private cloud. Multiple runbooks can be created to cover various scenarios such as disaster recovery and sandbox testing, by example.

Claims

1. A method, comprising:

selecting one or more virtual machines for which configurations will be included in a runbook, the runbook being used to establish a virtual office;

selecting, for each of the one or more virtual machines, computing device configurations;

specifying a dependency between at least two of the one or more virtual machines, the dependency comprising a hierarchical relationship between the at least two of the one or more virtual machines that corresponds to an order in which to start the at least two of the one or more virtual machines;

generating the runbook that comprises the computing device configurations and the dependency;

storing the runbook in a replication system;

receiving a request to use the runbook, wherein the request comprises a selection of a recovery method from any of a data restore, an archive restore, a disaster recover test, a disaster recovery production failover, and a test and development environment;

instantiating the at least two of the one or more virtual machines by dedicating computing resources to the at least two of the one or more virtual machines using the computing device configurations and the dependency to create the virtual office; and

providing access to the virtual office to a user.

2. The method according to claim 1, further comprising deleting the runbook when the virtual office is terminated by the user.

3. The method according to claim 1, wherein the request is generated automatically upon occurrence of a failover event.

4. The method according to claim 1, further comprising:

selecting the runbook;

instantiating the at least two of the one or more virtual machines by dedicating computing resources to the at least two of the one or more virtual machines using the computing device configurations and the dependency; and

providing access to the at least two of the one or more virtual machines to a user.

5. The method according to claim 1, further comprising establishing any of:

a virtual private network selection;

port forwarding; and

a site-to-site virtual private network settings.

6. The method according to claim 5, wherein the virtual private network selection comprises any of:

a split tunneling selection;

a site gateway Internet protocol address; and

a site netmask.

7. The method according to claim 5, wherein the site-to-site virtual private network settings comprises any of:

an endpoint name;

a public Internet protocol address;

a gateway;

a netmask; and

endpoint Internet protocol address.

8. The method according to claim 1, further comprising:

calculating the priority level; and

ranking the at least two of the one or more virtual machines based on calculated priority levels.

9. The method according to claim 1, further comprising establishing a priority level for the at least two of the one or more virtual machines, wherein the runbook further comprises the priority level.

10. A method, comprising:

evaluating a network topology of a target network, the network topology defining;

dependencies of computing devices; and

computing device configurations of the computing devices;

generating a runbook from the network topology, the runbook comprising;

a) an identification of the computing devices to be replicated as virtual machines of a virtual private cloud;

b) one or more subnets, where each of the virtual machines is assigned to the one or more subnets; and

c) computing device configurations for each of the virtual machines that comprise dependencies between the virtual machines that define an order in which to start the virtual machines, wherein the computing device configurations for each of the virtual machines comprise the computing device configurations of the computing devices and the dependencies between the virtual machines comprise the dependencies of the computing devices;

receiving a request to execute the runbook to establish the virtual private cloud;

executing the runbook to establish the virtual private cloud;

obtaining restore points the virtual machines, the restore points being associated with the computing devices;

preparing the virtual private cloud by establishing the virtual machines using the restore points and the computing device configurations in the runbook; and

providing access to the virtual private cloud to a user.

11. The method according to claim 10, wherein a first portion of the virtual machines are assigned to a first subnet of the one or more subnets and a second portion of the virtual machines are assigned to a second subnet of the one or more subnets.

12. The method according to claim 10, further comprising:

terminating the virtual private cloud; and

executing a second runbook to establish a second virtual private cloud, wherein the second virtual private comprises subnet configurations copied from prior execution of the runbook.

13. The method according to claim 10, further comprising applying wait times for establishing one or more of the virtual machines.

14. The method according to claim 10, wherein the one or more subnets each define a network boundary based on security attributes.

15. The method according to claim 10, wherein the restore points are selected based on a user-selected date.