1. INFSO-RI-223782 Support for IPv6 in ETICS EGEE’08 Conference, Istanbul, 22-26 September 2008 Marian ZUREK CERN - ETICS Marian.ZUREK@cern.ch

2. INFSO-RI-223782 Contents General overview Who/what we are: Partners/Architecture ETICS Infrastructure IPv6 compliance (IPv6 plugin) IPv6 Testbed Examples of usage ETICS plugin framework Future work Conclusions 2

3. INFSO-RI-223782 General Overview ETICS stands for E-infrastructure for Testing, Integration and Configuration of Software ETICS started in January 2006 and ended in December 2007. It had a very successful review exceeding all stated objectives ETICS 2 started in March 2008 (ranked first in the proposal selection process) and it’s supposed to run until February 2010 (mostly with EC funding) and then on its own ETICS is not ‘just’ a build system, it’s a complete infrastructure for building, testing, configuring and managing software projects 3

4. INFSO-RI-223782 Partners 4

5. INFSO-RI-223782 Architecture ETICS is not ‘just’ a build system 5

6. INFSO-RI-223782 What ETICS is It’s a software engineering management system It’s a build and test infrastructure It provides tools and resources to configure, manage and analyse build and test runs It provides a common interface to diverse projects to facilitate knowledge sharing and operations management It has an open repository of configuration metadata, packages, reports. The goal is to share information, but also to reliably store and preserve information It has a plugin-based architecture and APIs to allow integrating ETICS into existing processes and extending it with custom actions It’s multi-platform and independent from any specific build or test tool 6

7. INFSO-RI-223782TBDeleted 7 We are running Production testbed with growing number of OS/platfroms combinations: SLC4, SLC4, SL(C)5 family: 32 and 64bits, ia64 (Itanium) Debian RHEL4 : 32 and 64bits OSX (PPC) WinXP Nodes from various geographical locations are also present in the pool (Hungary, Italy, France)

8. INFSO-RI-223782 The ETICS Infrastructure The ETICS Infrastructure is currently based on three resource pools managed by Condor, at CERN, UoW and INFN There are about 450 cores available in the three sites with more than 40 different types of platforms At CERN in particular there are 120 cores and 12 different platforms (a platform is a combination of operating system, CPU architecture and compiler, ex: slc4_ia32_gcc36, deb4_x86_64_gcc412, etc) Additionally various nodes are attached to the CERN pool from third-party projects or organizations for specific use (4D Soft Ltd for DILIGENT in Hungary, GARR for EUChinaGrid and EGEE/SA2, IN2P3 for EGEE/SA2) 8

9. INFSO-RI-223782 The ETICS Infrastructure 9

10. INFSO-RI-223782 The CERN Resource Pool 10

11. INFSO-RI-223782 Under the hood or what’s needed for IPv6 tests 11 A dedicated Condor configuration has been adopted to assure the proper match making for jobs requesting IPv6 resources (not visible to the user) host_network_stack = "IPv6” STARTD_EXPRS = $(STARTD_EXPRS) host_network_stack START = (job_network_stack =?= $(host_network_stack)) “extra” part in the submision engine (not visible to user) append_requirements = ( host_network_stack =?= "IPv6" ) ++job_network_stack = "IPv6”

12. INFSO-RI-223782 Is your code IPv6 compliant?

13. INFSO-RI-223782 Running tests on IPv6 enabled resources

14. INFSO-RI-223782 IPv6 compliance report - ETICS

15. INFSO-RI-223782 IPv6 compliance report - gLite

16. INFSO-RI-223782 IPv6 compliance report - gLite/LCG-DM

17. INFSO-RI-223782 How to fix your code Small hint here …. This will be covered in a short tutorial by Mario Another presentation will be given during JRA1 All Hand meeting in …. dates/place TBConfirmed 17

18. INFSO-RI-223782 Plugins and Metrics Collectors The ETICS system is plugin-based (like for example ECLIPSE) It provides a core set of tools (like IPv6) and a published specification for developing additional plugins Plugins are essentially thin wrappers around existing or custom tools providing very specific functionality like packaging, static or dynamic testing, standards compliance testing, service installation and management, reporting, etc Plugins can publish information in the ETICS system in the form of metrics, which can then be used to do data mining or trend analysis using the available ETICS reporting tools Should another plugin be needed - it can be easily added to ETICS 18

19. INFSO-RI-223782 Examples of metrics collectors MetricsTypeProgramming languages/ technologies ToolETICS Plugin ComplexitystaticJava Python JavancssJCcnPlugin PyComplexityPlugin.py Design qualitystaticJavaJdependJDependPlugin N of potential bugsstaticC/C++ Python Perl PHP Java Flawfinder, RATS PMD Findbugs CFlawfinderPlugin CPyPhpRatsPlugin JPmdPlugin JFindbugsPlugin N of potential bugsdynamicC/C++ValgrindCValgrindPlugin Lines of codestaticAllSLOCCountSLOCCountPlugin CoveragedynamicJavaEmma Cobertura JUnitemmaPlugin JCoberturaPlugin Unit tests success rate dynamicJava Python JUnit PyUnit JUnitPlugin JUnitreportsPlugin.py PyUnitPlugin.py Compliance with standards staticIPv6 WSI IPv6Plugin WSInteroperabilityPlugi n ProfilingdynamicC/C++ Java Jrat Valgrind JRatPlugin CValgrindPlugin 19

20. INFSO-RI-223782 Example of Usage: EGEE EGEE uses ETICS within four Activities: NA4, JRA1, SA2, SA3 JRA1 and SA3 are the main ETICS users (more in the following slide) SA2 has implemented with ETICS the IPv6 compliance analysis of gLite code and the distributed IPv6 experimental testbed where the IPv6 version of BDII has been tested NA4 is using ETICS for experimenting with a few projects like Gridway, mpi, SAGA and the panc quattor compiler 20

21. INFSO-RI-223782 Example of Usage: EGEE – gLite Testing Very little testing is done with ETICS at the moment There is ongoing work to do deployment and patch testing of the gLite metapackages (services) However, this is made difficult by the fact that the definitions of the metapackages and patches are not in ETICS We are working on a Savannah plugin that would allow extracting information from Savannah (bugs, patches, etc) More complex tests are planned but only after this is solved 21

22. INFSO-RI-223782 Lesson learned Taking into account the site policies, building the Condor pool out of geographically dispersed Worker Nodes isn’t a trivial task as it may appear. Numerous issues identified like: Reverse DNS: Solved by hard-coding the IP addresses in the Condor config files Firewall policies (procedures, transitional openings) Condor: Job Match-making: partial match was causing the ETICS production pool throughput degradation Power-cuts, etc. Mail, IM, SMS, phone were very useful 22

23. INFSO-RI-223782 Next Steps Keep the setup operational Store working configurations and setup automated tests/deployments inside ETICS Make sure the ETICS service/infrastructure helps you in achieving your (IPv6 and other) goals (= Provide continuous support to the community ) 23

24. INFSO-RI-223782 Conclusions ETICS in collaboration with GARR and UREC is providing the infrastructure enabling the community to perform the IPv6 tests Automated deployment procedures should be established to guarantee the service persistency We plan to continue the collaboration 24

25. INFSO-RI-223782 The End Q & A 25

26. INFSO-RI-223782 Benefits of Using ETICS Common set of interfaces and tools to different projects Simplifies working with different projects and transferring knowledge among technical people Configuration information is stored in a single place with a common schema and preserved while people or projects change Multi-platform support allow building and testing the same code-base on as many platforms as needed with negligible additional effort The resource infrastructure allows running several builds and tests without having to set up dedicated machines All machines are configured in the same way or use virtual images in order to guarantee reproducibility of results Standard build and test tools are available out-of-the-box and can be applied in the same way to different build/test runs and different projects over time 26

27. INFSO-RI-223782 Benefits of Using ETICS (2) The built-in packaging system abstracts the package information and automatically builds the appropriate package format for the different platforms (tarballs, RPMS, debs, MSIs, etc). No need to maintain separate scripts Reporting tools are available out-of-the-box to control the software evolution, pinpoint issues and quickly solve problems APIs and plugins allow to integrate the tools into existing development processes and extend them with custom tests or reports as needed New plugins and tools developed by a project can be of benefit to all other projects (no duplication of effort) ETICS provides a large set of external libraries in source format or already precompiled for many platforms (the ‘externals’ project). Components can set dependencies on these libraries and automatically configure their workspace. 27

28. INFSO-RI-223782 The ‘Distributed Testing’ Feature One of the last features to be added, still in experimental mode It allows designing complex tests involving several services and test applications to be deployed on separate nodes ETICS analyses the definition and deploys the services on the necessary nodes A synchronization mechanism orchestrate the start/stop of services and the execution of the test applications At the end the results are collected and reported as a single report It is not yet usable by ‘any user’, it requires some deep knowledge of the system to be tested It has been successfully used in a number of cases by the DILIGENT project It has the strong prerequisite that the services to be deployed have to be managed without user intervention, which is not always the case 28