Management of Variants of Model of Service

• US 20100114618A1
• Filed: 10/30/2008
• Published: 05/06/2010
• Est. Priority Date: 10/30/2008
• Status: Abandoned Application

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Rolia, Jerome, Wilcock, Lawrence, Edwards, Nigel, Belrose, Guillaume Alexandre, Kirschnick, Johannes
• Application Number:
  US12/261,355
• Publication Number:
  US 20100114618A1
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/06375 Prediction of business process outcome or impact based on a proposed change
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling

Abstract

A system for developing a computer implemented service, for deployment on computing infrastructure, generates variants of the model by automatically choosing values for a limited set of design variables, and evaluates the variants in operation. A model manager (187) stores in a model repository (107) a current variant (57) and at least some previous variants, and their evaluation results and derivation trails, the generating part being arranged to use the evaluation results and the derivation trails to generate a next current variant. Such use of the repository can help make more efficient the search by the model manager for variants that work well. In particular the derivation trails and evaluations can make it easier to determine when to revert to a preceding variant or determine what new design choices to try next.

Claims

1. A system for developing a computer implemented service, for deployment on computing infrastructure, the system having:

a model manager arranged to develop a model representing at least part of the service, and representing at least part of the computing infrastructure for the service, the model manager having;

a generating part arranged to generate variants of the model by automatically choosing values for a limited set of design variables, and

an evaluating part for evaluating the variants in operation,

the model manager being arranged to store in a model repository a current variant and at least some previous variants, and their evaluation results and derivation trails indicating how the variants are derived from each other,

the generating part being arranged to use the evaluation results and the derivation trails to generate a next current variant by making new choices of values, or by reverting to one of the previous variants.

2. The system of claim 1, the evaluation part being arranged to evaluate more than one of the variants in parallel.

3. The system of claim 1, the model manager being arranged to determine that one or more of the previous variants are unlikely to be useful and to delete them from the repository.

4. The system of claim 1, the evaluation comprising how well the model meets given requirements for the service.

5. The system of claim 1, the generating part being arranged to develop the model through a number of states of development, with variants being associated with a given one of the states and each of the states having a different set of design variables.

6. The system of claim 5, the model manager being arranged to store as part of the derivation trail other possible trails between any variants of any of the development states to enable reversion along the other possible trails.

7. The system of claim 1, the model manager being arranged to generate a variant in the form of a clone model of the service from the model, the clone model having its own clone model repository, and the model manager being arranged to develop the clone model separately from the development of its parent model.

8. The system of claim 7, the model manager being arranged to deploy the model and deploy one or more of the clone models to run their corresponding services in parallel.

9. The system of claim 8, the deployed model and the deployed clone model having monitors, and the model manager being arranged to develop the corresponding services in parallel according to an evaluation of the outputs of the monitors compared to given requirements for the service.

10. The system of claim 7, the clone model having a lifespan independent of that of the parent model.

11. The system of claim 1, the model manager being arranged to record a complete snapshot of at least one of the variants in the model repository, and the model manager being arranged to revert the model to a preceding variant according to the snapshot.

12. The system of claim 1, the model also representing a configuration of software components to implement the service, and allocations of infrastructure resources to run the software components.

13. The system of claim 1, the model also having an indication of allowed adaptation behaviour of the service.

14. The system of claim 1 having a deployment part arranged to deploy the service on shared infrastructure according to the model.

15. A method of providing a computer implemented service deployed on computing infrastructure, the method having the steps of developing a model representing at least part of the service, and representing at least part of the computing infrastructure for the service,

generating variants of the model by automatically choosing values for a limited set of design variables,

evaluating the variants in operation,

storing in a model repository a current variant and at least some previous variants,

and their evaluation results and derivation trails indicating how the variants are derived from previous variants,

using the evaluation results and the derivation trails to generate a next current variant by making new choices of values, or by reverting to one of the previous variants, and

deploying the service on the computing infrastructure according to the model to make it available to users.

16. The method of claim 15, the evaluating involving evaluating more than one of the variants in parallel.

17. The method of claim 15, having the step of developing the model through a number of states of development, with variants being associated with a given one of the states and each of the states having a different set of design variables.

18. The method of claim 15, having the steps of generating a variant in the form of a clone model of the service from the model, the clone model having its own clone model repository, and developing the clone model separately from the development of its parent model.

19. The method of claim 15 having the steps of providing a shared infrastructure for service providers to use for providing the computer implemented service, and enabling the service provider to develop their model of their service, and enabling the service provider to deploy their service on the shared infrastructure according to their model, to make the service available to users.

20. A computer program stored on a machine readable medium and arranged when executed, to carry out the steps of developing a model representing at least part of the service, and representing at least part of the computing infrastructure for the service,

generating variants of the model by automatically choosing values for a limited set of design variables,

evaluating the variants in operation,

storing in a model repository a current variant and at least some previous variants,

and their evaluation results and derivation trails indicating how the variants are derived from previous variants,

using the evaluation results and the derivation trails to generate a next current variant by making new choices of values, or by reverting to one of the previous variants, and

deploying the service on the computing infrastructure according to the model to make it available to users.