1. All-Hands Meeting Outcome and Discussion
ETICS All-Hands – 23 May 2007
All

2. My Goals
Understand the status of co-scheduling and make a plan to have the system fully deployed before August
Come up with a list of actions to make the system more intuitive, easier to use, more reliable and faster by the end of the year and have that ‘certified’ by users
Come up with a reasonable plan to involve EGEE and DILIGENT more in using ETICS to do ‘real’ testing
ETICS 3rd All-Hands Meeting - University of Wisconsin, Madison /05/2007

3. Your Goals?
ETICS 3rd All-Hands Meeting - University of Wisconsin, Madison /05/2007

4. Understand the status of co-scheduling and make a plan to have the system fully deployed before August
Co-scheduling has been shown to work. Thanks to all the people involved for the effort they put on this
The current plan is:
Have all required software available and integrated by the end of June
Have the system deployed and running by the end of July at CERN, INFN, UoW, possibly Southampton
Produce a small, but significant number of scenarios and tour around showing what can be done
Involve users from EGEE, DILIGENT and OMII-Europe in deploying tests based on this technology
ETICS 3rd All-Hands Meeting - University of Wisconsin, Madison /05/2007

5. This topic has not completely been addressed
Come up with a list of actions to make the system more intuitive, easier to use, more reliable and faster by the end of the year and have that ‘certified’ by users
This topic has not completely been addressed
We have discussed about changes in the web app (use buttons instead of mouse clicks)
The common portal goes also in the direction of making the system more intuitive
We haven’t discussed about the CLI and how to make it faster, this is becoming an issue
We haven’t explicitly discussed how to have user recognition of the improvements
ETICS 3rd All-Hands Meeting - University of Wisconsin, Madison /05/2007

6. A meeting for DILIGENT will be organized during June
Come up with a reasonable plan to involve EGEE and DILIGENT more in using ETICS to do ‘real’ testing
We have decided to organize specific ‘workshops’ dedicated to each project
The meeting must be technical, with the right people on both sides (ETICS and customer project)
A meeting for DILIGENT will be organized during June
A meeting with EGEE has been already scheduled twice and twice cancelled, we have to insist (the good news is that EGEE management has also requested for it)
Same thing is being organized with OMII-Europe
The message is that we have to take the project by hand and guide them a bit
ETICS 3rd All-Hands Meeting - University of Wisconsin, Madison /05/2007

7. Editing functions
The new editing functions able to work on the local store without pushing objects in the DB have been show to work
They will be tested in June with the goal of releasing them in July
The –nonetwork option and parameter will be removed in favour of an automatic mechanism that detects if the DB cannot be contacted and warns the user that some operations cannot be done
ETICS 3rd All-Hands Meeting - University of Wisconsin, Madison /05/2007

8. Auditing
The logging/auditing functionality works fine (some cosmetic issues)
It is now scheduled for release in ETICS 1.1 at the end of June
ETICS 3rd All-Hands Meeting - University of Wisconsin, Madison /05/2007

9. Interoperability Metrics
We have agreed that it’s not reasonable at the moment to define ‘interoperability metrics’
We rather take the approach of taking a few of the use/test cases defined in D3.2 and fully implement them as demonstrators
D3.3 will then describe this work as proof of how ETICS can be used to verify interoperability
ETICS 3rd All-Hands Meeting - University of Wisconsin, Madison /05/2007

10. Plugins and profiles
We have decided to define a (limited) number of preset profile grouping a certain number of plugins each
The presets will be defined using a (XML) file shipped with the client
The web app will know what presets are available and allow users to display a list and check one or more of them
Resolution is done on the client
Expert users can override the presets or define new profiles locally
The fact that a plugin-target association overrides the default behaviour will be changed
ETICS 3rd All-Hands Meeting - University of Wisconsin, Madison /05/2007

11. Plugin Implementation
We have now an interesting set of plugins to be tested and released
This will be done during June
We have to agree on the distribution of work. Current understanding was
WP3: C/C++ tools (to be done)
WP4: Java tools (tools identified, plugins developed, integration and test to be done)
WP5: Python tools (some tools identified, some more work to do, some plugins developed, integration and test to be done)
This division of work is under discussion. I’m open to suggestion
ETICS 3rd All-Hands Meeting - University of Wisconsin, Madison /05/2007

12. Project schedule Review: January 2008 Final release: October 2007
Everything deployed ready to be used: July 2007
Feature freeze: June 2007
Feature freeze means that no additional features will be considered, existing incomplete features can be completed before July
At the end of July, incomplete features will be stopped
We may have to revise depending on how critical the missing features are in term of system functionality
ETICS 3rd All-Hands Meeting - University of Wisconsin, Madison /05/2007