ETICS 2 SA1 EXECUTION PLAN FOR THE FIRST TWELVE

THERMODYNAMICS AND KINETICS OF THE NANOCHECKERBOARD FORMATION YONG
12 LEARNING FROM ‘FAVELAS’ THE POETICS OF USERS’ AUTONOMOUS
18 GENETICS REVIEW EXAMINATION FOR NURSES IN ADULT DISCIPLINES

19 THE POETICS OF FICTION POETIC INFLUENCE ON
2003 CALIFORNIA COMMUNITY COLLEGES COMMISSION ON ATHLETICS SOUTHERN REGIONAL
20212022 CLARENCE FULTON ATHLETICS PLAYER INFORMATION PLAYER NAME

EGEE Quality Pan

ETICS 2 SA1 EXECUTION PLAN FOR THE FIRST TWELVE


ETICS 2 SA1 EXECUTION PLAN FOR THE FIRST TWELVE



ETICS 2





SA1 Execution Plan
for the first twelve months



EU DELIVERABLE: SA1 Work Package

Document identifier:

DSA1.1

116693.doc


Date:

10 October 2021


Work Package:

SA1: Service Management


Lead Partner:

CERN


Document status:

Draft





Document link:






Abstract:



The SA1 Execution Plan for the ETICS 2 project describes the improvements of the current system and the new features that will be implemented for the ETICS Services. A list of milestones will present the timeline, over the first twelve months of ETICS 2, of such improvements and new functionalities, as well as the work involving and depending on other ETICS 2 Activities.































































Copyright (c) Members of the ETICS 2 Collaboration. 2008.

See http://www.eu-etics.org/etics/partners/ for details on the copyright holders.

ETICS (“E-Infrastructure for Testing, Integration and Configuration of Software”) is a project funded by the European Union. For more information on the project, its partners and contributors please see http://www.eu-etics.org .

You are permitted to copy and distribute verbatim copies of this document containing this copyright notice, but modifying this document is not allowed. You are permitted to copy this document in whole or in part into other documents if you attach the following reference to the copied elements: "Copyright (C) 2008. Members of the ETICS 2 Collaboration. http://www.eu-etics.org ".

The information contained in this document represents the views of ETICS as of the date they are published. ETICS does not guarantee that any information contained herein is error-free, or up to date.

ETICS MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, BY PUBLISHING THIS DOCUMENT.

Delivery Slip


Name

WP/partner

Date

Signature

From

Alberto Aimar

SA1/CERN

20.5.2008


Reviewed by





Approved by





Document Log

Issue

Date

Comment

Author

0.1

18.5.2008

Initial Draft

A.Aimar

0.2

26.5.2008

Reviewed Draft

F.Hemmer

0.3




















Document Change Record

Issue

Item

Reason for Change














TABLE oF Content

1. Introduction 7

1.1. Purpose of the document 7

1.2. Application area 7

1.3. references 7

1.4. Document amendment procedure 7

1.5. Terminology and Glossary 7

2. Executive Summary 8

3. SA1 Goals Overview 9

3.1. SA1 Mandate and Responsibility and Mandate 9

3.2. SA1 Objectives 9

3.3. SA1 Deliverables of the First twelve Months Reporting Period 9

3.4. ETICS 2 Partners and SA1 Resources 10

3.4.1. ETICS 2 Partners 10

3.4.2. SA1 Resources and Roles 10

4. Present and Future of the ETICS Services 11

4.1. Etics Services Current Activities 11

4.2. ServicesS at CERN, INFN, Wisconsin 11

4.3. New Requirements and New Communities 11

4.4. New Build Infrastructures 12

5. SA1 PlanS for the first twelve MonthsReporting Period 12

5.1. Overview of the Objectives 12

5.2. Milestones and Tasks 13

5.2.1. Deployment Plan of the ETICS Services 13

5.2.2. New Features for the User Projects 14

5.2.3. Integration with Other ETICS Activities 15

5.3. Project Risks 15

6. Gannt Chart View 16





1.Introduction

1.1.Purpose of the document

This document presents the execution plan for the first twelve months of the SA1 Service Management work package of the ETICS 2 project.

SA1 is the activity responsible of providing a stable and professional support of the ETICS Services. This document initially describes the ongoing duties and the context of the current ETICS Services, which are already widely used by few important grid-related projects. The focus of the rest of the document is on future improvements and new features that will be added to the Services during the first year of the ETICS 2 project.

1.2.Application area

This document and the milestones mentioned apply to the SA1 project members and partners. Some features that depend on other work packages will only be described for the parts concerning their SA1 application area.

1.3.references



[1]

ETICS 2 – Description on Work -Technical Annex

[2]

ETICS – D3.1: Configuration, Build and Integration Specifications

[3]

ETICS – WP1 Document: Architecture and Design Specifications

[4]

ETICS – D2.4: Status of certification, integration and validation test bed setup

[5]

ETICS – D5.7: Quality Certification Feasibility Study and Sustainability Strategy

1.4.Document amendment procedure

This document can be amended by the Service Management team (SA1) further to any feedback from the other teams. Minor changes, such as spelling corrections, content formatting or minor text reorganisation not affecting the content and meaning of the document can be applied by SA1 without previous review. Other changes must be peer reviewed and submitted to the PMB for approval.

When the document is modified for any reason, its version number shall be incremented accordingly. The document version number shall follow the standard ETICS 2 conventions for document versioning. The document shall be maintained using the document management tools provided by the EDMS system at CERN.

1.5.Terminology and Glossary

ETICS Services

Software Services, by ETICS, providing build, test, report and archive functionality by ETICS to the User Projects. Currently the ETICS Services web and repository services are available at http://etics.cern.ch.

User Project

Project hosted and supported by the ETICS Services (e.g. gLite) and that uses the build and test facilities of the Services.

Build and Test Infrastructure

Underlying infrastructures providing computing resources and job management to the ETICS Services (e.g. Condor, EGEE, etc).

Worker Node

Computing element where the ETICS build and test jobs are executed. During the first phase of the project the worker nodes are managed by the Condor submission engine. In ETICS phase 2 job submissions will be extended also to the EGEE/gLite and DEISA/UNICORE infrastructures.

Disseminator

ETICS component that provides customizable reporting and visualization of data stored in the ETICS repository. For instance the Metrics Disseminator will be an ETICS component that reports and provides trend analysis on metrics collected by the ETICS test and static analysis plugins.

Plug-in Framework

Open interface allowing the extension of the ETICS client to additional tools (i.e. ETICS plug-ins) that are then executed during the ETICS build and test process.

Distributed Multi-Node Test

Test that requires several applications (or services) to be deployed and running on several worker nodes. This implies communication and synchronization among the nodes and the services under test.

2.Executive Summary

The mandate of the SA1 work package in ETICS 2 is to support and improve a secure and reliable infrastructure for the ETICS Services in order to provide build, test and release management to the software projects hosted. To fulfil its objectives SA1 must also plan how to move to a scalable and extensible architecture and define how to integrate the work of other activities regarding the support of external testing tools and build infrastructures such as Condor, gLite and UNICORE.

One of the goals of the ETICS 2 project is to go beyond the support of EGEE-related User Projects. Therefore the Services will have to be adapted to the needs of other user communities, for instance in terms or security and privacy of the User Projects applications and reports.

Specialised test and workflow management tools will be integrated in order to reduce the cost of producing efficient test suites. SA1 will extend the Services with a catalogue of preconfigured services and components as well as automated test bed deployment tools enabling ETICS users to design complex tests and easily prepare specific test cases.

The ETICS Services should also benefit of well-established technologies of hardware virtualization software, which are currently provided by several commercial companies and by open source communities.

The main SA1 milestones for the first twelve months of the ETICS 2 projects are summarized below:

3.SA1 Goals Overview

3.1.SA1 Mandate and Responsibility and Mandate

The SA1 (Service Management) mandate and responsibility and mandate can be summarized by the following main three duties:

3.2.SA1 Objectives

In addition to the mandate, the objectives defined for SA1 in the ETICS 2 proposal for the two years of the project are the following:

3.3.SA1 Deliverables of the First twelve Months Reporting Period

M03 - DSA1.1 – Execution plan for first twelve months of infrastructure operation

This deliverable describes the execution plan for the first half of the ETICS 2 project, including the service timeline and the infrastructure deployment and improvement plan.

M06 - DSA1.2 – ETICS Services Design Specification

This deliverable describes the overall architecture of the ETICS 2 services.

M09 - DSA1.3 – ETICS Site Service Level Agreement

This deliverable describes the Service Level Agreements upon whichgoverning the ETICS service will be provided. The SLAs will define the service level the users can expect from the service in terms of availability, accessibility and support.

M12 - DSA1.4 – Execution plan for second twelve months of infrastructure operation

This deliverable describes the execution plan for the second half of the ETICS 2 project, including the service roadmap and the infrastructure deployment plan.

3.4.ETICS 2 Partners and SA1 Resources

3.4.1.ETICS 2 Partners

These are the partners participating to the ETICS 2 project.



Beneficiary no.

Beneficiary name

Short Name

Country

Enter Project

Exit Project

1 (Coord.)

European Organization for Nuclear Research

CERN

Switzerland

Month 1

Month 24

2

Istituto Nazionale di Fisica Nucleare

INFN

Italy

Month 1

Month 24

3

Engineering - Ingegneria Informatica - S.P.A.

ENG

Italy

Month 1

Month 24

4

4D SOFT Szamitastechnikai KFT

4DSOFT

Hungary

Month 1

Month 24

5

Board of Regents of the University of Wisconsin System

WISCONSIN SYSTEM

USA

Month 1

Month 24

6

Magyar Tudomanyos Akademia Szamitastechnikai és Automatizalasi Kutatointezet

MTA SZTAKI

Hungary

Month 1

Month 24

8

Forschungszentrum Juelich GmbH

FZJ

Germany

Month 1

Month 24

7

VEGA IT GmbH

VEGA

Germany

Month 1

Month 24



3.4.2.SA1 Resources and Roles

Among the partners, 6 out of 8 participate to the SA1 work package.



Participant id

CERN

INFN

ENG

4DSOFT

UoW

Person-months per beneficiary

66 PM

18 PM

22 PM

8 PM

24 PM

Participant id

SZTAKI

FZJ

VEGA


Person-months per beneficiary

8 PM

0 PM

0 PM



CERN will provide maintenance of the ETICS Services and will implement several of the new features for these Services. CERN will also provide second level support to the Users and to the EGEE/gLite development and integration teams that currently are the main users of the ETICS Services.

INFN, also leader of the SA2 work package and major contributor to the EGEE/gLite development, will develop the services related to user dissemination (e.g. metrics) and implement the submission engine interface allowing ETICS to submit jobs to the EGEE infrastructure via the gLite middleware. They will also have the maintenance and support of the ETICS site in Bologna.

D4DSOFT, also leader of JRA2, together with SZTAKI will integrate in the ETICS Services the Testing Tools plug-ins and the Multi-node Distributed Testing features developed in JRA2.

UoW will continue to provide support for the Condor-based Condor Metronome framework which is the infrastructure currently used by ETICS for submitting build and test jobs of the User Project.

ENG will continue the maintenance and further development of the ETICS Configuration Web application.

4.Present and Future of the ETICS Services

4.1.Etics Services Current Activities

The major goals of the first ETICS project were to start, within a two year program, a professionally managed, integrated system of services and resources for running automated builds and test suites for distributed software projects, to set up a repository of packages, test reports and interoperability information that development projects can use to develop, validate and measure their software products.

ETICS has successfully designed, integrated and deployed a set of web services and tools for configuring, building and testing software, providing web and multiplatform command-line clients and provided an initial implementation of the repository of build and test reports, packages and tools The build and test system provided by ETICS can be efficiently used to set up software engineering procedures for grid middleware and applications as well as more traditional distributed software and stand-alone applications.

The Services of ETICS that will be maintained by SA1 include all the client and server components of the current ETICS software in particular the build and test web services, the repository web service as well as the command-line and web clients.

4.2.ServicesS at CERN, INFN, Wisconsin

ETICS has successfully progressed towards the achievement of its goals by working in four main areas, namely infrastructure, services, community support and dissemination. In terms of infrastructure ETICS has managed to set up three resource sites, at CERN, INFN and UoW providing more than 150 CPUs and more than 15 different types of platforms and a preliminary Service Level Agreement and documented deployment procedures for all services and tools.

4.3.New Requirements and New Communities

The maintenance, upgrade and release of the ETICS Services are major functions of SA1 in order to provide a professional service to the users. Improving and maintaining the current infrastructure will employ about 30% of the resources of SA1. The rest of the resources can be dedicated to extend the features of the Services and to support new user communities.

The major main development of the SA1 consists in the enhancement of the existing software engineering and validation Services with specialized tools and procedures targeted to specific infrastructural needs in term of infrastructure. Different development activities require a combination of common testing tools and metrics (e.g. static analysis, code coverage, unit, integration and system tests and regression testing tools) and specific dedicated tools (e.g. compliance with standards and specifications in a given scientific or engineering field, application-specific benchmarks). SA1 will work with SA2 and JRA2 in order to integrate these external tools to the ETICS Services.

A number of projects and communities are already committed to the use of ETICS and in the adoption of common software lifecycle procedures. However, these communities mainly gravitate around the EGEE infrastructure and the gLite middleware. One of the goals of the ETICS 2 project is to go beyond the EGEE-related projects and provide its services to other user communities.

4.4.New Build Infrastructures

Another objective of ETICS 2 and of the SA1 work package in particular, is to expand the ETICS Services to existing and emerging infrastructures by providing an integrated combination of key enabling technologies (e.g. testbeds virtualization, test management and workflow tools, release management tools) and active involvement of additional specialized providers.

SA1 will expand the ETICS Services beyond the currently supported infrastructures both in technological and organizational directions. The extension consists in the involvement of representative members of European and international infrastructures, such as DEISA and OSG via key players in these fields (Forschungszentrum Juelich) or strong collaboration activities via common partners (University of Wisconsin and INFN). This integration will be both provided by means of virtualization techniques, custom connectors or translators and through the definition and implementation of standard interfaces and repository services application interfaces to the ETICS Services. Furthermore, the support for specialized infrastructure and communities will be increased and based on clear Service Level Agreements contracts.

In order to facilitate the access to existing public, private or custom resources through ETICS, new techniques for harmonising different software engineering tools, federating testbeds resources and repositories of code and packages will be introduced during the 24 months of the project.

5.SA1 PlanS for the first twelve MonthsReporting Period

5.1.Overview of the Objectives

The ETICS Services supported by SA1 lay their foundations on the previous achievements and on the implementation of the initial ETICS project. The partners of ETICS 2 provide an integrated set of key technologies that will facilitate the extension of the SA1 build and test services to additional infrastructures and that will promote industry-standard methods for validation and distribution of software.

The existing Services should evolve a professionally managed operational model based on a federation of resources from different public entities or private companies and with the implementation of effective quality evaluation and monitoring procedures.

As already mentioned in the previous sections the ETICS Services must will considerably profit of recent, but now established, technologies of hardware virtualization software. ETICS 2 SA1 will integrate, for the first time inside, a set of grid-based automated test bed management tools to provide fully virtualized software build and validation environment.

The final SA1 goal is to prepare the transition from the current short-term operational model to a long-term sustainable European Ggrid Iinfrastructure. Explicit effort will be dedicated to prepare the commercialization of grid-based services by including industry-standard methodologies, stricter security and privacy enforcement methods, tools for requirements and release management and investigating business strategies and charging models.

5.2.Milestones and Tasks

The following milestones are proposed for the first twelve months of the project in order to achieve the objectives of the ETICS 2.

5.2.1.Deployment Plan of the ETICS Services

M05 - Infrastructure for Production and Release Candidate installations in place

A standard ETICS Service setup that constantly provides (1) a Production installation and (2) a Release Candidate installation both available to the User Projects.

The Production installation is the official ETICS Service, while the Release Candidate is available for ETICS testing and for preview of new features to selected users of the main User Projects. The release of the service consists in making the Release Candidate (RC) installation the new Production and in installing the former Production hardware with the next Release Candidate (RC+1).

M05 - Automation of Deployment of the ETICS Services

The deployment of an instance of the full ETICS Service should be fully automated. Both the web server and the repository hosts should be installed simply by choosing the host names, a software configuration and set of database exported files.

Automated installations are very important in order to accelerate and make more reliable the release cycle of ETICS. This automation mechanism is also fundamental in order to instantiate development and testing environments for specific teams in other activities.

M06 - ETICS Services Release Cycle Procedures Defined and Implemented

A formal release cycle should be in place and fully documented in order allow faster and organized releases of the ETICS Services. It should cover all phases of the configuration, release and deployment of the ETICS Services on the host nodes and establish all the steps that govern the services evolution and life cycle.

M06 - Design Specification of the Core Services (DSA1.2)

A document describing in detail the architecture of the ETICS Services will available and include the specification of all components and interfaces of the system. It will describe the system as intended at the end of the ETICS 2 project (i.e. March Feb. 2010) with longer term perspectives and possible evolutions and future scenarios.

M08 - Benchmarks and Automated Regression Testing of the ETICS Services

The ETICS Services should have a clearly defined set of datasets for tests and regression testing infrastructure. The automation of the regression testing will also leverage on the installation procedures that can automatically install the whole ETICS Services.

M10 - Monitoring and Alerts on the ETICS Services

The ETICS infrastructure should will be instrumented with a set of monitoring tools and, when possible, correcting applications that will control and fix the status of the ETICS Services resources, the consistency of the different components of the systems. The goal is to correct problems automatically or raise alerts to the SA1 team before such issues endanger the reliability and availability of the ETICS Services to the User Projects.

M12 - Virtualization of the Worker Nodes

The execution of the ETICS build and test processes should be modified to make use of virtualization technologies. The goal is to be able to support a large variety of OS platforms while maintaining a very limited number of OS on the physical Worker Nodes. The ETICS services should provide a large set of virtual pre-installed OS images that are instantiated on the physical Worker Nodes when the corresponding OS platform is needed.

5.2.2.New Features for the User Projects

Below are the milestones that represent the extension of the ETICS Services to new features and functionalities available to the User Projects.

M06 - Deployment Tests Support for Users Projects

The User Projects using ETICS will be able to test the deployment of their software on a specified platform. ETICS should then instantiate the necessary Worker Nodes and proceed with the deployment of the desired software configurations.

M08 - Metrics Disseminator for Trend Analysis

The ETICS Services should will be able to collect the metrics and display their results for any User Project. The disseminator should provide a web interface to select metrics data, customize its visualization for trend analysis plots.

M09 - Support of Distributed Multi-Node Testing

The ETICS Services should will be extended to integrate the distributed testing features implemented by JRA2. This includes the possibility to execute multi-node synchronized tests (previously also known as “co-scheduling”) that will be integrated in the ETICS Services using the Plug-in Framework.

M09 - ETICS Service Level Agreement defined (DSA1.3)

SA1 should develop and implement a standard ETICS Service Level Agreement (SLA) to propose to the User Projects. The SLA will consist of a general document adaptable to different kind of User Projects and to several requirement levels in terms of support, privacy, security, and quality of the services required.

M11 - Release/Patch Management for User Projects

The ETICS Services should will provide a system to define and release software patches for the User Projects. A patch is a set of configurations that defines a partial upgrade of selected user modules. This feature is useful in order to represent variations of an existing configuration.

This feature is the first step of a larger one of adding to the ETICS Services the support of Software Life Cycle and Workflow functionality in order to support integration, build and test processes.

M11 - Feasibility Study of ETICS integration with External Repositories and Infrastructures

The feasibility study should will investigate the possibility of connecting the ETICS Services to established external code repositories (e.g. Sourceforge, Google Code, etc) and to computing resources to use as submission engines (e.g. Amazon EC2, Google App Engine, etc).

M12 - SLA document defined with 2 major User Projects

The SLA framework defined at M09 should be implemented for 2 major ETICS User Projects in order to clearly specify the level of support and the quality of the services provided.

5.2.3.Integration with Other ETICS Activities

M06 - Training and Support of JRA2 and SA2 Development Activities

SA1 will provide training to members of the JRA2 and SA2 activities who will implement extensions to the ETICS system for Submission Engines and for Testing Tools respectively. In addition, if required, dedicated ETICS Services deployments will be provided to JRA2 and SA2 for their development activities.

M07 - Design and Implementation of a generic interface for Job Submission Engines (with SA2)

The Job Submission Engines, where the software of the User Projects is built and tested, should be extended to use new infrastructures. The goal is the implementation of a generic interface allowing other job submission systems to be used (e.g. gLite, UNICORE, etc).

M10 - Extension of Tests and Static Analysis Tools with Plug-in Integration (with JRA2)

The ETICS Service will be extended to include plug-ins for testing and metrics developed by JRA2. SA1 will provide the standard interface for further plug-in development and collection of metrics and reports.

M11 - Integration of ETICS Services with gLite and UNICORE (with SA2).

Integration in the ETICS Services of job submission system implemented using the EGEE/gLite and DEISA/UNICORE middleware. This will allow the submission of ETICS build and test jobs on these grid infrastructures.

M12 - Grid-QCM Certification of the ETICS Services (DSA1.4)

The ETICS Services should be certified at level 2 in the Grid-QCM quality standard, in view of reaching level 3 at the end of the ETICS 2 project as required defined in the ETICS 2 Description of Work.

5.3.Project Risks

Risk 1 - Inability to provide a Service with adequate response time

The risk must be mitigated by moving toward standard solutions that include high availability systems, database clustering and resource load-balancing.

Risk 2 - Lack of the human or material resources needed at the sites, both in term of HR or HW

The This risk can be mitigated by looking for new sources for resources; for instance contribution of the User Projects to the HR or HW resources of ETICS. If unavoidable one could define SLA agreements that control the usage of the ETICS Services by every given project (e.g. number of builds per day).

Effort must be put in ensuring the commitment of the partners in providing hardware resource by specific contractual Consortium Agreements.

Risk 3 - Difficulty in Integrating the Work of Other ETICS 2 Activities

Issues incurred by SA2, JRA1 and JRA2 could affect their ability to deliver their results to SA1, thus limiting the availability of these features into production on the ETICS Services. The risk can be mitigated by constant training, common work and frequent checkpoints of the SA1 work and the one of the other ETICS 2 activities.

6.Gannt Chart View

ETICS 2 SA1 EXECUTION PLAN FOR THE FIRST TWELVE



ICT-RI-223782

2008 © Members of ETICS 2 collaboration

PUBLIC

1 / 16




20AESTHETICS AESTHETIC THEORY AND FEMINIST POETICS FORM HISTORY AND
28 BIOKINETICS OF CADMIUM AND ZINC ACCUMULATION AND DEPURATION
4 APOLOGETICS AND SAVING FAITH IF OURS IS A


Tags: etics 2, of etics, etics, first, execution, twelve