Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
  • G06F9/5061—Partitioning or combining of resources
  • G06F9/5072—Grid computing

Definitions

• Computer applications are developed to operate on a particular computing platform.
• computing platforms are designed to control a single computer and, as a result, the applications designed for the computing platform also are designed to operate on a single computer.
• the Internet has introduced new ways in which computer programs are deployed to computers. While the method of deployment has changed, the end users still expect computer applications to operate the same regardless if they are deployed over the Internet or residing on the end user's computer.
• Embodiments of the present invention relate to systems, methods and computer storage media for operating a scalable computing platform.
• a service description describing a requested service is received.
• Upon receiving the service description a determination of the required resources and the available resources is made.
• the resources required to sustain the deployment of the service are mapped to the available resources of the computing platform so the service may be deployed.
• An instance description is amended with each deployment of the service to allow for sustained deployment of the service.
• FIG. 1 is a block diagram of an exemplary computing environment suitable for use in implementing embodiments of the present invention
• FIG. 2 is a block diagram of an exemplary system for operating a scalable computing platform, in accordance with an embodiment of the present invention
• FIG. 3 is a flow diagram of an exemplary method for operating a scalable computing platform, in accordance with an embodiment of the present invention
• FIG. 4 is a diagram representing the lifecycle of a service description through various assemblies, in accordance with embodiments of the present invention
• FIG. 5 is a graphical representation of an exemplary topology, in accordance with an embodiment of the present invention.
• FIG. 6 is a block diagram representing a load balancing channel, in accordance with an embodiment of the present invention.
• FIG. 7 is a block diagram representing a stateful switch channel, in accordance with an embodiment of the present invention.
• FIG. 8 is a block diagram representing a stateless switch channel, in accordance with an embodiment of the present invention.
• FIG. 9 is a flow diagram of the service deployment evolution, in accordance with an embodiment of the present invention.
• Embodiments of the present invention relate to systems, methods and computer storage media for operating a scalable computing platform.
• a service description describing a requested service is received.
• Upon receiving the service description a determination of the required resources and the available resources is made.
• the resources required to sustain the deployment of the service are mapped to the available resources of the computing platform so the service may be deployed.
• An instance description is amended with each deployment of the service to allow for sustained deployment of the service.
• the present invention provides a method for operating a scalable computing platform.
• the method includes receiving a request for one or more services wherein a service contract is in association with the request for the service(s).
• Each one of the service(s) is comprised of an element and a channel, and wherein the channel is at least one of a load balancer channel, a stateful switch channel, and a stateless switch channel.
• the method also includes receiving a service description for the one or more services, wherein the service description is comprised of at least one of an application configuration setting, a system configuration setting, and a resource reference.
• the method continues with the determination of the resources required to deploy the one or more services as well as determining at least one available resource of the scalable computing platform thereinafter a first instance description is produced. Once the resources required and available have been determined, the method includes mapping of those resources, as well as deploying the one or more services to generate a result. The method then continues with the transmission of the deployed service result. [0017] In another aspect, the present invention provides a method for operating a scalable computing platform.
• the method includes receiving an additional request for one or more services, determining the resources required to deploy the service(s), determining at least one available resource of the scalable computing system, producing a second instance description, mapping the resources required to deploy the service(s) to the available resource(s) of the scalable computing platform, deploying the service(s) to generate a result and transmitting the result.
• the method also provides for the modification of the first instance description and the second instance description to reflect the mapping of the resources required to deploy the service(s) to the at least one available resource(s) of the scalable computing platform.
• Yet another aspect of the present invention provides a computer system embodied on one or more computer storage media having computer-executable instruction embodied thereon for performing a method for operating a scalable computing platform.
• the method comprises a receiving component that receives a request for services, including a service description having a description of resource(s) required to deploy the service associated therewith, a resource determining component that determines the resource(s) required to deploy the service, a resource mapping component that maps the resource(s) required to deploy the service, and a deploying component that deploys the service in association with the mapped resource(s) required to deploy the service.
• computing device 100 an exemplary operating environment suitable for implementing embodiments of the present invention is shown and designated generally as computing device 100.
• Computing device 100 is but one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the computing environment 100 be interpreted as having any dependency or requirement relating to any one or combination of modules/components illustrated.
• Embodiments may be described in the general context of computer code or machine-useable instructions, including computer-executable instructions such as program modules, being executed by a computer or other machine, such as a personal data assistant or other handheld device.
• program modules including routines, programs, objects, modules, data structures, and the like, refer to code that performs particular tasks or implements particular abstract data types.
• Embodiments may be practiced in a variety of system configurations, including hand-held devices, consumer electronics, general- purpose computers, specialty computing devices, etc. Embodiments may also be practiced in distributed computing environments where tasks are performed by remote -processing devices that are linked through a communications network.
• computing device 100 includes a bus
• Bus 110 that directly or indirectly couples the following devices: memory 112, one or more processors 114, one or more presentation modules 116, input/output (I/O) ports 118, I/O modules 120, and an illustrative power supply 122.
• Bus 110 represents what may be one or more busses (such as an address bus, data bus, or combination thereof).
• Computing device 100 typically includes a variety of computer-readable media.
• computer-readable media may comprise Random Access Memory (RAM); Read Only Memory (ROM); Electronically Erasable Programmable Read Only Memory (EEPROM); flash memory or other memory technologies; CDROM, digital versatile disks (DVD) or other optical or holographic media; magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, carrier waves or any other medium that can be used to encode desired information and be accessed by computing device 100.
• RAM Random Access Memory
• ROM Read Only Memory
• EEPROM Electronically Erasable Programmable Read Only Memory
• flash memory or other memory technologies
• CDROM compact discs
• DVD digital versatile disks
• magnetic cassettes magnetic tape
• magnetic disk storage or other magnetic storage devices carrier waves or any other medium that can be used to encode desired information and be accessed by computing device 100.
• Memory 112 includes computer-storage media in the form of volatile and/or nonvolatile memory.
• the memory may be removable, non-removable, or a combination thereof.
• Exemplary hardware devices include solid-state memory, hard drives, optical-disc drives, etc.
• Computing device 100 includes one or more processors that read data from various entities such as memory 112 or I/O modules 120.
• Presentation module(s) 116 present data indications to a user or other device.
• Exemplary presentation modules include a display device, speaker, printing module, vibrating module, and the like.
• I/O ports 118 allow computing device 100 to be logically coupled to other devices including I/O modules 120, some of which may be built in.
• Illustrative modules include a microphone, joystick, game pad, satellite dish, scanner, printer, wireless device, and the like.
• FIG. 2 a block diagram is shown that illustrates an exemplary system 200 for a scalable computing platform, in accordance with an embodiment of the present invention.
• Computing platform 200 is but one example of a suitable computing platform and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the computing platform 200 be interpreted as having any dependency or requirement relating to any one or combination of modules/components illustrated.
• computing platform 200 contains a receiving component 212, a service description generating component 214, a resource determining component 216, a resource mapping component 218, a deploying component 220, all in communication with one another via a network 210.
• the network 210 may include, without limitation, one or more local area networks (LANs) and/or wide area networks (WANs). Such networking environments are commonplace in offices, enterprise-wide computing networks, intranets, and the Internet. Accordingly, the network 210 is not further described herein.
• An exemplary embodiment of computing platform 200 assembles various components into an instantiator 240 and a deploy er 250.
• the resource determining component 216 is assembled into the instantiator 240.
• the resource mapping component 218 and the deploying component 220 are assembled into the deploy er 250.
• the illustrated embodiment of computing platform 200 assembles the components of the invention into the particular assemblies identified, it will be understood and appreciated by those skilled in the art that assemblies are not limited to the instantiator 240 and the deploy er 250. It will also be understood and appreciated by those skilled in the art that the components are not restricted to the particular identified assemblies nor are the components necessarily assembled at all.
• the receiving component 212 receives a request for service.
• the service is a structured entity wherein the structure is determined by a service description that is received by the receiving component 212.
• the service description received is fitted to the service contract associated with the service that is requested.
• a service description presents a set of configuration settings, a series of input interfaces, and a series of dependencies on the interface of other services.
• the service In order for the service to be a structured entity, it is comprised of a structured set of roles, groups and channels. Roles provide a template description of a computer program. Roles are described by indicating the computer code implementing the role, the hosting environment required by the role, the configuration settings, the role's set of endpoints, and a model of their performance.
• the role's configuration settings may include collective settings which are shared by all instances of the role, or individual settings that are particular to each instance of the role. Additionally, the set of endpoints included in the description of a role are further classified as either input endpoints and output endpoints. The output endpoint of a role provides a connection point from a source element to the input endpoint of a target element. A role instance communicates through its endpoints. A role instance is also defined by the resources included in its description. Roles may also be grouped as a set of roles to forms a group. The minimal group size consists of a single role. Therefore, groups and roles may be described as an element when the two do not need to be differentiated.
• the service also includes channels. Channels establish connections between various elements through the element's end points.
• Receiving component 212 receives a request for a service and a service description.
• a service description includes information constraining how the service can be configured and deployed, as well as information that can be used to analyze the performance of the service. Additionally, the service description provides sufficient information so that the invention can allocate and coordinate the resources required to sustain the deployment of the service.
• the system description and an instance description includes the elements and channels that outline the service.
• the instance description is produced by the resource determining component 216 to incorporate the elements and channels that outline the service as included in the received service description as well as the resources that are determined to be required for a particular instance of the service to be deployed.
• a description of the relationship between the various elements and the various channels represents the topology of the service.
• the topology describes the endpoints the channels connect the various elements. If the channels or the elements are changed, the topology is also changed for the service.
• the topology of a service includes information relating to the connectivity of the elements for the service to function properly, the routing between the elements' input endpoints and a service's input interface, the routing between the elements' output endpoints and a service's dependencies, the minimum number of replicas of each element that is needed, the guidelines on maintenance that should occur to avoid interrupting the service, descriptions of performance parameters that can be utilized to evaluate the service performance, indications of affinity among roles that inform the deploy er 250 of proper mapping, and indications of propagation of configuration settings between elements
• a channel can be any of a load balancer channel, a stateful switch channel, and a stateless switch channel.
• a load balancer channel connects one output endpoint from a source element to the input endpoint of a target element. Traffic from the source element is redistributed to one of the target elements according to some policy associated with the channel. Examples of the policies that may determine the distribution of traffic include, but are not limited to, uniform distribution, least-cost routing, least-time routing, affinity-correlation routing, or any other distribution scheme that facilitates the connection between two elements.
• the load balancer channel has capacity to handle any number of input endpoints and output endpoints.
• the source elements will only have to include the information of the virtual address associated with the load balancer of the load balancing channel. The load balancer will then redistribute the connection to the plurality of target elements regardless of the number of target elements.
• An exemplary load balancing channel in accordance with an embodiment of the present invention is shown in the block diagram of FIG. 6 and represented generally as reference numeral 610.
• a plurality of source elements 620, 622, and 624 are expected to establish a load balancer channel connection with a plurality of target element 630 and 632.
• the plurality of source elements 620, 622, and 624 do not have the necessary information to establish a direct connection with target elements 630 and 632. Instead, source elements 620, 622, and 624 have a virtual address that is directed to load balancer 610.
• Source elements 620, 622, and 624 therefore connect with load balancer 610.
• Load balancer 610 then redistributes the connections to target elements 630 and 632 based on a policy assigned to that particular load balancer channel.
• the second type of channel is a stateful switch channel.
• a stateful switch channel is associated with "m" different addresses, where "m” is the number of instances of the target element.
• the source element is aware of the number of "m” target elements. The source element then selects one of the "m” instances of the target element with which to connect. The source elements therefore include a designation of which "m” instance with which to connect.
• a router within the channel then directs the connection to the appropriate target element.
• An exemplary, but not limiting, embodiment provides for the source elements to store the "m" addresses in the configuration of each of the source element instances and include the selected "m” address with the requested target connection. A router within the stateful switch then directs the connection to the appropriate target element.
• the stateful switch channel includes router 710, a plurality of source elements 720, 722, and 724, as well as a plurality of target elements 730 and 732.
• Each of the source elements 720, 722, and 724 are aware of the two target elements 730 and 732. Therefore, each of the source elements 720, 722, and 724 make a selection to direct their connection to one or more particular target elements.
• the connection is directed to the router 710 that distributes the connection to the appropriate target element(s) 730 and/or 732.
• a third type of channel, a stateless switch channel requires the source element to select among the target elements.
• the stateless switch channel does not require the configuration of the target element address from the source element. Therefore, the stateless switch channel provides that a source elements determines that a connection is required with a target element, but the selected target element is not identified in the connection.
• the router included in the stateless switch channel connects the source element with the target elements based on a communication protocol, an instruction provided by another element, or another distribution director.
• the stateless switch channel includes a router 810 and source elements 820, 822, and 824, as well as target elements 830 and 832.
• Each of the source elements 820, 822, and 824 are aware of the two target elements 830 and 832.
• the connection from the source elements 820, 822, 824 does not include distribution directions for the router 810 to distribute the connection to the identified target elements 830 or 832. Instead, in this exemplary embodiment, the router 810 distributes the connections based on a communication received from an alternative channel. As a result, the connections between source elements 820, 822, 824 are connected to target elements 830 and 832 based on distribution directions received by the router 810.
• FIG. 6, FIG. 7, and FIG. 8 are exemplary in nature and are not intended to be limiting with respect to the number of source elements, target elements, channels connecting elements, or the connections established within each channel.
• the service description may also include the configuration settings and the resource references.
• the configuration settings include application configuration settings and system configuration settings.
• Application configuration settings are part of an element's definition and therefore the declaration and resulting interpretation of the application configuration are intrinsic to the semantics and behavior of the element.
• the application configuration settings of an element may either be per-instance or common settings. A common setting is shared by all instances of the element. A per-instance setting can have different settings for each unique instance of the element.
• a second type of a configuration setting is a system configuration setting.
• System configuration settings are properties of an element's embedding or incorporation within a group of roles. Unlike application configuration settings that are intrinsic to the element's definition, the system configuration settings are instead interpreted and utilized by the computing platform. The assignment of the system configuration settings is under the control of the computing platform which operates within policies that have been assigned to that system configuration setting.
• Resource references may also be included in the service description.
• Resource references indicate the need to access some of the computing-platform-provided resources.
• the kinds of resources available are dictated by the computing platform. Examples of the resources include local file system space that conforms to a particular application program interface such as file, directory, and drive set resources. Additionally, log streams and event counters are examples of the resources made available by the computing platform.
• the instantiator 240 includes the resource determining component 216.
• the role of the instantiator 240 is to create a service to deploy based on the service description and the instance description.
• the instantiator provides evolving instances of the service for the deploy er 250 to deploy through the deploying component 220 and the resource mapping component 218.
• the instantiator 240 utilizes the resources that are determined for an instance of the service to be deployed as well as the service description to produce the instance description to allow either an initial deployment of the service or a progressive deployment of the service. Regardless of whether it's an initial deployment or a progressive deployment, the instantiator 240 determines the availability of the service.
• the instantiator 240 utilizes the resource determining component 216 to determine the resources required to deploy the service, as well as the resources available to deploy the service according to an agreement with the deploy er 250.
• the resource determining component 216 evaluates the service description and determines how the service should be configured to scale the service to provide sufficient service capacity to meet the current demand for the service. In order to configure the service for scaled deployment, the resource determining component evaluates, in part, the resources required to meet the instance's demand for the service.
• the resource determining component 216 then produces an instance description based on the resource determining component 216 determination of resources required and available to provide sufficient capacity of service. [0042]
• the deploy er 250 receives the instance description provided by the instantiator 240.
• the deploy er 250 utilizes the resource mapping component 218 to map the required resources detailed in the service description to physical devices and their associated connectivity settings.
• Examples of physical devices that the resource can be mapped to include, without limitation, computing device 100 of FIG 1. Additionally, and in support of computing device 100 of FIG. 1, physical devices that the resources may be mapped to are devices typically associated with data centers which include, by way of example only, switches, servers, racks, routers, virtual computing devices, remote computing devices, peer-to-peer computing devices, dedicated computing devices, and assignable computing devices. It will be understood and appreciated by those of ordinary skill in the art that the listed physical devices are not intended to limit the scope of physical devices to which the service description required resources may be mapped.
• the connectivity setting for the physical device may include the physical device's IP address or other identifying protocol.
• the deploying component 220 deploys the service.
• the deploying component 220 utilizes the mapping of the resources required and available performed by the resource mapping component 218 to deploy the service that is described in the instance description produced by the resource determining component 216.
• the instantiator 240 and the deploy er 250 utilize the components of the scalable computing platform 200 to deploy a service.
• the cycle defined by the actions of the instantiator 240 and the deployer 250 is repeated with each new instance of the service.
• Each new instance of the service utilizes the various components of the scalable computing platform 200 in a variety of ways to effectively provide the service at the capacity required without allowing a break in the service.
• an initial request for a service is received.
• the initial request for service includes a service contract and a service description.
• a service contract outlines the bounds of the service to be deployed. The bounds include requirements, limitations, and restrictions that will be considered and followed by the service description.
• the received request for service may include the service description as well as the service contract, or the request for service may be received independently of the service description and the service contract. As such, it has been contemplated that any and all combinations of the request for service, the service contract, and the service description are received.
• the request for service is received as indicated at block 310 and the service description is received as indicated at block 315.
• the configuration and resources required to sustain the service are determined as indicated at block 320, as are the resources that are available as indicated at block 325.
• an instance description of the service is produced as indicated at block 330.
• the required resources are mapped to the available resources, as indicated at block 3340.
• the mapping of the resources allows for the service described in the service description to be deployed, as indicated at block 350.
• a result is generated and transmitted, as indicated at block 360.
• the method returns to producing an instance description, as indicated at block 330. If an additional request is not received the method waits for the opportunity to re-generate an instance description. This is indicated at block 382.
• a development phase 410 includes receiving a request for new service or improvements for an existing service. During the developer phase 410, new requirements may also be introduced. The request for new service, request for improvements, and new requirements are incorporated into a developer's service description to define a service.
• the developer's service description is passed to the instantiator assembly phase 420 where the required resources and available resources are determined and the developer's service description is altered to become an instance description.
• the instance description is passed on to the deployment assembly phase 430.
• the service outlined by the instance description is deployed. Monitoring information and data center changes, such as physical device information, is obtained. The monitoring information, data center changes, and deployment status are then transmitted to the instantiation assembly and the development to be incorporated in their respective instance descriptions for a later instance of the service.
• FIG. 5 a graphical representation of an exemplary topology is illustrated and designated generally as reference numeral 500.
• the topology 500 includes elements and their associated configuration values as represented by reference numerals 502, 504, 508, 510, 512, 516, and 518. Additionally, a channel is represented at reference numeral 506 and reference numeral 514.
• the topology 500 shows elements represented at reference numerals 502 and 504 connecting with elements represented at reference numerals 508, 510, and 512. Between the two sets of elements is a channel, as indicated at reference numeral 506.
• the channel distributes the connection to the appropriate input endpoints of elements represented at 508, 510, and 512. Those elements connect from their output endpoint to the channel represented at 514.
• the channel 514 then distributes the connections to elements represented at reference numerals 516 and 518.
• the resulting topology 500 is included in the service description to outline the elements, channels, and configuration values of the service.
• the service deployment evolution 900 begins with a request for a new service that results in the creation of the service, as indicated at reference numeral 910.
• the service is deployed, as indicated at reference numeral 920, as the first instance of the service 930.
• the service lifecycle continues as described with reference to FIGS. 3 and 4.
• the service description is changed with each instance of the service.
• a second request for the service is received and it is deployed, as indicated at reference numeral 940, as the second instance of the service 950.
• the cycle continues for "n" number of instances of the service 960. Following the "n"th instance of the service, the service is deleted from the scalable computing platform, as indicated at reference numeral 970.
• embodiments of the present invention relate to systems, methods and computer storage media for operating a scalable computing platform.
• a service description describing a requested service is received.
• a determination of the required resources and the available resources is made.
• An instance description is produced.
• the resources required to sustain the deployment of the service are mapped to the available resources of the computing platform so the service may be deployed.
• the instance description is amended with each deployment of the service to allow for sustained deployment of the service.

Landscapes

• Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• Software Systems (AREA)
• Theoretical Computer Science (AREA)
• Mathematical Physics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Multi Processors (AREA)
• Stored Programmes (AREA)
• Computer And Data Communications (AREA)
• Data Exchanges In Wide-Area Networks (AREA)
• Information Transfer Between Computers (AREA)

Priority Applications (7)

Applications Claiming Priority (2)

Publications (1)

Family

ID=40900540

Family Applications (1)

Country Status (12)

Cited By (1)

Families Citing this family (19)

Citations (3)

Family Cites Families (19)

• 2008
  • 2008-01-28 US US12/020,890 patent/US8893141B2/en active Active
  • 2008-12-25 TW TW097150663A patent/TWI479415B/zh not_active IP Right Cessation
• 2009
  • 2009-01-07 SG SG2013004908A patent/SG187505A1/en unknown
  • 2009-01-07 KR KR1020107016564A patent/KR101544359B1/ko active Active
  • 2009-01-07 WO PCT/US2009/030269 patent/WO2009097173A1/en not_active Ceased
  • 2009-01-07 AU AU2009209365A patent/AU2009209365B2/en not_active Ceased
  • 2009-01-07 JP JP2010545042A patent/JP5391207B2/ja active Active
  • 2009-01-07 RU RU2010131472/08A patent/RU2502125C2/ru active
  • 2009-01-07 BR BRPI0906412-5A patent/BRPI0906412B1/pt not_active IP Right Cessation
  • 2009-01-07 CN CN200980103816.4A patent/CN101925887B/zh not_active Expired - Fee Related
  • 2009-01-07 EP EP09706572A patent/EP2238542A4/en not_active Ceased
  • 2009-01-07 CA CA2710343A patent/CA2710343C/en active Active

Patent Citations (3)

Non-Patent Citations (2)

Also Published As

Similar Documents

Legal Events