Patent Application
20180300740
The present invention relates generally to predicting cost of an infrastructure stack, and more particularly to predicting cost of an infrastructure stack described in a template ahead of provisioning.
In a previous disclosure, the estimation of cloud computing resource costs required to process a workload to be completed uses at least two different cloud computing models. In another previous disclosure, the cloud estimator tool determines a performance estimate and a cost estimate for the cloud computing configuration based on the hardware parameters and the computing load parameters characterized in the server configuration profile and the load profile. In yet another previous disclosure, determining the cloud services offering price for a particular one of the cloud service offerings includes mapping the cloud services architecture specification to cloud service pricing information for the particular one of the cloud service offerings. A previous disclosure provides a cost analysis tool enabling the user to estimate an application configuration and provide a business-ready analysis report of the components costs based on the configuration that complies with corporate governance. Another disclosure presents a service for estimating and monitoring costs for computational applications in cloud computing environments; the cost estimation service is developed using cost models and monitoring data for a set of predefined applications.
In one aspect, a method for predicting cost of an infrastructure stack described in a template is provided. The method is implemented by a computer. The method comprises receiving from a user the template, wherein the template describes the infrastructure stack. The method further comprises analyzing information in the template, mapping the information to a set of attributes, and simulating based on the attributes an infrastructure model depicting the infrastructure stack. The method further comprises applying a predefined costing model to the infrastructure model. The method further comprises producing estimated billing for the cost of the infrastructure stack, ahead of provisioning the infrastructure stack.
In another aspect, a computer program product for predicting cost of an infrastructure stack described in a template is provided. The computer program product comprises a computer readable storage medium having program code embodied therewith. The program code is executable to receive from a user, by a computer, the template, wherein the template describes the infrastructure stack. The program code is further executable to analyze, by the computer, information in the template. The program code is further executable to map, by the computer, the information to a set of attributes. The program code is further executable to simulate, by the computer, an infrastructure model depicting the infrastructure stack, based on the attributes. The program code is further executable to apply, by the computer, a predefined costing model to the infrastructure model. The program code is further executable to produce, by the computer, estimated billing for the cost of the infrastructure stack, ahead of provisioning the infrastructure stack.
In yet another aspect, a computer system for predicting cost of an infrastructure stack described in a template is provided. The computer system comprises one or more processors, one or more computer readable tangible storage devices, and program instructions stored on at least one of the one or more computer readable tangible storage devices for execution by at least one of the one or more processors. The program instructions are executable to receive from a user, by a computer, the template, wherein the template describes the infrastructure stack; analyze, by the computer, information in the template; map, by the computer, the information to a set of attributes; simulate, by the computer, an infrastructure model depicting the infrastructure stack, based on the attributes; apply, by the computer, a predefined costing model to the infrastructure model; and produce, by the computer, estimated billing for the cost of the infrastructure stack, ahead of provisioning the infrastructure stack.
As enterprises are moving into cloud computing, deployments and configurations of virtual machines and application software become more complex. The solution to this problem is automating the deployments and configurations using templates. A template describes a cloud infrastructure stack for a cloud application in a text file with infrastructure resources that make up the cloud infrastructure stack. A template includes several major constructs, such as resources to define the computing resources, parameters to pass values to the template during runtime, conditions to define whether certain resources are created, and auto scaling that ensures that there are correct number of instances available to handle the load. The template may include several other constructs.
Templates can be classified as simple or complex based on the type of constructs inside them. In a simple template with no input parameters, conditional logic, or auto scaling, it is easier to visualize the resources that are created upon deploying the template as the resulting cloud infrastructure stack is static. However, in a complex template which accepts parameters and has conditional logic or auto scaling constructs, it is not easy to visualize the infrastructure topology as the resulting cloud infrastructure stack is dynamic. Under such a circumstance, predicting the cost of the cloud infrastructure stack is extremely difficult.
In order to overcome the problem in predicting the cost for complex templates, the embodiments of the present invention present a system that can easily predict the cost of a cloud infrastructure stack before its creation. This system predicts the cost by simulating the outcome of a template based on a set of variables such as input parameters, resources, conditional logic, and auto scaling.
The system with its prediction capabilities helps consumers of cloud computing to plan their cloud infrastructures that suits their business, budget, and other financial planning. The system also helps consumers to choose right vendors by comparing the estimated costs of various vendors. The system helps to identify the optimal amount of cloud infrastructure required to meet the anticipated needs of customers or users. After visualizing the estimated cost of the infrastructure, cloud consumers can define their cloud migration strategy.
Receiving the parsed information from template parser 103, semantic analyzer 104 extracts the attributes from the parse tree. Semantic analyzer 104 breaks compute information to CPU, disk, and memory. Semantic analyzer 104 initializes JSON objects. Semantic analyzer 104 sets the region attribute in the JSON objects. Semantic analyzer 104 sets JSON objects with the attributes representing resources that are used in simulating the output stack. Semantic analyzer 104 reads auto scaling groups. Semantic analyzer 104 extracts minimum and maximum numbers of instances from the parse tree. Semantic analyzer 104 sets instances in the JSON objects. Semantic analyzer 104 passes the JSON objects to the condition simulator 105.
Condition simulator 105 enables prediction of the behavior of the cloud computing infrastructure from a set of parameters and resources information. Condition simulator 105 analyzes the parameters and resources information from the attributes received from semantic analyzer 104. Condition simulator 105 simulates different parameter values. Condition simulator 105 simulates different conditions to true and simulates resource creation in a region selected by user 101. The simulated output depicts infrastructure stack 106 with the minimum number of instances as mentioned in the auto scaling groups before scaling out, and the simulated output depicts infrastructure stack 106 with the maximum number of instances during scaling out. A simulated model is passed from condition simulator 105 to cost estimator 107.
Cost estimator 107 receives the simulated model from condition simulator 105. Cost estimator 107 includes a pre-defined costing model. The pricing is based on the region selected by user 101 and the consumption of various resources such as CPU, disk, memory, network, and volume. Cost estimator 107 applies the pre-defined costing model to the simulated model for estimating the costs. Cost estimator 107 produces estimated billing for a cost of infrastructure stack 106 ahead of actual provisioning.
Consider a template with the following definitions. These definitions state how resources should be created under different contexts production, development, or test and scaling information to maintain application availability.
Parameters: This section defines the various input parameters that are evaluated in the conditions.
Conditions: This section defines conditions that determine how the resources are created.
Resources: This section defines details of the resources that are created.
AutoScaling: This section defines describes scaling information.
Referring to
Referring to
Referring to
Referring to
The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device, such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network (LAN), a wide area network (WAN), and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, and conventional procedural programming languages, such as the “C” programming language, or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture, including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
It is to be understood that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.
Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.
Characteristics are as follows:
On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.
Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).
Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).
Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service.
Service Models are as follows:
Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.
Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.
Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).
Deployment Models are as follows:
Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.
Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.
Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.
Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).
A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure that includes a network of interconnected nodes.
Referring now to
Referring now to
Hardware and software layer 60 includes hardware and software components. Examples of hardware components include: mainframes, RISC (Reduced Instruction Set Computer) architecture based servers, servers, blade servers, storage devices, and networks and networking components. In some embodiments, software components include network application server software and database software.
Virtualization layer 62 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers, virtual storage, virtual networks, including virtual private networks, virtual applications and operating systems, and virtual clients.
In one example, management layer 64 may provide the functions described below. Resource provisioning provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may include application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User Portal provides access to the cloud computing environment for consumers and system administrators. Service Level Management provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) Planning and Fulfillment provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.
Workloads layer 66 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: Mapping and Navigation, Software Development and Lifecycle Management, Virtual Classroom Education Delivery, Data Analytics Processing, and Transaction Processing.
