September 2, 2009
This article was contributed by Nathan Willis
A group of SUSE Linux users put plans in motion last week to create a
free, community-managed server distribution that maintains compatibility
with Novell's enterprise offerings, but guarantees the long-term-support
not provided by openSUSE. The
result, said organizers, would be similar to the relationship between CentOS and Red Hat Enterprise Linux (RHEL), and
would ultimately be beneficial to Novell. There are numerous practical
difficulties to be overcome in the creation of this distribution, though,
and the form that this distribution might take is not yet clear.
The idea of a free SUSE-based Linux distribution suitable for server use
has cropped up more than once in the past; what spurred action this time
was the August 14th announcement
that openSUSE was moving from a 24-month to an 18-month maintenance period.
Boyd Lynn Gerber, a consultant who works with the SUSE Linux Enterprise
Server (SLES) and Desktop (SLED) products
and participates in the openSUSE project, voiced concern
over the change, especially for small-to-medium sized businesses (SMBs)
without the financial resources to purchase SLES and SLED support contracts
(which start at $799 and $120 per year, respectively). For comparison,
SLES and SLED receive
general updates for five years, and security patches for seven.
Gerber argued that shortening the supported lifespan of openSUSE widened
the gap in the product line between openSUSE and SLES/SLED, potentially
making it hard for small businesses to smoothly transition into the
enterprise line. He proposed starting a group to work on a distribution in
between openSUSE and SLES/SLED — one that would be available without
purchasing a support contract from Novell, but would offer a longer,
multi-year lifespan with which businesses would be comfortable, in
particular guaranteeing backports for critical patches and security
fixes.
Multiple options
Gerber's initial plan suggested three possible courses of action: create
a support structure to maintain openSUSE backports for a longer period of
time (a.k.a. the "OpenSUSE LTS" option), create a new distribution built
from the source code releases of SLES but with Novell's trademarks removed
(the "OpenSLES" option), or create a new distribution using the latter
model, but for SLED instead of SLES (the "OpenSLED" option). The
subsequent discussion on the opensuse-project
mailing list debated the merits of each alternative, but the level of
response also led Gerber to start a separate mailing
list on which to further pursue the idea.
The OpenSLED option was quickly dismissed, because the product would be
too similar to openSUSE itself, and because SLED does not include any
server-oriented packages, so it would do little to meet additional needs
for SMBs. Between the OpenSUSE LTS and OpenSLES options, opinion on the
new list was evenly split. The pros of OpenSUSE LTS include the relative
legal simplicity — creating a derivative of openSUSE does not require
permission or even cooperation from Novell — but the cons include
significantly higher investment of volunteer time. openSUSE contains more
packages than either SLES or SLED, so more patches and backports would be
required to maintain it over time.
Furthermore, adding LTS to openSUSE would require creating a framework
for triaging, testing, and approving updates and backports well after an
openSUSE release's end-of-life, whereas mimicking SLES's lifespan for an
OpenSLES distribution could rely on Novell's tested patches. The down side
of running an OpenSLES distribution, according to list traffic, is the risk
of alienating or angering Novell if the company perceives the effort as
siphoning away SLES customers. Gerber and others countered that an
OpenSLES would, in reality, attract more customers to SLES by
providing a lower barrier to entry, particularly for SMBs.
Supporters of the OpenSLES option compare it to CentOS, which they
describe as a popular choice among SMBs either with smaller budgets or
merely testing the waters before signing up for enterprise support with
RHEL. CentOS, the "Community ENTerprise Operating System" is
volunteer-driven, and since 2003 has built
its releases from Red Hat's publicly available RHEL source code packages,
with Red Hat's trademarks and branding excised. RHEL, like SLES and SLED,
has a seven-year support life cycle.
Progress
Thus far, said Gerber, Novell has given the idea a chilly public
reception, although he claims that in private conversation members of
Novell management have been more open and expressed the view that an
OpenSLES could be a tool to gain more SLES customers. "We will need
to show or demonstrate to Novell and their upper management that this a
good thing to support," he said.
Gerber believes that the OpenSLES option is clearly better than the
OpenSUSE LTS option, and has started planning, laying down the groundwork
for a non-profit entity to oversee the project, creating initial project
guidelines based on the examples provided by CentOS and other derivative
distributions, and looking for legal representation to assist with
licensing and trademark usage concerns. Just a handful of people
participated in the discussion on opensuse-project, but a dozen or so have
already joined the new mailing list, and Gerber said the discussion is
ongoing in the #opensuse-server IRC channel on Freenode.
Novell did not respond to requests for comment about the project,
although SLES manager Gerald Pfeifer did ask
several questions about the proposal on the opensuse-project list,
particularly about the suggestion that Novell was not properly serving the
SMB market.
Although SUSE Linux does not have an ecosystem of derivative
distributions like those surrounding Red Hat's products or Debian, there
does not appear to be anything preventing such spin-offs from starting up.
openSUSE has detailed trademark
guidelines [PDF] explicitly covering redistribution and modification
projects. SLES and SLED are not covered by that set of guidelines, but
Novell has a trademark usage request system
through which interested parties can ask for trademark usage approval on a
case-by-case basis. As for the software itself, openSUSE is of course a
fully open project, and Novell provides source code
packages for SLES and SLED on its web site.
Clearly SUSE users and resellers are interested in the possibility of a
free alternative to Novell's current enterprise offerings. There are no
hard numbers to back up the position that CentOS has directly increased Red
Hat's sales of RHEL, but the company certainly tolerates its existence, and
CentOS as well several other highly-focused RHEL
derivatives like Scientific
Linux have continued to thrive. Proposals to build a long-term-support
option for existing distributions are no guarantee of success; several
efforts to add that support to
Fedora have come and gone in recent years. If it is successful,
creating an OpenSLES may be the first step not only towards filling the
long-term-support gap, but to expanding the SUSE-based distribution
family.
(
Log in to post comments)