1 / 8

ICT infrastructure changes Erik Allaert

ALMA Integrated Computing Team Coordination & Planning Meeting #1 Santiago, 17-19 April 2013. ICT infrastructure changes Erik Allaert. Overview. Mailing lists: centralize in one place Repository: CVS → SVN newer, still actively maintained technology

feoras
Télécharger la présentation

ICT infrastructure changes Erik Allaert

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ALMA Integrated Computing TeamCoordination & Planning Meeting #1Santiago, 17-19 April 2013 ICT infrastructure changes Erik Allaert

  2. Overview • Mailing lists: • centralize in one place • Repository: CVS → SVN • newer, still actively maintained technology • TWiki: almaw.hq.eso.org → ictwiki.alma.cl • new location • new structure • new version • JIRA: • new server • new version • new project • heavily customized workflow ICT planning meeting #1 / SCO

  3. Mailing lists • 17 common ICT mailing lists, hosted centrally at SCO • All lists configured same, same policy: • per default no monthly password reminder • a limit of 3MB per message • lists are archived • list-membership is restricted, i.e. (un)subscription requires the approval of a moderator • lists are administered by SE-QM only • … • For details: see https://ictwiki.alma.cl/twiki/bin/view/SEQM/IctMailingLists (requires account on ictwiki) ICT planning meeting #1 / SCO

  4. CVS → SVN … • Note: only for project2 – other projects remain under CVS at cvssrv.hq.eso.org • Decided at September 2012 planning meeting – subject to conditions for using replication software (WANdisco) • Initially planned for January 2013, but postponed due to acceptance activities and other JAO priorities. • Scheduled for 18-22 March, ready on 20 March ICT planning meeting #1 / SCO

  5. … CVS → SVN • Test-server (without replication) available well in advance to exercise normal operation by developers, NRI, build-farm, … • allowed to identify more suitable directory structure • tested fixes for code referring explicitly to CVS administrative files • some Makefiles assumed particular file-permissions on binary files, while SVN deals with that in a different way • After migration and enabling replication • few WANdisco cases (talk-back script, logs, address already in use) • SVN client version • Pending: branching strategy / use of trunk ICT planning meeting #1 / SCO

  6. TWiki • almasw.hq.eso.org: • TWiki 4.3.1 (Apr 2009) • Organized in webs corresponding to CIPT-subsystems • In use in its current form since ~2004 • Accumulated ~450 users (in spite of being open for almost all webs) • ictwiki.alma.cl: • Twiki 5.1.3 (Dec 2012) • Organized in webs according to ICT-groups • Subject to JAO access policy: user account needed (130 at start) • Available for testing since ~Jan 2013, to users since Apr 2013 • With read-only snapshot of almasw (as it was when frozen) • Option to move old topics to new webs for limited time ICT planning meeting #1 / SCO

  7. JIRA … • Decided during Sept 2012 CIPT leads-meeting to go for new ICT “project” within JIRA • Opted for separate, independent server as JIRA host • All ICT standard activities should have an ICT ticket (to which other projects/tickets can link) • Access to ICT-project: all ICT-members, TBD list of scientists, operators, engineers (to be agreed with DSO/SIST/ASG) • Clear initial involvement of group-lead to decide on the priority of the issue ICT planning meeting #1 / SCO

  8. … JIRA • jira.alma.cl: • JIRA 4.4 • > 130 projects, 40 issue-types, >1350 users, … • several system-wide settings not optimal for ICT (e.g. resolution, priority, time tracking, issue statuses, …) • New server: • JIRA 5.2.9 • 9 issue types, with clear definition • specific workflow for typical ICT software development process ICT planning meeting #1 / SCO

More Related