Tracking Tools Evolution TF meeting on savannah, jira and a new ggus dev. item

Tuesday 8 Oct 2013, 10:00 → 12:00 Europe/Zurich

28/1-025 (CERN)

Maria Dimou (CERN)

Tracking Tools Evolution TF twiki is HERE!

Dial-in numbers:	+41227676000 (English-US, Main)
Access codes:	0102254 (Leader) 0174222 (Participant)
Leader site:	https://audioconf.cern.ch/call/0102254
Participant site:	https://audioconf.cern.ch/call/0174222

F2F MEETING WITH GGUS DEVELOPERS AND SAVANNAH EXPERTS TO DISCUSS:

1. WLCG-related savannah projects' migration to jira. Status info in the Tracking Tools TF twiki (see also attachment with ATLAS info).

   1. ALICE input by Alina Grigoras: Alina is in charge of the migration of ALICE Offline projects to JIRA.
      1. AliEn2 is migrated.
      2. AliEn and AliRoot are in the process (on-going work to adapt their numerous custom fields).
      3. AAF (ALICE Analysis Facility) and ALICE Analysis are pending.
          
   2. ATLAS input by I.Ueda:
      1. ATLAS has several categories of savannah projects. In this thread  one can see activities for migrating the contents of "ATLAS Computing Operations". There has not been much progress within "ATLAS Computing Operations", waiting for the migration tool to be adapted to Jira 6.
      2. I.Ueda will summarise experience gathered in ATLAS by some test migrations.
   3. CMS input by Christoph Wissing:
      1. CMS Computng is being migrated to GGUS, meeting this afternoon (agenda https://indico.cern.ch/conferenceDisplay.py?confId=272817 ).
      2. The CRAB project will definitely be migrated.
      3. Other CMS savannah trackers appended to this agenda as "More information". Feedback is in prepartion from within CMS.
   4. LHCb input by Joel Closier attached to this agenda as Document.
   5. IT + Grid projects:Reminder sent by Benedikt to IT on 2010/10/03This is a reminder for the Grid and IT related projects. Answers concerning the migration/archiving of the following 83 projects are still missing:
        https://savannah.cern.ch/search/?type_of_search=soft&words=%%%&type=8
        https://savannah.cern.ch/search/?type_of_search=soft&words=%%%&type=10
      https://savannah.cern.ch/search/?type_of_search=soft&words=%%%&type=5
      https://savannah.cern.ch/search/?type_of_search=soft&words=%%%&type=13
      Can this TF decide what the future of each should be? savannah.cern.ch homepage shows the following number of projects:
      1. 10 Other Grid Projects.
      2. 8 LCG Grid Deployment
      3. 8 LCG Applications Area
      4. 30 EGEE
      5. 35 CERN IT
   6. Savannah dev. team: Current savannah phase-out plan is to keep the savannah server alive as long as there are projects which are in the process of migration to jira. Those project owners who said nothing about their inrtention, should remember that  all the tickets migrated to jira would be accessible via the same URL with savannah.cern.ch, but the tickets not migrated shall simply disappear.
   7. JIRA FAQ up-to-date in the Service Now KB https://cern.service-now.com/service-portal/faq.do?se=JIRA-service

2. GGUS development request: The (possible) implementation of the request to Notify >1 site with a single GGUS ticket submission. Details in https://savannah.cern.ch/support/?138299 . This is a complex development so we have to be clear about the requirements. We also need to understand how often this bulk submission is likely to be needed. Summarising what we have so far:
   1. To avoid mistakes and abuse, the privilege should be offered to expert supporters/submitters.
   2. The submitter name should remain their own (no TPM involvement) so they control the future exchanges.
   3. Subject and Description field should be typed once and cloned to all individual ticket instances.
   4. The official site name, as in GOCDB or OIM, should still be offered for selection to the expert submitter, so they don't risk to mis-type complex names, e.g. AEGIS03-ELEF-LEDA (maybe not a WLCG name but the prettiest I found).
   5. The possibility to select >1 ROC/NGI (not only "Notify Site") should also be foreseen.
3. Re-visit the Mandate of this TF and decide its future direction:
   1. Developers, deployers, experts of GGUS, SNOW, savannah, jira and the experiments discuss development options for each tool and interfaces between them, when required.
   2. Periodically present status reports at the fortnightly WLCG Operations meeting.
   3. Propose timelines for features’ / fixes’ entry in operation at the same meeting, to get agreement from the community.
4. A.O.B.

IF PEOPLE NEED TO CONNECT REMOTELY PLEASE INFORM MARIA A.S.A.P. TO SET UP AUDIO CONF.

document LHCb-Savannah-to-Jira-migration-plan

Document Librarian_AND_Integrators_meeting_20130924

Minutes TrackingToolsTF_20131008am.txt

more information CMSsavannah.pdf