Over-provisioning cloud resources using dependency maps and utilization triggers

Patent metadata

Field	Value
Publication number	US-10831518-B2
Application number	US-201715828461-A
Country	US
Kind code	B2
Filing date	Dec 1, 2017
Priority date	Dec 1, 2017
Publication date	Nov 10, 2020
Grant date	Nov 10, 2020

Abstract

Machine logic (for example, software) for compressing the image of an instance of a VM/container during time period(s) when the VM/container instance is inactive. A proxy is used to handle requests made to the VM/container instance during periods when it is inactive. A dependency graph is used to determine that a related set of instances of VM/containers so that: (i) when one of the VM/container instances of the related set is deactivated, then the whole set of VM/container instances are deactivated together; and/or (ii) when one of the VM/container instances of the related set is reactivated, then the whole set of VM/container instances are reactivated together.

First claim

What is claimed is:

1. A computer-implemented method comprising:
actively running a first instance of a VM/container on a first computer device;
receiving a first request to deactivate the first instance of the VM/container;
responsive to the first request to deactivate, storing an image of the first instance, with the storing including:
generating an uncompressed image file data set corresponding to the first instance,
compressing, by a file level data compression algorithm, the uncompressed image file data set to generate a compressed image file data set, and with the file level data compression algorithm being a DEFLATE type compression algorithm, and
storing the compressed image file data set in a data storage device;

deactivating, by a first proxy, the first instance of the VM/container;
responsive to the deactivation of the first instance of the VM/container, receiving, by the first proxy, a first data communication from an address on a first address list;
responsive to the receipt of the first data communication, reactivating, by the first proxy, the first instance of the VM/container based, at least in part, upon the first data communication being from the address on the first address list;
receiving a second request to deactivate the first instance of the VM/container;
deactivating, by the first proxy, the first instance of the VM/container;
responsive to the deactivation of the first instance of the VM/container, receiving, by the first proxy, a first data communication from an address on a second address list; and
responsive to the receipt of the first data communication from the address on the second list, sending, by the first proxy, a responsive message to a source of the first data communication from the address on the second list to indicate that the first instance of the VM/container will be re-activated at a predetermined future time.

2. The method of claim 1 wherein the data storage device is a non-volatile data storage device.

3. The method of claim 1 further comprising:
receiving a request to reactivate the first instance of the VM/container; and
responsive to the request to reactivate, reactivating the first instance of the VM/container, with the reactivation including:
reading the compressed image file data set from the data storage device,
decompressing, by the file level data compression algorithm, the compressed image file data set to generate a decompressed image file data set corresponding to the first instance of the VM/container, and
activating the decompressed image file data set to begin actively running again the first instance of the VM/container.

4. The method of claim 3 wherein the VM/container is a virtual machine.

5. The method of claim 3 wherein the VM/container is a container.

6. The method of claim 1 wherein the file level compression algorithm is agnostic.

7. The method of claim 1 wherein the file level compression algorithm is one of the following types: PKZIP, Gzip, tar, 7z, RAR.

8. The method of claim 1 further comprising:
determining that the first computer device is going into hibernation;
wherein the request to deactivate is made in response to the determination that the first computer device is going into hibernation.

9. The method of claim 1 further comprising:
determining that the first instance of the VM/container has been idle a predetermined amount of time;
wherein the request to deactivate is made in response to the determination that the VM/container has been idle a predetermined amount of time.

Assignees

• IBM

Inventors

• Wyble Christopher D
• Boss Gregory J
• Ngo Ton A
• Monov Simeon D

Classifications

• H04L67/56

  Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54) · CPC title

• G06F9/4418 Primary

  Suspend and resume; Hibernate and awake · CPC title

• Y02D10/00

  Energy efficient computing, e.g. low power processors, power management or thermal management · CPC title

• G06F8/63

  Image based installation; Cloning; Build to order · CPC title

• H03M7/60

  General implementation details not specific to a particular type of compression · CPC title