Matching a usage history to a new cloud
Embodiments relate to systems and methods for identifying usage histories and end users that may benefit from being redeployed to a new cloud-based network. In particular, a new cloud can receive usage histories corresponding to end user usage in a respective set of other pre-existing clouds. In embodiments, the new cloud can determine whether the new cloud provides sufficient resources to properly host each end user recorded in the usage histories. Further, the new cloud can determine whether there is a cost benefit or other advantage for a user to move to the new cloud. In embodiments, a deployment recommendation may be sent to an administrator of the cloud associated with the desirable usage history.
1. A method comprising:
receiving, by a processor, a set of usage histories, wherein a usage history among the set of usage histories comprises resource usage data and corresponding billing data associated with a user of an existing server;
determining, using the processor and in view of the resource usage data of the usage history, a pattern of resource usage associated with the user and whether a new server has sufficient resources to host the user in view of the pattern of resource usage associated with the user comprising simulating an execution of the usage history on the resources of the new server to produce simulation results and determining that the new server has sufficient resources if the simulation results indicate that a resource capacity of the new server is not exceeded, wherein the existing server and the new server are deployed in a cloud;
determining, using the processor in view of the billing data of the usage history and in view of the pattern of resource usage associated with the user, whether the new server provides a pricing benefit to the user; and
recommending, in view of the pattern of resource usage associated with the user, if the new server has sufficient resources to host the user and if the new server provides the pricing benefit, that the user deploy on the new server.
2. The method of claim 1 , wherein determining whether the new server has sufficient resources comprises:
comparing the resource usage data of the usage history to a corresponding resource capacity of the new server; and
determining that the new server has sufficient resources if the corresponding resource capacity is equal to or greater than the resource usage data.
3. The method of claim 1 , wherein recommending comprises:
notifying an administrator of the new server regarding recommending that the user deploy on the new server.
4. The method of claim 1 , wherein recommending comprises:
notifying the user regarding recommending that the user deploy on the new server.
5. The method of claim 1 , wherein recommending comprises:
redeploying the user to the new server from a server that is currently hosting the user.
6. The method of claim 1 , wherein determining whether the new server provides a pricing benefit to the user comprises:
comparing the billing data of the usage history to a corresponding price available from the new server; and
determining that the new server provides the pricing benefit if the corresponding price is equal to or less than the billing data.
7. The method of claim 6 , wherein comparing the billing data of the usage history to a corresponding price comprises:
comparing an aggregate of billing data over a time period to a corresponding aggregate of prices available from a new server.
8. The method of claim 1 , wherein the usage history comprises resource consumption metrics and resource billing metrics.
9. A non-transitory computer-readable storage medium containing instructions that, when executed by a processor, implement operations comprising:
receiving, by the processor, a set of usage histories, wherein a usage history among the set of usage histories comprises resource usage data and corresponding billing data associated with a user of an existing server;
determining, in view of the resource usage data of the usage history, a pattern of resource usage associated with the user and whether a new server has sufficient resources to host the user in view of the pattern of resource usage associated with the user comprising simulating an execution of the usage history on the resources of the new server to produce simulation results and determining that the new server has sufficient resources if the simulation results indicate that a resource capacity of the new server is not exceeded, wherein the existing server and the new server are deployed in a cloud;
determining, in view of the billing data of the usage history and in view of the pattern of resource usage associated with the user, whether the new server provides a pricing benefit to the user; and
recommending, in view of the pattern of resource usage associated with the user, if the new server has sufficient resources to host the user and the new server provides the pricing benefit, that the user deploy on the new server.
10. A system comprising:
a memory to contain instructions; and
a processor, communicatively connected with the memory, to:
receive, by the processor, a set of usage histories, wherein a usage history among the set of usage histories comprises resource usage data and billing data for a user of an existing server;
determine, in view of the resource usage data of the usage history, a pattern of resource usage associated with the user and whether a new server has sufficient resources to host the user in view of the pattern of resource usage associated with the user comprising simulate an execution of the usage history on the resources of the new server to produce simulation results and determine that the new server has sufficient resources if the simulation results indicate that a resource capacity of the new server is not exceeded, wherein the existing server and the new server are deployed in a cloud;
determine, in view of the billing data of the usage history and in view of the pattern of resource usage associated with the user, whether the new server provides a pricing benefit to the user; and
recommend, in view of the pattern of resource usage associated with the user, if the new server has sufficient resources to host the user and the new server provides the pricing benefit, that the user deploy on the new server.
11. The system of claim 10 , wherein recommending comprises:
notify an administrator of the new server regarding recommending that the user deploy on the new server.
12. The system of claim 10 , wherein recommending comprises:
notify the user regarding recommending that the user deploy on the new server.
13. The system of claim 10 , wherein recommending comprises:
redeploy the user to the new server from a server that is currently hosting the user.
14. The system of claim 10 , wherein determine whether the new server provides a cost benefit to the user comprises:
compare the billing data of the usage history to a corresponding price available from the new server; and
determine that the new server provides the pricing benefit if the corresponding price is equal to or less than the billing data.
15. The system of claim 14 , wherein compare the billing data of the usage history to a corresponding price comprises:
compare an aggregate of billing data over a time period to a corresponding aggregate of prices available from a new server.
16. The system of claim 10 , wherein the usage history comprises resource consumption metrics and resource billing metrics.
17. The system of claim 10 , further comprising:
a network interface, connected to the processor, to communicate with existing servers to receive the set of usage histories.