DILIGENT ETICS meeting

Monday 26 Feb 2007, 10:00 → 12:00 Europe/Zurich

DILIGENT meeting with ETICS responsibles to prepare the production of DILIGENT Release Beta

=== Releases === - 0.8: next week (1.0 RC) - 1.0: three four weeks (end March) - 1.1: during April or May === General === 1) Private Infrastructure - requires the installatiuon of NMI and Condor and the configuration of certain enviornment varaibles - all configurations are done on the node side (including which projects are allowed) - the set of a node outside CERN network can create some firewall issues 2) Notification - audit mechanism can be an alternative solution (in etics 1.1) 3) Locking configuration - available in etics 1.1 - recursive locking available - dependencies are not locked 4) Cloning - no plans to include in the short-term, needs better analysis (different strategies possible) - better configuration management can help to decrease the need of such functionality 5) New WebApp - requirements will be collected and a new layout proposed (April-May) - avaialble in Summer 6) Remote Build/Test - available in etics 0.8 - scheduling of builds: not in etics 1.0, probably in etics 1.1 or 1.2 - user profiles: mid-term plans (together with MyETICS) - remote test is availale but limited to one single node, one platform per submission === Deployment Testing ==== 1) Automatic Deployment - long-term plans only, the existence of "deployment commands" (installation and configuration) can be the solution - usage of test commands (init test) can be the solution in the short-term - customed diligent generated report pages can be integrated as plug-ins 2) Testing dependencies - ETICS dependencies are common to build and test - deployment testing is a particular case that can require setting up dependencies from the components to test to the test tool (usually it is the other way around) 3) Testing Role - tester role: executes remote tests - developer role: creates/updates components configurations === ACTIONS === Action 1: send the contact person from DILGIENT to Alberto Action 2: DILIGENT should provide a list of prioritised requirements Action 3: ETICS will discuss the introduction of a "deployment command" and come back to DILIGENT for further discussion