Savannah to Jira Migration LHCb Computing Workshop 19 th of May 2014

Is it necessary to migrate? Savannah is not supported any more in its development. o We will not be able to satisfy the increasing needs of the users o Any problems that might arise, in the long term, with eventual changes on the hardware and software (MySQL and operating system) platform, could partially or totally disable the functionality of Savannah Jira has been chosen by IT to replace Savannah as a result of a market survey. o Jira offers additional functionality and flexibility through a user friendly interface. o Easy to learn and use it from day 1. It’s a commercial software constantly maintained while new functionalities are periodically added. Migrating a project from Savannah to Jira is not mandatory! o It is an option we offer the users when there is need of data preservation. o Otherwise, a new project may be started already in Jira and leave all data as they are in Savannah.

What will happen to Savannah? We would like to stop Savannah at some time in the future, once all of the projects have been treated. For each project we propose one of the following options o Migration to Jira We use in house developed specific tools (plugin) We perform the initial configuration that better suits the users o Archiving The information related to the projects will be archived o Static web pages Allows access to the information of the projects like if it was in read- only mode and with no possibility to perform any administrative tasks nor executing Savannah like operations like search.

When is the deadline? There is no deadline There is urgent need to migrate all the projects at the earliest possible date for the following reasons: o The in house developed plug-in is not guaranteed that it work with the future updates of Jira (it did happen in the past) o We agreed with IT not to install any new Jira updates until the migration process is terminated o There is increasing request from the users to add specific functionalities in Jira which will be available in the new versions. Migration schedule: o 27 Projects migrated in the production instance of Jira o 4 Projects Archived: ( Archiving will effectively take place at the end of the process ) o 32 Projects to be scheduled for migration in the coming weeks already tested o 28 projects to be tested and suggested/considered for migration o 126 Projects to be suggested or considered for archiving We consider the overall process might be completed by July 2014.

LHCb projects (1/2) Activity coordinated with Marco Clemencic o 1 st step: List of projects to be considered for Migration o 2 nd step: Mapping of custom variables between Savannah and Jira o 3 rd step: Test migrations and bugs reporting Repeated operations. The bugs were concerning mostly: o Wrong formatting of text/code o Files/links were not present in Jira o Roles assigned to the users o Other minor issues

LHCb projects (2/2) Considered for migration: 11 projects. o Ganga, GAUDI, LHCb physics software, LHCb Scripts, LHCb Tag Collector, LHCb Trigger Configuration, LHCb Upgrade Conditions Database, LHCbDirac, LHCb Conditions Database, LHCb Data Quality, LHCb Deployment The remaining 7 projects will be archived once a final decision is taken o LHCb Production Operations, Gauss, LHCb Eclipse Plugins, LoKi, LHCb LCG Support, BENDER, LHCb Computing Operations

How to use a migrated project? All the information that was available in Savannah will also be available in the migrated project in Jira. Jira is using similar layout with Savannah The users associated to the project will be created also in Jira if they not exist already. Associations between users and issues are kept the same Access rights at project level will also be migrated but it is suggested to use more powerful tools like egroups and “access scheems” which greatly facilitates the management of the projects o We provide support for this …

Going live.. A test case for demonstration purposes: Gaudi

Thank you