alma integrated computing team coordination & planning meeting #4 santiago, 19-21 november 2014...

8
ALMA Integrated Computing Team Coordination & Planning Meeting #4 Santiago, 19-21 November 2014 Reporting Software Principles M Chavan, ESO R Soto, ALMA

Upload: bruno-watkins

Post on 31-Dec-2015

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: ALMA Integrated Computing Team Coordination & Planning Meeting #4 Santiago, 19-21 November 2014 Reporting Software Principles M Chavan, ESO R Soto, ALMA

ALMA Integrated Computing Team

Coordination & Planning Meeting #4 Santiago, 19-21 November 2014

Reporting Software Principles

M Chavan, ESOR Soto, ALMA

Page 2: ALMA Integrated Computing Team Coordination & Planning Meeting #4 Santiago, 19-21 November 2014 Reporting Software Principles M Chavan, ESO R Soto, ALMA

ICT-CPM3 17-19 June 2014

At CPM-3: reporting software has special status Zero-risk area – under well defined conditionsAllows fast-tracking from developer to end-user, to shorten

development loop ICT-3269 created to follow up First draft of document: Aug 2014 Developers discussed with Release Manager Consensus: Oct 2014 Prototype implementation for KPI reports development

History

Page 3: ALMA Integrated Computing Team Coordination & Planning Meeting #4 Santiago, 19-21 November 2014 Reporting Software Principles M Chavan, ESO R Soto, ALMA

ICT-CPM3 17-19 June 2014

Tools that extract data, then process and serve itProduce HTML, PDF, XML, JSON, …

Applications that alter data are not considered RS Subsystem Lead proposes, Release Manager approves Reporting Software does not necessarily follow ALMA

SW release cycle

Reporting Software

Page 4: ALMA Integrated Computing Team Coordination & Planning Meeting #4 Santiago, 19-21 November 2014 Reporting Software Principles M Chavan, ESO R Soto, ALMA

ICT-CPM3 17-19 June 2014

RS runs on dedicated Virtual Machines Uses production database with read-only accounts

Accounts are resource-limited (runaway queries, etc.) RS is secured like all other Web applications

Unless it serves public ALMA data

Sandboxing (ensuring zero-risk)

Page 5: ALMA Integrated Computing Team Coordination & Planning Meeting #4 Santiago, 19-21 November 2014 Reporting Software Principles M Chavan, ESO R Soto, ALMA

ICT-CPM3 17-19 June 2014

RS runs on ALMA standard Linux/Tomcat serversUses standard configuration files in $ACSDATA/config

Any deviation from standards must be agreed upon between developers and operationsChanges to kernel parameters, Tomcat configuration

parameters, etc. Any non-standard software will be installed by

operationsA special version of the Python interpreter, etc.

Allow the VM to be recreated quickly and reliably In case of crash, etc.

Runtime environment

Page 6: ALMA Integrated Computing Team Coordination & Planning Meeting #4 Santiago, 19-21 November 2014 Reporting Software Principles M Chavan, ESO R Soto, ALMA

ICT-CPM3 17-19 June 2014

Create and maintain the VM(s) where RS is running Monitor the state of the VM, Tomcat container(s),

network and database server Provide a test environment that mimics the production

environment VM backups will be provided

Crash recovery

Responsibilities: Operations

Page 7: ALMA Integrated Computing Team Coordination & Planning Meeting #4 Santiago, 19-21 November 2014 Reporting Software Principles M Chavan, ESO R Soto, ALMA

ICT-CPM3 17-19 June 2014

Development and phase A testing (obviously) Installation of RS applications on the test and

production environmentsCrash recovery

Coordination with DSO for Phase C testing and deployment to production environment

HousekeepingWhich version of which tools is installed where?

First-line end-user assistance — this is a critical issue

Responsibilities: Developers

Page 8: ALMA Integrated Computing Team Coordination & Planning Meeting #4 Santiago, 19-21 November 2014 Reporting Software Principles M Chavan, ESO R Soto, ALMA

ICT-CPM3 17-19 June 2014

All current reports will be migrated to the RSPhase One Manager, integrated reports, etc.

Shift Log Tool special case: reporting code is delivered with desktop client and part of Web client Desktop client will invoke Web-based reports

If approved, migration will begin 1Q2015

Transition