Methods, systems, and apparatus to scale in and/or scale out resources managed by a cloud automation system

Patent metadata

Field	Value
Publication number	US-2018359162-A1
Application number	US-201715617753-A
Country	US
Kind code	A1
Filing date	Jun 8, 2017
Priority date	Jun 8, 2017
Publication date	Dec 13, 2018
Grant date	—

Abstract

Methods and apparatus to scale in and/or scale out arbitrary resources managed by a cloud automation system are disclosed. An example apparatus includes an execution plan determiner to determine an execution plan for a scaling operation of an application in a platform environment based on a dependency graph; a component scaler to scale a scalable component in the platform environment corresponding to the application based on the execution plan by executing custom logic associated with the scalable component specified in the execution plan; and a dependent updater to update operation of a dependent component based on the scaling of the scalable component, the dependent component operating in conjunction with the scalable component.

First claim

What is Claimed is:

1 . An apparatus comprising:
an execution plan determiner to determine an execution plan for a scaling operation of an application in a platform environment based on a dependency graph; a component scaler to scale a scalable component in the platform environment corresponding to the application based on the execution plan by executing custom logic associated with the scalable component specified in the execution plan; and a dependent updater to update operation of a dependent component based on the scaling of the scalable component, the dependent component operating in conjunction with the scalable component.

2 . The apparatus of claim 1 , wherein the dependency graph corresponded to the dependency of components within a blueprint.

3 . The apparatus of claim 1 , wherein the component scaler is to scale the scalable component by:
scaling out the scalable component into more scalable components; or scaling in the scalable component into less scalable components.

4 . The apparatus of claim 1 , wherein the dependent component depends on the scalable component by at least one of managing or communicating with the scalable component.

5 . The apparatus of claim 1 , wherein the dependent updater is to update operation of the dependent component by updating an Internet protocol (IP) table of the dependent component, the IP table corresponding to the scalable component.

6 . The apparatus of claim 1 , further including an interface to receive instructions to scale the scalable component.

7 . The apparatus of claim 6 , wherein the interface is to receive parameters of the scaling operation from a user.

8 . The apparatus of claim 7 , wherein the component scaler is to scale the scalable component using a custom action identified in the received parameters.

9 . The apparatus of claim 6 , wherein the interface receives instructions to (A) scale in the scalable component when available resources corresponding to the scalable component are high and (B) scale out the scalable component when the available resources corresponding to the scalable component are low.

10 . The apparatus of claim 1 , wherein the dependent component operates in conjunction with the scalable component by at least one of communicating with the scalable component, interacting with the scalable component, interfacing with the scalable component, monitoring the scalable component, or managing operation of the scalable component.

11 . A tangible computer readable storage medium comprising instructions which, when executed, cause a machine to at least:
determine an execution plan for a scaling operation of an application in a platform environment based on a dependency graph; scale a scalable component in the platform environment corresponding to the application based on the execution plan by executing custom logic associated with the scalable component specified in the execution plan; and update operation of a dependent component based on the scaling of the scalable component, the dependent component operating in conjunction with the scalable component.

12 . The computer readable storage medium of claim 11 , wherein the dependency graph corresponded to the dependency of components within a blueprint.

13 . The computer readable storage medium of claim 11 , wherein the instructions cause the machine to scale the scalable component by:
scaling out the scalable component into more scalable components; or scaling in the scalable component into less scalable components.

14 . The computer readable storage medium of claim 11 , wherein the dependent component depends on the scalable component by at least one of managing or communicating with the scalable component.

15 . The computer readable storage medium of claim 11 , wherein the instructions cause the machine to update operation of the dependent component by updating an Internet protocol (IP) table of the dependent component, the IP table corresponding to the scalable component.

16 . The computer readable storage medium of claim 11 , wherein the instructions cause the machine to receive instructions to scale the scalable component.

17 . The computer readable storage medium of claim 16 , wherein the instructions cause the machine to receive parameters of the scaling operation from a user.

18 . The computer readable storage medium of claim 17 , wherein the instructions cause the machine to scale the scalable component using a custom action identified in the received parameters.

19 . The computer readable storage medium of claim 16 , wherein the instructions cause the machine to receive instructions to (A) scale in the scalable component when available resources corresponding to the scalable component are high and (B) scale out the scalable component when the available resources corresponding to the scalable component are low.

20 . The computer readable storage medium of claim 11 , wherein the dependent component operates in conjunction with the scalable component by at least one of communicating with the scalable component, interacting with the scalable component, interfacing with the scalable component, monitoring the scalable component, or managing operation of the scalable component.

21 . A method comprising:
determining an execution plan for a scaling operation of an application in a platform environment based on a dependency graph; scaling a scalable component in the platform environment corresponding to the application based on the execution plan by executing custom logic associated with the scalable component specified in the execution plan; and updating operation of a dependent component based on the scaling of the scalable component, the dependent component operating in conjunction with the scalable component.

22 . The method of claim 21 , wherein the dependency graph corresponded to the dependency of components within a blueprint.

23 . The method of claim 21 , the scaling of the scalable component includes:
scaling out the scalable component into more scalable components; or scaling in the scalable component into less scalable components.

24 . The method of claim 21 , wherein the dependent component depends on the scalable component by at least one of managing or communicating with the scalable component.

25 . The method of claim 21 , wherein the updating of the operation of the dependent component includes updating an Internet protocol (IP) table of the dependent component, the IP table corresponding to the scalable component.

26 . The method of claim 21 , further including receiving instructions to scale the scalable component.

27 . The method of claim 26 , further including receiving parameters of the scaling operation from a user.

28 . The method of claim 27 , wherein the scaling of the scalable component includes using a custom action identified in the received parameters.

29 . The method of claim 26 , further including receiving instructions to (A) scale in the scalable component when available resources corresponding to the scalable component are high and (B) scale out the scalable component when the available resources corresponding to the scalable component are low.

30 . The method of claim 21 , wherein the dependent component operates in conjunction with the scalable component by at least one of communicating wit

Assignees

• Vmware Inc

Inventors

• Savov Boris
• Dimitrov George P
• Raikov Ventsyslav
• Georgiev Kristiyan

Classifications

• G06F16/9024

  Graphs; Linked lists (G06F16/9027 takes precedence) · CPC title

• H04L41/5051 Primary

  Service on demand, e.g. definition and deployment of services in real time · CPC title

• H04L41/0896

  Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities (flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76) · CPC title

• H04L41/5096

  wherein the managed service relates to distributed or central networked applications · CPC title

• H04L41/5054

  Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components · CPC title