200 likes | 315 Views
WP3 - Software Configuration Tools and Methodologies. Elisabetta Ronchieri INFN CNAF ETICS 2 nd EU Review (CERN) 15 February 2008. Contents. Goals Achievements Challenges WP3 in Numbers Conclusions. Contents. Goals Achievements Challenges WP3 in Numbers Conclusions.
E N D
WP3 - Software Configuration Tools and Methodologies Elisabetta Ronchieri INFN CNAF ETICS 2nd EU Review (CERN) 15 February 2008
Contents • Goals • Achievements • Challenges • WP3 in Numbers • Conclusions ETICS 2nd EU Review - CERN - 15 February 2008
Contents • Goals • Achievements • Challenges • WP3 in Numbers • Conclusions ETICS 2nd EU Review - CERN - 15 February 2008 3
Goals G1. Provide a configuration, build and integration system able to describe software tasks to be executed by the ETICS facility. G2. Provide a configuration information schema able to capture the configuration information of software developed by software project and a coherent storage of such information in the ETICS database ETICS 2nd EU Review - CERN - 15 February 2008 4
Goals G3. Web Server: the heart of the ETICS system • Provide a logic for the entire ETICS system • Handle access to the ETICS system in secure mode • Handle metadata, artefacts, and user requests • Perform complex queries on behalf of the clients • Handle build/test remotely • Support build/test locally G4. Command Line Interfaces (CLIs): one of the ETICS clients • Allow users to register their software, specify configuration information (i.e., edit metadata) • Handle access to Web Service in secure mode • Checkout code and metadata • Build/Test code locally and remotely • Tag code and metadata • Produce reports and different format of artefacts ETICS 2nd EU Review - CERN - 15 February 2008 5
ETICS Portal (myETICS, Build/Test, Repository, Administration) Repository Service Web Service Via browser Project DB Clients ETICS CLIs, Build/Test Web Serivce and metadata Build/Test Artefacts Report DB Metronome Execution Engine Metronome Client Wrapper WNs ETICS Infrastructure
Contents • Goals • Achievements • Challenges • WP3 in Numbers • Conclusions ETICS 2nd EU Review - CERN - 15 February 2008 7
Achievements A1. Authentication and Authorization • Performed authentication using standard x.509 certificates in Web Service and CLIs • Registered information of users (e.g., name and distinguish name) in the ETICS data model • Based authorization on role definition • i.e., defined roles to descriminate the operations users can perform • e.g., clients connecting without certificate are mapped as Guest • Allowed or denied operations to the users by Web Service ETICS 2nd EU Review - CERN - 15 February 2008 8
Achievements A2. Software Metadata definition • Based schema version on Common Information Model (CIM) • Defined formal entities to express project structure, build/test/checkout configurations, security information, dependencies, environment variables, properties, users, roles • E.g., software project structure and configuration structure • Project, Subsystem and Component referred as Modules • More than one Configurations is allowed for each Module • More than one Platforms is allowed for each Configuration • Set Hierarchy in Project and Subsystem Configurations Project Subsystem Component Component ... Subsystem ... Component ..... Configuration Platform 1 VCS Command Build Command Test Command Dependency1 Property1 Environment1 Platform n VCS Command Hierarchy1 ETICS 2nd EU Review - CERN - 15 February 2008
Achievements A3. Build/Test • Handled the downloading of code and metadata information • Supported the build and test locally and remotely • Generated platform specific artefacts (e.g., RPMS, MSI, Debian, tarballs) during the build of software • Generated build and test reports • Supported the browsing of software information • Supported the editing of software metadata • e.g., the possibility to create metadata, modify/remove them and copy existing metadata • Supported co-scheduling by the editing functionality • DT {node1, node2, …, nodeN} • Set hierarchy in DT configuration • Node {service1, service2, …, serviceN} • Set services in Node configuration • Handled code and metadata tag Project DestrebutedTest Node Node ... Subsystem ... Component ..... ETICS 2nd EU Review - CERN - 15 February 2008 10
Achievements A4. Interoperability and Compliance to Standards • Metrics • Identified four interoperability metrics • Number of 3rd Party Components (No3C) • Number of Generic Components (NoGC) • Number of Architectural Revisions (NoAR) • Number of Versions (NoV) • Used configuration information stored in the ETICS database • Collectors • Provided information collectors for the reporting engine • Compliance to standards: Ipv6 WS-compliance • Interoperability Metrics ETICS 2nd EU Review - CERN - 15 February 2008 11
Contents • Goals • Achievements • Challenges • WP3 in Numbers • Conclusions ETICS 2nd EU Review - CERN - 15 February 2008 12
Challenges C1. Improve the data model in order to guarantee a better response time from the backend • CIM does not scale to large software applications • Started a revision of the data model C2. Improve the CLI performances • Current version based on CIM and SOAP • As the size of a project increases, the performance of the client decreases to handle large XML documents • Substantially performance improvements by using newer version of the Python SOAP engine (called ZSI) in handling large XML documents • Started tests in the ETICS client C3. Improve the calculation of the configuration properties • Substantially performance improvementsby making better use of caching ETICS 2nd EU Review - CERN - 15 February 2008 13
Contents • Goals • Achievements • Challenges • WP3 in Numbers • Conclusions ETICS 2nd EU Review - CERN - 15 February 2008 14
WP3 in Numbers Deliverables: Milestones: ETICS 2nd EU Review - CERN - 15 February 2008
WP3 in Numbers Measurements • Supported Platforms 41 • Fedora Core 4 • Scientific Linux 3 • Scientific Linux Cern 5 • Red Had Enterprise Linux 5 • SUSE 5 • Solaris 1 • Debian 4 • centOS 5 • Darwin/Mac OS 4 • win32 1 • aix 1 • ubuntu 3 ETICS 2nd EU Review - CERN - 15 February 2008 16
WP3 in Numbers Measurements: • Supported languages 7 • C, C++, Python, Java, Perl, sh, csh • Implemented Requirements 97.56% D3.1 • Total number of open and closed bugs over time • Ratio of closed/open bug over time ETICS 2nd EU Review - CERN - 15 February 2008 17
Contents • Goals • Achievements • Challenges • WP3 in Numbers • Conclusions ETICS 2nd EU Review - CERN - 15 February 2008 18
Conclusions • Most important achievements A1. Authorization and Authentication A2. Software Metadata Definition A3. Build/Test A4. Interoperability and compliance to standards • Three outstanding challenges C1. Data Model Structure C2. CLI Performances C3. CLI Property Calculation • Planned in ETICS II activities to address the challenges ETICS 2nd EU Review - CERN - 15 February 2008
Thanks http://www.eu-etics.org ETICS 2nd EU Review - CERN - 15 February 2008