Abstract: In a computer-implemented method for automated test execution in a shared virtualized resource pool, a test description containing at least one model for a service under test (SUT) is received and one or more infrastructure configurations to be tested by resources in the shared virtualized resource pool based upon the test description are identified. In addition, a service lifecycle management (SLiM) tool is interacted with to cause the SUT and a load source to be created, the SLiM tool is directed to instantiate the SUT and the load source on the one or more infrastructure configurations in the shared virtualized resource pool for the SUT, and the SLiM tool and the load source are interacted with to receive performance data related to performance of the SUT under one or more loads generated by the load source.

Abstract: Management of heterogeneous data sources is described. In accordance with an embodiment method, a plurality of heterogeneous data sources is identified (410). The plurality of heterogeneous data sources can represent static data sources and management data streams received from servers for network management. The data sources can be encapsulated into data source containers (420). Each data source container can encapsulate a separate data source and can be mapped into an interdependent source graph (430). The interdependent source graph can include object links between the data source containers, the object links representing relationships existing between the data source containers. The interdependent source graph can be queried by traversing the interdependent source graph using data source container relationships to obtain management information about at least one of the data sources (440).

Abstract: Sizing an infrastructure configuration optimized for a workload mix includes: a) instructing a virtualized-aware testing service (VATS) test controller to perform a test of an initial infrastructure configuration in a virtualized environment, in which the test provides at least one test result; b) determining whether the at least one test result satisfies a predetermined requirement as identified in the workload mix; c) modifying at least one parameter of the initial infrastructure configuration to create a modified infrastructure configuration in response to the at least one test result failing to satisfy the predetermined requirement; d) instructing the VATS test controller to perform another test on the modified infrastructure configuration to generate another at least one test result; e) repeating steps b)-d) until a final infrastructure configuration that causes the another at least one test result to satisfy the predetermined requirement is identified; and f) outputting the final infrastructure configur

Abstract: A system for automated lifecycle management of a computer implemented service, according to requirements, having a service model (30) representing the service at a given development state in the lifecycle, and a transition model (70) representing allowed operations to change the service model to a different one of the development states of the service, according to the requirements, and the transition model having a transparent structure suitable for automated inspection of the allowed operations, and suitable for automated adaptation of the allowed operations. The service model can be developed to another of its states of development according to the transition model. This can help facilitate more automation of the service development than for example code in a closed and fixed form such as for example a compiled program for altering the service model. This in turn can enable more complex services to be developed, or reduce development costs.

Abstract: Management of heterogeneous data sources is described. In accordance with an embodiment method, a plurality of heterogeneous data sources is identified (410). The plurality of heterogeneous data sources can represent static data sources and management data streams received from servers for network management. The data sources can be encapsulated into data source containers (420). Each data source container can encapsulate a separate data source and can be mapped into an interdependent source graph (430). The interdependent source graph can include object links between the data source containers, the object links representing relationships existing between the data source containers. The interdependent source graph can be queried by traversing the interdependent source graph using data source container relationships to obtain management information about at least one of the data sources (440).

Abstract: Sizing an infrastructure configuration optimized for a workload mix includes: receiving the workload mix; identifying demand estimates for the one or more predefined benchmarks; applying a predictive model to identify an initial infrastructure configuration having a size anticipated to meet the demand estimates; instructing a virtualized-aware testing service (VATS) test controller to perform a test of the initial infrastructure configuration in a virtualized environment, where performance of the test generates at least one test result; determining whether the at least one test result satisfies a predetermined requirement as identified in the workload mix; and outputting the determination of whether the at least one test result satisfies the predetermined requirement.

Abstract: Sizing an infrastructure configuration optimized for a workload mix includes: a) instructing a virtualized-aware testing service (VATS) test controller to perform a test of an initial infrastructure configuration in a virtualized environment, in which the test provides at least one test result; b) determining whether the at least one test result satisfies a predetermined requirement as identified in the workload mix; c) modifying at least one parameter of the initial infrastructure configuration to create a modified infrastructure configuration in response to the at least one test result failing to satisfy the predetermined requirement; d) instructing the VATS test controller to perform another test on the modified infrastructure configuration to generate another at least one test result; e) repeating steps b)-d) until a final infrastructure configuration that causes the another at least one test result to satisfy the predetermined requirement is identified; and f) outputting the final infrastructure configur

Abstract: In a computer-implemented method for automated test execution in a shared virtualized resource pool, a test description containing at least one model for a service under test (SUT) is received and one or more infrastructure configurations to be tested by resources in the shared virtualized resource pool based upon the test description are identified. In addition, a service lifecycle management (SLiM) tool is interacted with to cause the SUT and a load source to be created, the SLiM tool is directed to instantiate the SUT and the load source on the one or more infrastructure configurations in the shared virtualized resource pool for the SUT, and the SLiM tool and the load source are interacted with to receive performance data related to performance of the SUT under one or more loads generated by the load source.

Abstract: Sizing an infrastructure configuration optimized for a workload mix includes: receiving the workload mix; identifying demand estimates for the one or more predefined benchmarks; applying a predictive model to identify an initial infrastructure configuration having a size anticipated to meet the demand estimates; instructing a virtualized-aware testing service (VATS) test controller to perform a test of the initial infrastructure configuration in a virtualized environment, where performance of the test generates at least one test result; determining whether the at least one test result satisfies a predetermined requirement as identified in the workload mix; and outputting the determination of whether the at least one test result satisfies the predetermined requirement.

Abstract: A system for automated lifecycle management of a computer implemented service, according to requirements, having a service model (30) representing the service at a given development state in the lifecycle, and a transition model (70) representing allowed operations to change the service model to a different one of the development states of the service, according to the requirements, and the transition model having a transparent structure suitable for automated inspection of the allowed operations, and suitable for automated adaptation of the allowed operations. The service model can be developed to another of its states of development according to the transition model. This can help facilitate more automation of the service development than for example code in a closed and fixed form such as for example a compiled program for altering the service model. This in turn can enable more complex services to be developed, or reduce development costs.

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.

Abstract: A system for managing a computer implemented service, according to given requirements has a template (71) of a model of the service, parameterised by requirements and also representing allowed operations (65) to change the model, parameterised by requirements. A rendering tool (61) uses the template to create a service model according to the given requirements. The service can be deployed according to the model. A change manager (62) can make changes to the service model according to the allowed operations of the template. Having the allowed operations in parameterised form in the template can help reduce a risk of introducing changes which are inconsistent with the requirements.