EMI 1 (Kebnekaise) - Activity

here

• ETICS-client 1.5.0-1 FULL Release Notes

ETICS-project configurations:

• emi_B_1_rc0, alias for the emi_B_1_dev
  • contains all the sub-system configurations, that were mentioned for EMI-0, with .DEFAULT properties
  • contain "in work" sub-system configurations, providing in this way an automatic build of the latest tags against new versions of dependencies, enabling anticipation of problems
  • nightly-builds - running at 12:00 and 22:00 each day
  • An overall 91% success rate was obtained after the second NB - the RC0 milestone is considered achieved on 22.Feb.2011
  • History of NBs:
    • First NB results: Logs, Artefacts
    • Second NB results: Logs, Artefacts
  • RC0 repository: http://emisoft.web.cern.ch/emisoft/dist/EMI/1/RC0/sl5/
  • EMI 1 RC0 .repo file
  • RC0 Configurations Update Log

• emi_B_1_rcX (with X= [1|2|x]) - project-configurationa for various Release Candidates stages:
  • RC1:
    • standard build instructions, no special options apart from the standard QA options
    • considered achieved when a threshold of 100% successful build of binary packages
    • An overall 100% success rate was obtained and the RC1 milestone is considered achieved on 14.Mar.2011
    • emi_B_1_rc1
      • project-configuration to be used from 22.Feb.2011, with the new etics-client (1.5.0), no .DEFAULT properties defined
      • mock configuration name: emi-1-RC1-sl5-x86_64
      • nightly -builds - running from Sunday to Friday at 04:00, 12:00, 20:00, and on Saturday at 04:00, 20:00
      • QA-metrics nightly-builds - running Saturday at 12:00
      • RC1 repository: http://emisoft.web.cern.ch/emisoft/dist/EMI/1/RC1/sl5/
      • EMI 1 RC1 .repo file
      • RC1 Configurations Update Log
      • Last (100% successful) NB
  • RC2:
    • emi_B_1_rc2
      • project-configuration to be used from 14.Mar.2011, with the follwing option enabled for the build: –createsource and –repackage, but with strict.compliance.check=False
      • nightly -builds - running at 04:00, 12:00 without the "--repackage" option and at 20:00 with "--repackage" option
      • QA-metrics nightly-builds - to be enabled
      • RC2 repository: http://emisoft.web.cern.ch/emisoft/dist/EMI/1/RC2/sl5/
      • EMI 1 RC2 .repo file
      • RC2 Configurations Update Log
      • Last (100% successful) NB
  • RC3:
    • emi_B_1_rc3
      • project-configuration to be used from 30.Mar.2011, with the following option enabled for the build: –createsource and –repackage, with strict.compliance.check=True
      • threshold for declaring achieved the RC3 step if an overall successful build of 60 %, meaning successful repackage with Mock step.
      • nightly -builds - running at 12:00, 22:00
      • QA-metrics nightly-builds - to be enabled
      • RC3 repository: http://emisoft.web.cern.ch/emisoft/dist/EMI/1/RC3/sl5/
      • EMI 1 RC3 .repo file
      • RC3 Configurations Update Log
      • Last (69% successful) NB
• Final Release configuration, emi_B_1_rc4
  • project-configuration to be used from 11.Apr.2011, with the following option enabled for the build: –createsource and –repackage, and with property strict.compliance.check=True
  • threshold is an overall successful build of 100 %, meaning successful repackage with Mock step; exceptions can be accepted, if justified
  • nightly -builds - running at 12:00, 22:00
  • QA-metrics nightly-builds - on Friday
  • RC4 repository: http://emisoft.web.cern.ch/emisoft/dist/EMI/1/RC4/sl5/
  • EMI 1 RC4 .repo file
  • RC4 Configurations Update Log

• The strict.compliance.check property (available with etics-client >=1.5.2-1, Release Notes) can be defined at the project level. If it set to "True" the results of the mock builds are taken into account in defining the status of a component. That is, if Component A builds in ETICS, but fails in mock, it is marked as Successful if strict.compliance.check=False and it is marked as Failed if strict.compliance.check=True

Acceptance Criteria

The acceptance criteria are the conditions by which a Product is considered ready or not for inclusion in an EMI release. The criteria can be "exclusive" or "inclusive". Failing an exclusive criterion causes exclusion from the release, failing an inclusive criterion doesn't cause exclusion from the release, but the Product is marked as not fully compliant with the release criteria. The exclusive criteria are marked in bold in the table. Refer to the legend for an explanation of the colour coding.

• EMI 1 Acceptance Criteria table

How to use JAVA in EMI

• How to use JAVA in EMI

ETICS usage examples:

Example for the WA use:

Details Hide Details

etics -checkout --ignorelocking --config "your_configuration" --project "emi" --project-config "emi_B_1_rc1" --runtimedeps --forcecheckout --verbose --continueonerror
etics -build  --config "emi-glite-apel_R_3_2_5_1" --verbose --target postpublish --continueonerror
platform:   sl5_x86_64_gcc412EPEL

Example using the etics-client:

Details Hide Details

  #  python etics-client-setup.py --volatile default

   # etics-checkout --c <component_configuration_name> --project-config <project_configuration_name> --platform sl5_x86_64_gcc412EPEL <component_name>

   # etics-build --platform sl5_x86_64_gcc412EPEL <component_name> 

ETICS-configuration schedule

• Order of ETICS sub-systems configurations:
  1. VOMS:
  2. CESNETSecurity:
     • gridsite-[shared|apache], glite-security-gsoap-plugin, glite-security-gss, glite-px-proxyrenewal
  3. gLiteSecurity:
     • glite-security-[lcas|lcmaps] glite-security-[trustmanager|util-java]
  4. DataManagement
  5. gLiteInformationSystem:
     • bdii, glue-schema, glite-info-provider-[release|service|ldap]
  6. gLiteL&B, DGAS, APEL, ARGUS
  7. gLiteJobManagement (CREAM+WMS), ARC, UNICORE, StoRM

-- DoinaCristinaAiftimiei - 19-Dec-2010