Release Management

From GEANT2-JRA1 Wiki

Contents

[edit]

Objectives

To ensure a harmonious combination between the services, the GUI, and the deployment of services by the NRENs, a release management process has been devised and a release management team has been set-up. The aim of the tests and release management process is to offer stable services to the NRENs and so favour a large deployment of the services included in each release.

[edit]

Achievements

[edit]

Release Management Process

After the release team has been set up, the first task was to write a Release Management Process.

[edit]

First production release - perfSONAR v1.0

Then, the Release Management Process was applied to a selected group of services for the first time. The services chosen to be included in this first release were:

  • Round Robin Database Measurement Archive (RRD MA): This service was chosen because has already been deployed by several networks - round robin databases are widely used within the research community - and most of planned functionality has been developed.
  • Lookup Service (LS): This service was selected as it “glues” together all the available perfSonar services.

The Release Management Process started after installing two tools by the release management team: Subversion and Bugzilla. Subversion gave the developers group a more flexible and faster versioning control system, which replaced Concurrent Versions System (CVS). Bugzilla was needed so that the developers and release management team have a reliable and easy to use bug-tracking system that can be as well used for managing tasks. Therefore, both tools help the management of software releases and the development process by providing the way to:

  • Track bugs and code changes
  • Communicate with team mates
  • Submit and review patches
  • Manage quality assurance

The release management team worked on an installer system that would work generally. Both a text-based and a graphical installer were developed, together with documentation instructing users on how to install all the tools that already need to be in place before staring the installation of perfSONAR Before the final production release was launched, several Release Candidates were made available. The community of users and developers was asked to install and try the Release Candidate, filling in the eventual bugs on the bug-tracking software – Bugzilla. Finally, on 18th July of 2006 PerfSONAR_v1.0 was released.

[edit]

Next steps

The next objective of the release management team is to release perfSONAR v2.1, v2.2.

[edit]

Requested features

To be included in one of the subsequent releases v2.x:

  • RRD MA - Input errors and output drops (RL)
    • Priority: high, Released end of August.
    • Requested for the PERT (highly required feature) and for the LHC support package we are preparing.
  • perfsonarUI
    • Utilisation of input errors and output drops (VJ and NJ)
      • Priority: High, To be done for the end of August.
      • Requested for the PERT (highly required feature) and for the LHC support package we are preparing.
    • BWCTL plug in (Erlangen)
      • priority: high. Provided ASAP
      • Needed to be used by NOC during the pilot.
    • BWCTL plug-in history (Erlangen)
      • priority: Medium
      • Provide historical information about the BWCTL tests and improved visualisation.
  • L2 status + E2Emon (LRZ - JRA4)
    • To be released as soon as possible, so that the Service Desk can start supporting it.
  • Hades getting ready for LHC support (Erlangen)
    • Priority: high - release in October
    • Inter-operable with OWAMP, hades as a released SW package (probe installation, scheduler, MA), share a scheduler with OWAMP
  • BWCTL getting ready for LHC support (Erlangen - tbc)
    • Priority: High (release in September - tbc)
    • Scheduler and MA available
  • TCMP (UJ) - Test environment for the PERT
    • Priority: High, early August.
    • The PERT is interrested to get access to file captures from within the backbone. This aims at giving the PERT and access to the tool and to a test machine.
[edit]

perfSONAR vx.y

The services to include in perfSONAR vx.y (planned for end of 2007/early 2008 ) in addition to the existing ones are:

  • Multi-LS (*)
  • RRD MA Service (*)
    • Improved performance
  • SQL MA Service (*)
  • E2EMon MP (?)
  • Telnet/ssh MP (*)
  • Authentication Service ( the (*) services/visualisation must be using the authentication service, (?) are unknown)
  • BWCTL MP (*)
  • perfSONAR UI (*)
  • DFN-CNM (*)
  • E2EMon Visualisation (?)
  • CL-MP (?)
  • All the services will be made available through regular distribution
    • Priority: High as the current installation depends on too many dependencies.
  • Performances improvements on all the services and visualisation is required (feedback from the training).

The code must be delivered at the end of October for release purpose.

[edit]

References

[edit]

Contact

  • Jeff W. Boote, email: boote@internet2.edu
  • Luís Marta, email: lmarta@fccn.pt
[edit]

Work in progress

The release management team is collecting all the bugs and other issues that the users comunities communicate, and working with the developers on trying to solve them. The documentation of the next release and the fixed bugs list are being updated accordingly.

Retrieved from "http://wiki.perfsonar.net/jra1-wiki/index.php/Release_Management"
Personal tools