SCALABLE, STANDARDIZED I.T. DEPLOYMENT PLATFORM

• US 20180295033A1
• Filed: 04/11/2018
• Published: 10/11/2018
• Est. Priority Date: 04/11/2017
• Status: Active Grant

• Current Assignee: Nerdio, Inc.
• Original Assignee: ADAR, Inc.
• Inventors: Vladimirskiy, Vadim, Dalvi, Amol, Malec, George
• Granted Patent: US 10,715,403 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: G06F 9/5077 Logical partitioning of resources; Management or configuration of virtualized resources specific details on emulation or internal functioning of virtual machines G06F9/455
• CPC Class Codes: G06F 9/5083 Techniques for rebalancing the load in a distributed system
• CPC Class Codes: G06Q 10/06313 Resource planning in a project environment
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0886 Fully automatic configuration
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 43/20 the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
• CPC Class Codes: H04L 43/50 Testing arrangements

Abstract

The present disclosure provides a scalable, standardized IT deployment environment that allows for deployment to any public or private cloud automatically, and without human interaction, that is resizable such that the individual resources can be released (“turned off”) when not needed and powered on when use is expected. Additionally, the present disclosure provides a cost calculation system for better understanding the costs of the IT environment as early as the pre-provisioning stage. The present disclosure also provides a system for proactively testing productivity and efficiency within the IT environment, the results of which can be fed back into the autoscaling mechanism.

Claims

1. A system that automatically scales a scalable resource in an IT environment comprising:

a scalable resource having a plurality of incrementally scalable sizes, wherein each size is defined by comprising a number of CPU cores and a first amount of RAM;

a server including a controller controlling the size of the resource;

a memory coupled to the controller, wherein the memory is configured to store program instructions executable by the controller;

wherein, in response to executing the program instructions, the controller is configured to;

receive a baseline size of the scalable resource supporting a first number of users including a first number of CPU cores and a first amount of RAM;

receive a request to resize the resource to a new size supporting a new number of users;

in response to the request to resize the resource, and without user intervention, using a users to core ratio, wherein the users to core ratio is defined as the number of users that can be supported per CPU core, calculate a minimum number of CPU cores needed to support the new size by multiplying the users to core ratio by the new number of users;

in response to the request to resize the resource, and without user intervention, using a RAM to core ratio, wherein the RAM to core ratio is defined as the amount of RAM that is needed per CPU core, calculate an amount of RAM needed for the new size by multiplying the RAM to core ratio by the number of CPU cores needed to support the new number of users;

in response to the calculation of CPU cores and the calculation of RAM, and without user intervention, identify one of the plurality of incrementally scalable sizes for the resource that comprises at least the minimum number of CPU cores needed to support the new number of users and at least the amount of RAM needed for the new size;

in response to identifying the one of the plurality of incrementally scalable sizes for the scalable resource, and without user intervention, resize the scalable resource to the identified one of the plurality of incrementally scalable sizes for the scalable resource.

2. The system of claim 1 wherein the request to resize the scalable resource to the new size supporting the new number of users is derived from an action plan comprising a schedule of a plurality of users scheduled to access the scalable resource at any given time.

3. The system of claim 2 wherein the action plan is automatically generated by a composition of a plurality of work hours profiles, each work hours profile comprising a user adjustable schedule of when an associated user is expected to use the scalable resource.

4. The system of claim 3 wherein each work hours profile is adjustable through a user adjustable graphical user interface.

5. The system of claim 1 wherein the request to resize the resource to a new size supporting the new number of users is triggered by the output of a testing server.

6. The system of claim 5 wherein the output of the testing server automatically adjusts an action plan comprising a schedule of a plurality of users scheduled to access the scalable resource at any given time, and the request to resize the scalable resource to a new size supporting the new number of users is derived from the action plan.

7. The system of claim 5 wherein the output of the testing server automatically adjusts at least one work hours profile comprising a user adjustable schedule of when an associated user is expected to use the scalable resource, wherein the adjustment of the at least one work hours profile modifies an action plan comprising a schedule of a plurality of users scheduled to access the scalable resource at any given time, and the request to resize the scalable resource to a new size supporting the new number of users is derived from the action plan.

8. The system of claim 1 further comprising:

a second scalable resource having a plurality of incrementally scalable sizes, wherein each size is defined by comprising a number of CPU cores and an amount of RAM;

wherein, in response to executing the program instructions, the controller is configured to;

receive a baseline size of the second scalable resource supporting a second number of users including a second number of CPU cores and a second amount of RAM;

receive a request to resize the resource to a second new size supporting a second number of users;

in response to the request to resize the resource, and without user intervention, using the users to core ratio, calculate a minimum number of CPU cores needed to support the second new size by multiplying the users to core ratio by the second new number of users;

in response to the request to resize the resource, and without user intervention, using the RAM to core ratio, calculate an amount of RAM needed for the second new size by multiplying the RAM to core ratio by the number of CPU cores needed to support the second new number of users;

in response to the calculation of CPU cores and the calculation of RAM, and without user intervention, identify one of the plurality of incrementally scalable sizes for the resource that comprises at least the minimum number of CPU cores needed to support the second new number of users and at least the amount of RAM needed for the second new size;

in response to identifying the one of the plurality of incrementally scalable sizes for the second scalable resource, and without user intervention, resize the second scalable resource to the identified one of the plurality of incrementally scalable sizes for the second scalable resource.

9. The system of claim 8 further comprising a non-scalable resource, wherein the request to resize the scalable resource to the new size supporting the new number of users is derived from an action plan comprising a schedule of a plurality of users scheduled to access the scalable resource at any given time and the action plan includes a schedule for turning on and off the non-scalable resource.

10. The system of claim 1 further comprising a non-scalable resource, wherein the request to resize the scalable resource to the new size supporting the new number of users is derived from an action plan comprising a schedule of a plurality of users scheduled to access the scalable resource at any given time and the action plan includes a schedule for turning on and off the non-scalable resource.

11. A method for automatically scaling a scalable resource in an IT environment including:

a scalable resource having a plurality of incrementally scalable sizes, wherein each size is defined by comprising a number of CPU cores and a first amount of RAM;

a server including a controller controlling the size of the scalable resource;

a memory coupled to the controller, wherein the memory is configured to store program instructions executable by the controller, the method comprising the step of;

in response to executing the program instructions, receiving in the controller a baseline size of the scalable resource supporting a first number of users including a first number of CPU cores and a first amount of RAM;

receiving in the controller a request to resize the scalable resource to a new size supporting a new number of users;

in response to the request to resize the scalable resource, and without user intervention, using a users to core ratio, wherein the users to core ratio is defined as the number of users that can be supported per CPU core, calculating by the controller a minimum number of CPU cores needed to support the new size by multiplying the users to core ratio by the new number of users;

in response to the request to resize the scalable resource, and without user intervention, using a RAM to core ratio, wherein the RAM to core ratio is defined as the amount of RAM that is needed per CPU core, calculating by the controller an amount of RAM needed for the new size by multiplying the RAM to core ratio by the number of CPU cores needed to support the new number of users;

in response to the calculation of CPU cores and the calculation of RAM, and without user intervention, identifying by the controller one of the plurality of incrementally scalable sizes for the scalable resource that comprises at least the minimum number of CPU cores needed to support the new number of users and at least the amount of RAM needed for the new size;

in response to identifying the one of the plurality of incrementally scalable sizes for the scalable resource, and without user intervention, resizing by the controller the scalable resource to the identified one of the plurality of incrementally scalable sizes for the scalable resource.

12. The method of claim 11 wherein the request to resize the scalable resource to the new size supporting the new number of users is derived from an action plan comprising a schedule of a plurality of users scheduled to access the scalable resource at any given time.

13. The method of claim 12 wherein the action plan is automatically generated by a composition of a plurality of work hours profiles, each work hours profile comprising a user adjustable schedule of when an associated user is expected to use the scalable resource.

14. The method of claim 13 wherein each work hours profile is adjustable through a user adjustable graphical user interface.

15. The method of claim 11 wherein the request to resize the resource to a new size supporting the new number of users is triggered by the output of a testing server.

16. The method of claim 15 wherein the output of the testing server automatically adjusts an action plan comprising a schedule of a plurality of users scheduled to access the scalable resource at any given time, and the request to resize the scalable resource to a new size supporting the new number of users is derived from the action plan.

17. The method of claim 15 wherein the output of the testing server automatically adjusts at least one work hours profile comprising a user adjustable schedule of when an associated user is expected to use the scalable resource, wherein the adjustment of the at least one work hours profile modifies an action plan comprising a schedule of a plurality of users scheduled to access the scalable resource at any given time, and the request to resize the scalable resource to a new size supporting the new number of users is derived from the action plan.

18. The method of claim 11 wherein the IT environment further comprises:

a second scalable resource having a plurality of incrementally scalable sizes, wherein each size is defined by comprising a number of CPU cores and an amount of RAM; and

the method further comprises the steps of;

receiving in the controller a request to resize the second scalable resource to a second new size supporting a second new number of users;

in response to the request to resize the second scalable resource, and without user intervention, using the users to core ratio, calculating by the controller a minimum number of CPU cores needed to support the second new size by multiplying the users to core ratio by the second new number of users;

in response to the request to resize the resource, and without user intervention, using a RAM to core ratio, calculating by the controller an amount of RAM needed for the second new size by multiplying the RAM to core ratio by the number of CPU cores needed to support the second new number of users;

in response to the calculation of CPU cores and the calculation of RAM, and without user intervention, identifying by the controller one of the plurality of incrementally scalable sizes for the second scalable resource that comprises at least the minimum number of CPU cores needed to support the second new number of users and at least the amount of RAM needed for the second new size;

in response to identifying the one of the plurality of incrementally scalable sizes for the second scalable resource, and without user intervention, resizing by the controller the second scalable resource to the identified one of the plurality of incrementally scalable sizes for the second scalable resource.

19. The method of claim 18 wherein the IT environment further comprises a non-scalable resource, and wherein the request to resize the scalable resource to the new size supporting the new number of users is derived from an action plan comprising a schedule of a plurality of users scheduled to access the scalable resource at any given time and the action plan includes a schedule for turning on and off the non-scalable resource.

20. The method of claim 11 wherein the IT environment further comprises a non-scalable resource, wherein the request to resize the scalable resource to the new size supporting the new number of users is derived from an action plan comprising a schedule of a plurality of users scheduled to access the scalable resource at any given time and the action plan includes a schedule for turning on and off the non-scalable resource.