perfSONAR 4.0 status update
Posted November 29, 2016 - permalink
The perfSONAR project wanted to give everyone an update on the progress of the progress of perfSONAR 4.0, the next major release of the software. So far we have done two release candidates and have gotten a lot of great participation in testing the new release. As you may recall from emails we have been sharing the past couple months, we estimated a final release approximately in December. Using our own testing and community feedback as input, we think that in order to provide the community with the best possible software we will be doing a third release candidate in January with the final release to follow sometime after that. As the perfSONAR project has matured we have tried to hold the software to a higher standard, and what once may have made it through the release process we now scrutinize a bit more. We will send a more detailed timeline for the months going forward a bit closer to the RC3. We appreciate your understanding and look forward to your continued assistance in testing the software.
Recent kernel CVE
Posted November 23, 2016 - permalink
A new Red Hat CVE has been released:
Our read of the CVE does not find any issue of concern specific to the toolkit. Its possible the host may be vulnerable to some types of DoS attacks in some particular cases.
New web100 kernel packages are now available for users of the perfSONAR toolkit. You may run 'yum update' to grab the new kernel. You should restart your host after the upgrade completes.
perfSONAR 4.0RC1 now available for testing
Posted October 5, 2016 - permalink
The perfSONAR team would like to invite everyone to start testing the first release candidate of perfSONAR 4.0, the next major revision of perfSONAR. This is NOT a production release and DO NOT INSTALL THIS ON PRODUCTION HOSTS. At this point in time we are seeking testers with extra machines to help try the new software in preparation for a final release later this year.
Major new changes features include:
- pScheduler: A completely new measurement scheduling system designed to replace BWCTL.
- New Graphs: New visualization of measurement data that leverage ESnet's React charting library.
- CentOS 7 support: We now have packages available for CentOS 7. We will also provide 4.0 packages for CentOS 6, so an immediate OS upgrade is not required at this time. A timeline of support for CentOS 6 will be provided in a separate message.
- MaDDash 2.0: MaDDash now supports alerts based on custom patterns thanks to work by the University of Michigan as a subproject of the PuNDIT project. It also has email notification, customizable color palettes and more.
- MeshConfig Admin GUI: A new web interface that allows you to define central meshes graphically.
- Sunsetting of Web100 and NDT: This release does not install NDT or Web100 by default. Our support plan for these tools moving forward will be covered in a note being sent out shortly.
Those are the highlights but see https://www.perfsonar.net/release-notes/version-4-0-rc1/ for more detailed release notes.
The best way to get the software depends on your operating system and installation method, so for details appropriate to your environment see: http://docs.perfsonar.net/release_candidates/4.0rc1/install_rcs.html and http://docs.perfsonar.net/release_candidates/4.0rc1/install_debian.html.
In general, updates can be done through the OS package manager with no extra steps and you can do new installs with the OS of choice's minimum install equivalent, point at our repositories and install the perfsonar-toolkit package or one of our other bundles.
Youu can install the packages on an existing CentOS 6/7 machines via yum, or a Debian/Ubuntu via apt, or download ISOs. <meta http-equiv="content-type" content="text/html; charset=utf-8">The ISOs can be downloaded here: http://downloads.perfsonar.net/toolkit/release_candidates/
Thank you ahead of time to all our testers. This is one of our larger releases in recent memory, and a lot more than can be covered in this email is included. We encourage everyone to take a look through the documentation at http://docs.perfsonar.net/release_candidates/4.0rc1, be on the look-out for further communication and to attend/watch the netcast of the perfSONAR talks at the Technology Exchange (http://www.internet2.edu/news-events/events/technology-exchange/) conference for more details.
perfSONAR Support Timeline Updates
Posted September 28, 2016 - permalink
With the pending release of perfSONAR 4.0, the following dates are being announced related to the support of perfSONAR:
- September 2016:
- perfSONAR 4.0 RC1 released
- October 2016:
- perfSONAR 4.0 RC2 released
- November 2016:
- perfSONAR 4.0 final released
- May 2017:
- perfSONAR 3.5.1 end-of-life
- No longer providing new web100 builds
- No longer providing NDT with perfSONAR
- November 2017:
- perfSONAR 4.1 released, will not be available for CentOS 6
- BWCTL support dropped
- May 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.
- It also means you have 18 months 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 will be providing tools to copy configuration and data from CentOS 6 to CentOS 7 to help with the transition.
- Currently there are no plans to change supported Debian versions, but that may change. We will update the timeline appropriately if it does, and give everyone ample notification.
- 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.