Implementing comparison of cloud service provider package offerings
US-9818127-B2 · Nov 14, 2017 · US
US10243879B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10243879-B2 |
| Application number | US-201514658030-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 13, 2015 |
| Priority date | Mar 13, 2015 |
| Publication date | Mar 26, 2019 |
| Grant date | Mar 26, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An intelligent placement engine generates a placement map that provides a configuration for deploying a service based at least in part, on one or more configuration parameters. A data center in which the service is to be hosted is defined using a data center definition, while the service is defined using a service definition. The configuration parameters include estimated probabilities calculated based on estimated resource consumption data. The resource consumption data is estimated based at least in part on historical data distributions.
Opening claim text (preview).
We claim: 1. A method comprising: receiving a request for a data center to host a service, the request including a service definition that specifies rules and requirements for the service; generating a model of the data center indicating resource allocations to support deployment of the service; prior to deploying the service in the data center, generating and rendering a placement map based at least in part on the model, the placement map comprising a visual representation of a deployment plan for deploying the service with the data center, the visual representation of the placement map including a plurality of availability groupings of hardware servers, each of the plurality of availability groupings of hardware servers visually distinguishing hardware servers in a corresponding availability grouping from hardware servers contained in a remainder of the availability groupings; subsequent to rendering the placement map, receiving approval of the placement map; and subsequent to receiving the approval, deploying the service within the data center according to the placement map. 2. A method as recited in claim 1 , wherein: the method further includes receiving a data center definition that specifies rules and requirements for a data center implementation; generating the model based, at least in part, on the data center definition; and deploying the service within the data center by at least constructing the data center according to the data center definition. 3. A method as recited in claim 2 , wherein the data center definition includes data center rules and requirements comprising one or more of: a number of physical server locations; a number of actual racks per server location; a number of maximum racks per server location; a number of availability and fault domains; a number of compute units with central processing units (CPUs) and memory; a number of storage units with storage capacity; a number of networks with capacity; a number of physical security domains; heating and cooling load and capacity; power requirements per component; cost per component; a physical weight of each component; or a physical load capacity for each rack. 4. A method as recited in claim 1 , wherein: the method further includes identifying an existing data center in which the service is to be deployed; and generating the model of the data center by at least determining a state of the data center. 5. A method as recited in claim 1 , wherein the service definition comprises one or more of: service availability requirements; possible server architectures; service availability domain rules; geographic requirements; compliance requirements; network latency requirements; bandwidth requirements; maximum network loss requirements; storage capacity requirements; or service-specific requirements. 6. A method as recited in claim 1 , wherein generating the placement map comprises generating the placement map to favor at least one or more of: a monetary cost associated with deploying the service; estimated service availability; or estimated data center resource consumption. 7. A method as recited in claim 1 , wherein generating the placement map comprises: estimating data center resource demand data based, at least in part, on the service definition; applying a transfer function to the estimated resource demand data to estimate data center resource consumption data; calculating an data center resource overload probability based, at least in part, on the estimated data center resource consumption data; and generating the placement map based, at least in part, on the overload probability. 8. A method as recited in claim 7 , wherein the data center resource demand data comprises at least one of: requests per second; or number of distinct users. 9. A method as recited in claim 7 , wherein the data center resource consumption data comprises one or more of: central processing unit (CPU) utilization percentage; a number of CPU cores; CPU speed; network bandwidth; network latency; storage capacity; disk transfers per second; or memory utilization. 10. A method as recited in claim 7 , further comprising: performing the estimating, applying, and calculating for a particular data center resource of a plurality of data center resources; and calculating an overall probability of system overload by combining the calculated overload probabilities for the plurality of data center resources; wherein generating the placement map based, at least in part, on the overload probability comprises generating the placement map based, at least in part, on the overall probability of system overload. 11. A method as recited in claim 1 , further comprising calculating a monetary cost of hosting the service. 12. A system, comprising: a data center definition store maintaining a data center definition that models infrastructure components of a data center, wherein the infrastructure components of the data center are specified according to a data center definition language; a service definition store maintaining a service definition that includes rules and architecture requirements for a service to be hosted by the data center, wherein the rules and architecture requirements are specified according to a service definition language; a calculator module configured to generate a model of the data center that indicates resource allocations to support deployment of the service; a placement map generator configured to generate and render a placement map based at least in part on the model, the placement map comprising a visual representation of a deployment plan for deploying the service with the data center prior to actual deployment of the service in the data center, the visual representation of the placement map including a plurality of availability groupings of hardware servers, each of the plurality of availability groupings of hardware servers visually distinguishing hardware servers in a corresponding availability grouping from hardware servers contained in a remainder of the availability groupings; and a deployment engine configured to deploy the service within the data center according to the placement map and which deploys the service subsequent to receiving approval to deploy the service. 13. A system as recited in claim 12 , further comprising a service requirements and rules editor configured to provide a user interface for specifying the service definition. 14. A system as recited in claim 12 , further comprising a data center requirements and rules editor configured to provide a user interface for specifying the data center definition. 15. A system as recited in claim 12 , further comprising a monitoring module configured to: monitor operational output of deployed services; apply machine learning techniques to the operational output; and update one or more of the configuration parameters. 16. A system as recited in claim 12 , further comprising a placement map viewer and editor configured to: provide a user interface for viewing the placement map; compare the placement map to rules associated with the data center; compare the placement map to rules associated with one or more services; and modify the placement map in response to user input. 17. A system as recited in claim 12 , further comprising a data center state store configured to maintain data that describes a state of the data center. 18. The system of claim 12 , wherein the placement map includes a plurality of visual representations correspondi
Electricity · mapped topic
the resource being a machine, e.g. CPUs, Servers, Terminals · CPC title
Partitioning or combining of resources · CPC title
Electricity · mapped topic
Collecting or measuring resource availability data · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.