Sliding Back the Support Scale
The amount of time a given release of a Linux distribution is supported is of paramount interest to its users. After all, large-scale deployments depend on stability, and stability means support. Some users of openSUSE are liable to be feeling a bit shaken this week, after the project announced that the support period for its releases has been cut by a fourth.
On Tuesday, SUSE Security Team Lead Marcus Meissner posted an end-of-life notice to the opensuse-announce mailing list, announcing that updates for openSUSE 10.3 updates would be discontinued after October 31, 2009, just over two months from now. Meissner wrote that, having supported the release for two years, the support period had run its course, and that discontinuing support would allow developers to focus on newer releases, providing the level of quality users have come to expect. The email also included an end-of-life schedule for the 11.0 and 11.1 releases, as well as for the current development version, 11.2. It was this last item that raised concerns, as it read:
openSUSE 11.2 (currently in development, to be released November 12th 2009) for the next two openSUSE releases plus two months overlap period.
openSUSE releases occur every eight months, so two releases plus two months works out to eighteen months — six months less than the current twenty-four months, a twenty-five percent reduction. While individual users experience relatively little disruption from a distribution upgrade — particularly if it only occurs every eighteen months — for enterprise users it is a significant undertaking, one requiring large amounts of time and even larger amounts of money, and the support-period can be the deciding factor between two distributions. (Even if the software is free, the man-hours to perform the upgrade are not, nor is the time lost to problems that arise, and businesses don't like to lose money.) This is the rationale behind the update schedule for Ubuntu: regular distribution releases occur every six months, with an eighteen month support cycle, but at regular intervals, a release is designated as Long Term Support or LTS, promising three years of support on the desktop, and five years on the server.
Following the announcement, Novell's Michael Loeffler posted a follow-up to clarify the change. Loeffler wrote:
with regards to the discontinuation mail for openSUSE 10.3  sent out by
Marcus the other day I'd like to clarify the changes in the maintenance period
openSUSE will shorten the maintenance period to 2 versions plus 2 months
which translates with the current release cycle of 8 months to 18 months
instead of 24 months we had with openSUSE 11.1 and previous releases.
With that we now can guarantee an overlap time from a maintenance perspective
which gives enough time to update machines to newer versions.
How users will ultimately respond to the change, and how it will affect enterprise deployment of openSUSE remains to be seen, as it has been just three days since the announcement. What is most certain, however, is that it will receive thorough and spirited discussion — that is, after all, a hallmark and one of the great strengths of Open Source.
Justin Ryan is a Contributing Editor for Linux Journal.
|Speed Up Your Web Site with Varnish||Jun 19, 2013|
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Linux Systems Administrator
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Validate an E-Mail Address with PHP, the Right Way
- Technical Support Rep
- Senior Perl Developer
- UX Designer
- Introduction to MapReduce with Hadoop on Linux
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?