Project roadmap

perfSONAR Roadmap Process

The perfSONAR project roadmap is revised semi-annually based on feedback from project leaders and key community stakeholders.  The living version of this document can be found on the project wiki.

Development Timeline

A 4-phase development timeline will be employed, with overlapping development timelines between alpha and final releases:

  • 4.0 Release Candidate 1: September 29, 2016 (Coincident with the 2016 Internet2 Technology Exchange)
  • 4.0 Release Candidate 2: November, 2016
  • 4.0 Release Candidate 3: March, 2017
  • 4.0 Final: April, 2017
  • 4.0.x:  Released as needed
  • 4.1 Release Candidate 1: Fall, 2017 (Coincident with the 2017 Internet2 Technology Exchange)
  • 4.1 Release Candidate 2: Fall, 2017 (TBD)
  • 4.1 Final: January, 2018 (TBD)

Release 4.0

Release 4.0 includes:

  • pScheduler, a successor to BWCTL, featuring:
    • Full-reatured repeating tests
    • A new, more-powerful limit system
    • Insight into the testing schedule
    • Extensibiilty for new types of measurements, test tools and ways to archive results
  • Graphical display enhancements
  • GUI to facilitate testing coordination
  • Enhanced ability to select testing endpoints by criteria (capability, location, etc.)
  • Improved alerting technology for dashboard applications
  • CentOS 7  / Debian 8 Support

Coincident with this release, we will develop a detailed proposal for Release 4.1.

Legacy Release Support Schedule

With the pending release of perfSONAR 4.0, the following dates are being announced related to the support of perfSONAR:

  • Summer 2017: 
    • perfSONAR 3.5.1 end-of-life
    • No longer providing new web100 builds
  • Winter 2018:
    • perfSONAR 4.1 released, will not be available for CentOS 6
    • BWCTL support dropped
  • Summer 2018: 
    • perfSONAR 4.0 end-of-life
    • CentOS 6 support officially dropped

A few takeaways from the above timeline:

  • The current timeline gives roughly 6 months to update to 4.0 if you want to stay on a supported version. Auto-updates will be an option for going to 4.0, meaning that for most known deployments you should get the new version within a day or two of the final release later this fall. 
  • You need to make plans to migrate from CentOS 6 to CentOS 7 if you want to stay on a supported platform. This can NOT be done by auto-update, and requires a new install of CentOS 7. We provide tools to copy configuration and data from CentOS 6 to CentOS 7 to help with the transition.
  • We are dropping web100 support 6 months after 4.0 is released. This is something that has been contemplated for awhile now and the fact that there is no web100 patch for series 3 kernels, like that on CentOS 7, makes this a good time to make that transition.  We will not be including NDT on the toolkit or other perfSONAR bundles anymore since it requires web100. We do not make this decision lightly, and have used the results of user surveys and community discussions to help guide these two choices.