+

WO2002017065A2 - Appareil et procede utilisees dans un ordinateur hebergeant un environnement de services - Google Patents

Appareil et procede utilisees dans un ordinateur hebergeant un environnement de services Download PDF

Info

Publication number
WO2002017065A2
WO2002017065A2 PCT/GB2001/003045 GB0103045W WO0217065A2 WO 2002017065 A2 WO2002017065 A2 WO 2002017065A2 GB 0103045 W GB0103045 W GB 0103045W WO 0217065 A2 WO0217065 A2 WO 0217065A2
Authority
WO
WIPO (PCT)
Prior art keywords
service level
level agreement
electronic service
esla
computer
Prior art date
Application number
PCT/GB2001/003045
Other languages
English (en)
Other versions
WO2002017065A3 (fr
Inventor
Asit Dan
Daniel Dias
Joseph Hellerstein
Original Assignee
International Business Machines Corporation
Ibm United Kingdom Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by International Business Machines Corporation, Ibm United Kingdom Limited filed Critical International Business Machines Corporation
Priority to AU2001269290A priority Critical patent/AU2001269290A1/en
Publication of WO2002017065A2 publication Critical patent/WO2002017065A2/fr
Publication of WO2002017065A3 publication Critical patent/WO2002017065A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • the present invention relates to an apparatus and method for use in a computer hosting services environment. Generally, it relates to the global Internet network and, more particularly, to Internet servers of World Wide Web (WWW or Web) sites supporting one or more organisations hosted at these sites, and specifically providing service level agreements for each of these organisations .
  • WWW World Wide Web
  • the background of the present invention deals with how service applications are hosted at a third party infrastructure according to some Service Level Agreements (SLAs) for ensuring a certain level of end-client satisfaction.
  • SLAs Service Level Agreements
  • the Internet is the world's largest network, and it has become essential in organisations such as government, academia and commercial enterprises. Transactions over the Internet are becoming more common, especially in the commercial arena. Businesses increasingly run their applications using infrastructure (e.g., server, network connectivity) provided by a third party, referred to as the "service provider . "
  • Web hosting will be used as the running example herein, those skilled in the art will readily appreciate that the invention applies to many other computer hosting services.
  • clients to Web hosting services are dissatisfied with the hosting service provided, because it does not meet their performance, availability, or functional expectations.
  • a service contract or SLA provides a means by which the expectations of the service provider can be negotiated with the customer. Service contracts have existed for a decade or more. However, they have been paper agreements.
  • IT information technology
  • the SLA may include expected bandwidth throughput at the network and/or servers, disk space utilisation, availability, i.e., up-time of network and server resources, as well recovery time upon failure, and pricing for various levels of service .
  • the SLA cannot be read by computers for the purpose of monitoring to detect violation of agreements, and/or used by a resource manager for automatic configuration/allocation of resources.
  • the present invention provides computer-based methods and systems for building, provisioning and executing one or more electronic service level agreements (eSLAs) for Web and other computer hosting services, which specify and enforce service contracts for Web and other computer hosting services. Further, the present invention provides a process whereby an eSLA can be used for negotiation, service level monitoring, and enforcement.
  • eSLAs electronic service level agreements
  • a computer-based system for use in a computer hosing services environment as defined in claim 15.
  • an article of manufacture for use in a computer hosting services environment, comprising a machine readable medium containing one or more programs which when executed implement the steps of: constructing an electronic service level agreement between a service provider and a client based on client input for an application associated with the client to be hosted by the service provider; and checking the consistency of the electronic service level agreement with respect to one or more existing electronic service level agreements previously committed to by the service provider .
  • the method for use in a computer hosing services environment may comprise the step of modifying the electronic service level agreement when at least one inconsistency is found.
  • the method may further comprise the step of provisioning one or more resources of an infrastructure on which the application is to be hosted in accordance with the constructed electronic service level agreement.
  • the method may further comprise the step of executing the constructed electronic service level agreement.
  • the method may further comprise the step of reporting one or more events associated with the execution of the constructed electronic service level agreement.
  • the one or more events may comprise at least one of a violation of a portion of the electronic service level agreement and a near-violation of a portion of the electronic service level agreement.
  • the method may comprise the step of providing a warning that a portion of the electronic service level agreement is one of violated and near-violated.
  • the method may comprise the step of providing an alarm that a portion of the electronic service level agreement is one of violated and near-violated.
  • the method may further comprise the step of providing explanation as to why a portion of the electronic service level agreement is one of violated and near-violated.
  • the method may comprise the step of determining whether the electronic service level agreement will be satisfied for a given workload based on historical data.
  • the method may further comprise the step of determining for how long the electronic service level agreement will be satisfied based on a workload forecasting and performance prediction technique.
  • the constructing step may comprise determining pricing for inclusion in the electronic service level agreement associated with the hosting of the application by the service provider.
  • a computer-based eSLA system includes four main components: (1) an eSLA builder; (2) an eSLA provisioner; (3) one or more execution systems; and (4) a system configuration and measurement system.
  • the eSLA builder component provides the mechanism for defining and pricing the eSLA, checking the validity of the eSLA and a repository for storing the completed eSLAs .
  • the provisioning system is responsible for configuring ⁇ ⁇ tSJ _ ⁇ o L ⁇ o 01 o in
  • the eSLA may also specify a set of conditions/rules that indicate a violation of the service agreement. Alternatively, this could be expressed as a negation of a set of conditions which completely specify when the agreement is met/satisfied. For example, for a Web site, the following conditions could be stated: high_response : (weighted_response_time > r_max) & (weighted_throughput ⁇ t_max) ; non_available: (continuous_down_time > con _down_max)
  • More conditions, or conditions of finer granularity can be defined.
  • the minimum number of conditions that would indicate violation of the contract, at a level that can be measured, is defined.
  • the eSLA may also specify penalties associated with violation of the contract terms. Associated with each violation condition, a penalty clause is preferably defined. The penalty may be a function of the deviation from the agreed limits. The violation may occur either due to the actual workload exceeding specification or due to the failure in satisfying service metrics.
  • an overall computer-based eSLA methodology comprises the following steps:
  • the eSLA for example, with the above elements, is defined (preferably in a high level language using an authoring tool) .
  • the eSLA After the eSLA is defined, it is then executed. This can be done by generation of code that executes the eSLA, or interprets the eSLA. Inputs to the eSLA executing step are measurements related to the defined metrics. (3) Either on-line or off-line, violations of the eSLA are determined and output .
  • alarms are generated if the eSLA is not violated but gets to within some threshold of violation. Warning of the amount of penalty that would be accrued if the violation were to occur may be indicated as a severity measure .
  • warnings are generated if the eSLA is not violated, or close to being violated, but a constraint, such as maximum allowable throughput according to the eSLA, is close to being violated.
  • the eSLA may be renegotiated, and a new eSLA defined, going back to step (2) .
  • it may also be determined what eSLAs will be satisfied for a given workload based on historical data.
  • step (8) is used in conjunction with a workload forecasting and performance prediction tool to determine how long the eSLA will be satisfied.
  • an explanation is output as to why an eSLA violation occurred so that more complex eSLAs can be accommodated.
  • service providers have automation whereby SLAs can be negotiated, provisioned, and enforced with feedback when violations occur. This capability enables new service offerings with service level guarantees .
  • the present invention provides a feedback mechanism whereby system administrators learn early on of failures to meet service level agreements thereby enabling new negotiations.
  • failures result from many practical causes, including, for example: imperfections in the models of system performance, inaccuracies in workload forecasts, and scheduling changes in equipment acquisition.
  • FIG. 1 is a block diagram illustrating an eSLA system according to an embodiment of the present invention and an overall environment in which such system may operate;
  • FIG. 2 is a block diagram illustrating components of an eSLA builder module according to an embodiment of the present invention
  • FIG. 3 is a block diagram illustrating components of an eSLA provisioner module according to an embodiment of the present invention
  • FIG. 4 is a block diagram illustrating components of an execution system according to an embodiment of the present invention.
  • FIG. 5 is a flow diagram illustrating an overall eSLA methodology according to an embodiment of the present invention.
  • FIG. 6 is a flow diagram illustrating an eSLA building process according to an embodiment of the present invention.
  • FIG. 7 is a flow diagram illustrating an eSLA provisioning process according to an embodiment of the present invention.
  • FIG. 8 is a flow diagram illustrating an eSLA execution process according to an embodiment of the present invention.
  • FIG. 9 is a flow diagram illustrating an eSLA violation reporting process according to an embodiment of the present invention.
  • FIG. 10 is a block diagram illustrating a generalised hardware architecture of a computer system suitable for implementing an eSLA system according to the present invention.
  • the parties to each eSLA are a Web application owner and a service provider (e.g., the party providing the infrastructure such as the server, network interconnectivity, etc.) .
  • a service provider e.g., the party providing the infrastructure such as the server, network interconnectivity, etc.
  • the present invention is not limited to such a particular environment. Rather, the invention is more generally applicable to any computer hosting services environment in which it is desirable to build, execute, monitor and act on electronic service level agreements in order to, among other things, obtain significant reductions in the cost of ownership and hosting associated with such environments.
  • FIG. 1 a block diagram illustrates an eSLA system and an overall environment in which such system may operate .
  • administrators of hosted applications via their respective computer systems 250-1 through 250-M and end-users via their respective computer systems 500-1 through 500-N communicate with the eSLA-based system 1000 of the present invention.
  • the eSLA-based system is comprised of an execution system 2000 (more than one execution system may be employed depending on the number and nature of the eSLAs) , an eSLA builder module 3000, an eSLA provisioner module 6000 and system configuration and measurements repositories 7000.
  • the eSLA builder, eSLA provisioner and the execution system are operatively coupled to the system configuration and measurements repositories.
  • the eSLA builder, eSLA provisioner and execution system may also be operatively coupled to each other.
  • an administrator represents an owner of the application which is to be hosted on the third party infrastructure provided by the service provider.
  • the application Once the application is hosted on the service provider ' s infrastructure in accordance with the terms and conditions of the eSLA agreed upon between the service provider and application owner, end-users may access the application via the Internet.
  • the level of service received by the end-users when accessing the hosted application on the service provider's infrastructure is controlled and monitored by the execution system (s) provisioned in accordance with the one or more previously-built eSLAs .
  • administrators and end-users interact with the eSLA-based system in the following manner.
  • Administrators of hosted applications communicate with the eSLA builder module 3000 to specify eSLAs for hosted applications and to receive reports of service level violations of the eSLAs .
  • the eSLA provisioner 6000 translates the eSLAs into operational parameters, some of which are stored in the system configuration repositories 7000 and others of which are directly changed in the execution system 2000. That is, the provisioning system is responsible for configuring the run-time system in order to meet one or a set of eSLAs.
  • End-users (500-1 through 500-N) interact with the execution system that operates in a manner specified by the eSLAs .
  • the execution system is responsible for handling the run-time user requests, e.g., Web servers and load distributors, and a mechanism for enforcing the eSLAs at run-time.
  • the repositories 7000 include one or more repositories for storing information on the current system configuration and run-time information on the metrics that are part of the eSLA.
  • each end-user and each administrator accesses the eSLA system via his/her own computer system.
  • the components of the eSLA system may be implemented on one or more computer systems .
  • the individual computer systems are preferably connected by one or more suitable networks such as, for example, the Internet.
  • suitable networks such as, for example, the Internet.
  • the present invention is not so limited. That is, it is possible that all participants and components shown in FIG. 1 access and/or reside on a single computer system.
  • the eSLA system and its operating environment may be realised on any number of computer systems and, in a distributed environment like the Internet, will be realised on several computer systems coupled via a common communication network. An exemplary embodiment of one such computer system is described below in the context of FIG. 10.
  • FIG. 2 a block diagram illustrates components of an eSLA builder module.
  • the eSLA builder 3000 is comprised of an eSLA authoring tool 3005, an eSLA repository 3010, a current eSLA repository 3015, a validity checker module 3020, a pricer module 3025, a modeler module 3030 and a reporting module 3035.
  • the eSLA authoring tool 3005 interacts with administrators to construct a current eSLA which is stored in repository 3015.
  • the eSLA authoring tool also retrieves and updates other eSLAs in the eSLA repository 3010, some of which may be for different hosted applications.
  • XML extensible Markup Language
  • any suitable XML editor may serve as the authoring (and editing) tool.
  • the validity checker 3020 provides this capability in cooperation with the modeler 3030 by determining if sufficient capacity is present .
  • service pricing may be done as well. This is accomplished in accordance with the pricer module 3025.
  • Automated pricing may, for example,
  • FIG. 5 a flow diagram illustrates an overall eSLA methodology. Administrators (250-1 through 250-M) build the eSLA in step 400 (via the eSLA builder 3000) , which is then provisioned in step 410 (via the eSLA provisioner 6000) to one or more execution systems 2000 that then execute under the control specified by the eSLA in step 420. The effect of these eSLAs is then reported back to the builder 3000, which may cause the eSLA to be renegotiated if terms and/or conditions of the eSLAs cannot be met .
  • FIG. 6 a flow diagram illustrates an eSLA building process. Specifically, FIG. 6 illustrates details of step 400 of FIG. 5. Accordingly, as shown in FIG. 6, an eSLA is specified through interactions with an administrator in step 100.
  • the eSLA authoring sub-component of the eSLA system provides a mechanism for defining the elements for the eSLA in accordance with an administrator. Through this automated mechanism, the eSLA is built. A preferred example of what an eSLA may specify is now given.
  • An eSLA identifies the principal workload types. For example, for a storefront Web site, these could include: (i) Web browsing of the site; (ii) adding a browsed item to a shopping cart; and (iii) buying the set of items in the shopping cart.
  • the eSLA may have the minimum number of workload types that may provide adequate granularity for characterising the load on the servers at a level needed by the eSLA.
  • the eSLA may then specify metrics used to characterise the service level agreed to.
  • the metrics could include: (a) the response time for requests of the workload types specified above, which could include further specifications of the average response time, 95th percentile of response time, or other metric of response time; (b) the maximum throughput for each workload type for which the response times are guaranteed, and preferably specification of whether the system will limit the throughput if it exceeds the stated maximum; (c) the maximum number of concurrent requests of each type in the system; (d) the system availability, either overall, or for each type of request.
  • the number and the granularity of the metrics depends both on what metrics can be gathered, and on the smallest number of metrics that adequately characterise the performance or availability of the system.
  • the eSLA may also specify methodology for monitoring workload and service metrics (e.g., response time, availability) . This may include both specification of data sensors and their placements in the execution path, as well as processing of data to generate desired metrics (e.g., weighted throughput, window for estimation of average, etc.).
  • workload and service metrics e.g., response time, availability
  • desired metrics e.g., weighted throughput, window for estimation of average, etc.
  • the eSLA may also specify a set of conditions/rules that indicate a violation of the service agreement. Alternatively, this could be expressed as a negation of a set of conditions which completely specify when the agreement is met/satisfied. For example, for a Web site, the following conditions could be stated: high_response: (weighted_response_time > r_max) & (weighted_throughput ⁇ t_max) ; non_available: (continuous_down_time > cont_down_max)
  • More conditions, or conditions of finer granularity can be defined.
  • the minimum number of conditions that would indicate violation of the contract, at a level that can be measured, are defined.
  • the eSLA may also specify penalties associated with violation of the contract terms. Associated with each violation condition, a penalty clause is defined. The penalty may be a function of the deviation from the agreed limits. The violation may occur either due to the actual workload exceeding specification or due to the failure in satisfying service metrics .
  • an eSLA specified in accordance with the invention may include any particular number and/or variety of clauses, conditions, remedies for violations, etc., constructed in accordance with the specific application for which it is being built.
  • step 120 the eSLA is checked for consistency, especially with regard to capacity constraints given the other eSLAs that are committed to by the service provider. If some part of the eSLA is not consistent, the process returns to step 100. The noted inconsistencies may then rectified by the parties. Otherwise, in step 130, a price is determined for the services to be offered, as described previously for FIG. 2. If the price is not in agreement with the administrator's expectations, the process returns to step 100. Otherwise, the eSLA provisioner (6000 in FIG. 1) is notified of the new eSLA in step 140. It is to be appreciated that the eSLA building operation preferably receive reporting input from the execution system (shown as step 420 in FIG. 6) .
  • FIG. 7 is a flow diagram illustrating an eSLA provisioning process. Specifically, FIG. 7 illustrates details of step 410 of FIG. 5. Accordingly, as shown in FIG. 7, an eSLA is either created for the first time or updated in step 300. In step 310, the affected resources are located. In step 320, resource control information is changed in the configuration repository (7000 in FIG. 1) and/or in the execution systems (2000 in FIG. 1) themselves.
  • FIG. 8 a flow diagram illustrates an eSLA execution process. Specifically, FIG. 8 illustrates details of how the execution system performs step 420 of FIG. 5. Accordingly, as shown in FIG. 8, the execution system receives an end-user request in step 600. In step 610, the execution system allocates resources in the manner specified by the control parameters that have been set by the eSLA provisioner (6000 in FIG. 1) . In step 620, SLA violations are reported.
  • FIG. 9 is a flow diagram illustrating an eSLA violation reporting process. Specifically, FIG. 9 illustrates details of step 620 of FIG. 8. Accordingly, as shown in FIG. 9, the execution system generates an event in response to an occurrence associated with the hosted application. This event is stored in repository 7000 and is subscribed to by the eSLA builder 3000.
  • the reporting component (3035 of FIG. 2) constructs a report based on the event using the context provided by the eSLA for which the violation or near-violation, as explained below, occurred.
  • the appropriate administrator is notified.
  • the administrator decides whether to renegotiate the eSLA based on such feedback. If so, the eSLA building process is reentered.
  • the system may compute and report penalties associated with violations.
  • alarms are generated and reported if the eSLA is not violated but gets to within some threshold of violation. Warning of the amount of penalty that would be accrued if the violation were to occur may be indicated as a severity measure.
  • warnings are generated and reported if the eSLA is not violated, or close to being violated, but a constraint, such as maximum allowable throughput according to the eSLA, is close to being violated.
  • the eSLA may be renegotiated, and a new eSLA defined.
  • it may also be determined what eSLAs will be satisfied for a given workload based on historical data. Further, such a determination is used in conjunction with a workload forecasting and performance prediction tool to determine how long the eSLA will be satisfied.
  • violations of service delivery by the subcontractor are preferably linked to the ability of the main service provider to satisfy their eSLA.
  • an explanation is preferably output as to why an eSLA violation occurred so that more complex eSLAs can be accommodated.
  • FIG. 10 a block diagram is shown illustrating a generalised hardware architecture of a computer system suitable for implementing one or more of the functional components/modules of an eSLA-based system as depicted in the figures and explained in detail herein.
  • the computer system may be implemented in accordance with a processor 10000, a memory 10010 and I/O devices 10020.
  • processor as used herein is intended to include any processing device, such as, for example, one that includes a CPU (central processing unit) and/or other processing circuitry.
  • memory as used herein is intended to include memory associated with a processor or CPU, such as, for example, RAM, ROM, a fixed memory device (e.g., hard drive), a removable memory device (e.g., diskette), flash memory, etc.
  • I/O devices or “I/O devices” as used herein is intended to include, for example, one or more input devices, e.g., keyboard, for entering data to the processing unit, and/or one or more output devices, e.g., CRT display and/or printer, for presenting results associated with the processing unit.
  • processor may refer to more than one processing device and that various elements associated with a processing device may be shared by other processing devices.
  • software components including instructions or code for performing the methodologies described herein may be stored in one or more of the associated memory devices (e.g., ROM, fixed or removable memory)- and, when ready to be utilised, loaded in part or in whole (e.g., into RAM) and executed by a CPU.
  • the associated memory devices e.g., ROM, fixed or removable memory
  • the present invention is typically implemented as a computer program product, comprising a set of program instructions for controlling a computer or similar device. These instructions can be supplied preloaded into a system or recorded on a storage medium such as a CD-ROM, or made available for downloading over a network such as the Internet or a mobile telephone network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Economics (AREA)
  • General Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Development Economics (AREA)
  • Marketing (AREA)
  • Tourism & Hospitality (AREA)
  • Game Theory and Decision Science (AREA)
  • General Business, Economics & Management (AREA)
  • Educational Administration (AREA)
  • Operations Research (AREA)
  • Databases & Information Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Debugging And Monitoring (AREA)

Abstract

L'invention concerne des systèmes et des procédés informatiques permettant de créer, de fournir et d'exécuter au moins un contrat de service électronique (eSLA) pour le Web et d'autres services hébergeant un ordinateur, qui spécifient et exécutent des contrats de service pour le Web et les services précités. Selon un aspect de l'invention, un système informatique eSLA (1000) comprend quatre composants principaux: 1) un créateur de eSLA (3000); 2) un fournisseur de eSLA (6000); 3) au moins un système d'exécution (2000); et 4) un système (7000) de mesure et de configuration de système. En général, le composant de création de eSLA (3000) comprend un mécanisme permettant de définir, d'évaluer, et de vérifier la validité du eSLA, et un référentiel permettant de stocker les eSLAs exécutés. Le système de fourniture (6000) sert à configurer le système pendant l'exécution afin de le conformer à moins un ensemble de eSLA. Le système d'exécution (2000) sert à manipuler les demandes utilisateur pendant l'exécution, par exemple, des serveurs Web et des distributeurs de charge, et comprend un mécanisme permettant d'exécuter les eSLA pendant l'exécution. Le système de configuration de système et de mesure (7000) conserve des informations sur la configuration du système courant, et des informations de durée d'exécution sur les métriques faisant partie des eSLA.
PCT/GB2001/003045 2000-08-18 2001-07-06 Appareil et procede utilisees dans un ordinateur hebergeant un environnement de services WO2002017065A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001269290A AU2001269290A1 (en) 2000-08-18 2001-07-06 Apparatus and method for use in a computer hosting services environment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US64252600A 2000-08-18 2000-08-18
US09/642,526 2000-08-18

Publications (2)

Publication Number Publication Date
WO2002017065A2 true WO2002017065A2 (fr) 2002-02-28
WO2002017065A3 WO2002017065A3 (fr) 2002-09-06

Family

ID=24576949

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB2001/003045 WO2002017065A2 (fr) 2000-08-18 2001-07-06 Appareil et procede utilisees dans un ordinateur hebergeant un environnement de services

Country Status (3)

Country Link
US (1) US20060206619A1 (fr)
AU (1) AU2001269290A1 (fr)
WO (1) WO2002017065A2 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050131978A1 (en) * 2003-12-10 2005-06-16 Microsoft Corporation Systems and methods that employ process algebra to specify contracts and utilize performance prediction implementations thereof to measure the specifications
US7228255B2 (en) 2004-12-22 2007-06-05 International Business Machines Corporation Adjudication means in method and system for managing service levels provided by service providers
US7555408B2 (en) 2004-12-22 2009-06-30 International Business Machines Corporation Qualifying means in method and system for managing service levels provided by service providers
US20110106712A1 (en) * 2009-11-02 2011-05-05 Microsoft Corporation Cost-Aware Service Aggregation
US8438117B2 (en) 2004-12-22 2013-05-07 International Business Machines Corporation Method and system for managing service levels provided by service providers

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7660731B2 (en) * 2002-04-06 2010-02-09 International Business Machines Corporation Method and apparatus for technology resource management
US7509373B2 (en) 2003-11-24 2009-03-24 At&T Intellectual Property I, L.P. Methods for providing communications services
US7464179B2 (en) * 2003-11-24 2008-12-09 At&T Intellectual Property I, L.P. Methods, systems, and products for providing communications services amongst multiple providers
WO2005050496A1 (fr) * 2003-11-24 2005-06-02 River Dynamics Pty Ltd Surveillance d'attentes de service
US7467219B2 (en) 2003-11-24 2008-12-16 At&T Intellectual Property I, L.P. Methods for providing communications services
US7519657B2 (en) * 2003-11-24 2009-04-14 At&T Intellectual Property L, L.P. Methods for providing communications services
US7343416B2 (en) * 2003-11-24 2008-03-11 At&T Delaware Intellectual Property, Inc. Methods, systems, and products for providing communications services amongst multiple providers
KR100555729B1 (ko) * 2005-08-16 2006-03-03 김성규 보조차양을 갖는 차양모
US20080184283A1 (en) * 2007-01-29 2008-07-31 Microsoft Corporation Remote Console for Central Administration of Usage Credit
US20080183712A1 (en) * 2007-01-29 2008-07-31 Westerinen William J Capacity on Demand Computer Resources
US8046694B1 (en) 2007-08-06 2011-10-25 Gogrid, LLC Multi-server control panel
US8954592B1 (en) * 2007-11-05 2015-02-10 Amazon Technologies, Inc. Determining computing-related resources to use based on client-specified constraints
US7856499B2 (en) * 2008-03-20 2010-12-21 Sap Ag Autonomic provisioning of hosted applications with level of isolation terms
US8769113B2 (en) * 2009-05-19 2014-07-01 Telefonaktiebolaget L M Ericsson (Publ) Establishing a communication session
US9256900B2 (en) * 2010-11-15 2016-02-09 International Business Machines Corporation Managing service demand load relative to infrastructure capacity in a networked computing environment
CN103886398B (zh) * 2012-12-20 2018-01-12 中国电信股份有限公司 一种跨系统异构环境下的业务监控方法和系统
US9558005B2 (en) * 2014-05-19 2017-01-31 Intel Corporation Reliable and deterministic live migration of virtual machines
US10264059B2 (en) 2015-08-28 2019-04-16 International Business Machines Corporation Determining server level availability and resource allocations based on workload level availability requirements
US9769730B1 (en) * 2016-03-21 2017-09-19 Verizon Patent And Licensing Inc. Service level agreement violation warning and service suspension
US20240385884A1 (en) * 2021-12-23 2024-11-21 Intel Corporation Methods, systems, articles of manufacture and apparatus to estimate workload complexity

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
IL125726A (en) * 1996-02-12 2002-12-01 British Telecomm Service provision system for use in distributed processing environments
US5893905A (en) * 1996-12-24 1999-04-13 Mci Communications Corporation Automated SLA performance analysis monitor with impact alerts on downstream jobs
US5732218A (en) * 1997-01-02 1998-03-24 Lucent Technologies Inc. Management-data-gathering system for gathering on clients and servers data regarding interactions between the servers, the clients, and users of the clients during real use of a network of clients and servers
EP0883075A3 (fr) * 1997-06-05 1999-01-27 Nortel Networks Corporation Procédé et dispositif de prédiction des valeurs futurs d'une série chronologique
CA2212251A1 (fr) * 1997-07-31 1999-01-31 Crosskeys Systems Corporation Integration de plate-formes de gestion de tiers au moyen de passerelles resolve (md)
WO1999025085A1 (fr) * 1997-11-07 1999-05-20 Visual Networks Technologies, Inc. Procede et appareil permettant d'effectuer des analyses de niveau de service de parametres de la tenue du reseau de communication aux donnees

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050131978A1 (en) * 2003-12-10 2005-06-16 Microsoft Corporation Systems and methods that employ process algebra to specify contracts and utilize performance prediction implementations thereof to measure the specifications
EP1545066A2 (fr) 2003-12-10 2005-06-22 Microsoft Corporation Systèmes et procédés basés sur un algèbre de processus et des applications de prédiction de performance pour spécifier des contrats et mesurer les spécifica- tions
EP1545066A3 (fr) * 2003-12-10 2009-12-16 Microsoft Corporation Sytèmes et procédés basés sur une algèbre de processus et des applications de prédiction de performance pour spécifier des contrats et mesurer les spécifications
US7228255B2 (en) 2004-12-22 2007-06-05 International Business Machines Corporation Adjudication means in method and system for managing service levels provided by service providers
US7555408B2 (en) 2004-12-22 2009-06-30 International Business Machines Corporation Qualifying means in method and system for managing service levels provided by service providers
US8438117B2 (en) 2004-12-22 2013-05-07 International Business Machines Corporation Method and system for managing service levels provided by service providers
US20110106712A1 (en) * 2009-11-02 2011-05-05 Microsoft Corporation Cost-Aware Service Aggregation

Also Published As

Publication number Publication date
US20060206619A1 (en) 2006-09-14
AU2001269290A1 (en) 2002-03-04
WO2002017065A3 (fr) 2002-09-06

Similar Documents

Publication Publication Date Title
US20060206619A1 (en) Electronic service level agreement for Web site and computer services hosting
US7583607B2 (en) Method and apparatus for designating and implementing support level agreements
Keller et al. Defining and Monitoring Service-Level Agreements for Dynamic e-Business.
US7801976B2 (en) Service-oriented architecture systems and methods
US8069242B2 (en) System, method, and software for integrating cloud computing systems
Pawar et al. Trust model for optimized cloud services
US7062472B2 (en) Electronic contracts with primary and sponsored roles
Keller et al. Managing dynamic services: A contract based approach to a conceptual architecture
US8285827B1 (en) Method and apparatus for resource management with a model-based architecture
US20050060662A1 (en) Process for creating service action data structures
US20060025985A1 (en) Model-Based system management
US20040186905A1 (en) System and method for provisioning resources
US20050043979A1 (en) Process for executing approval workflows and fulfillment workflows
US9774541B1 (en) System, method, and computer program for generating an orchestration data tree utilizing a network function virtualization orchestrator (NFV-O) data model
US20100122119A1 (en) Method to manage performance monitoring and problem determination in context of service
US20040024767A1 (en) Method and system for managing event information in a computer network
US20050044099A1 (en) Process for creating an information services catalog
Wang et al. Quality of service (QoS) contract specification, establishment, and monitoring for service level management
JP2000506641A (ja) 分散処理環境において使用するためのサービス提供システム
US20060112317A1 (en) Method and system for managing information technology systems
Westerinen et al. The continuing evolution of distributed systems management
Xiong et al. Trust-based resource allocation in web services
Mohamed et al. rSLA: an approach for managing service level agreements in cloud environments
Venticinque Agent Based Services for Negotiation
US20060143024A1 (en) Methods and systems that calculate a projected utility of information technology recovery plans based on contractual agreements

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载