Newsletters Subscriptions Forums Store Career Media Kit About Us Contact Search Home

BREAKING NEWS
News While It's Still Hot
August 15, 2005

Novell Opens Up Development for SUSE Linux


by Timothy Prickett Morgan


While you could always get your hands on the source code behind SUSE Linux Professional version of the Linux operating system, the process that commercial Linux distributor Novell went through to create that bleeding-edge Linux was completely closed off. As expected, Novell last week said that it would be opening up the process whereby it develops its desktop and server implementations of the Linux platform through the establishment of the openSUSE project.

The project, which is located at www.opensuse.org, was announced at the LinuxWorld trade show in San Francisco, and openSUSE performs the same function for Novell as Red Hat's Fedora Project does for that rival of Novell's. It will get new features in front of die-hard Linux users and will eventually allow community development of the software that will be put into future enterprise Linux releases.

The rumor before the announcement was that Novell would put the beta version of the future SUSE Professional 10.0 source code, code-named "Prague," out there on the openSUSE site. Novell did more than this, in fact, and it released all of the source code for the current SUSE Linux Professional 9.3 as well as the code for the SUSE Professional 10.0 beta. Just like the Fedora Project is how Red Hat collects and integrates future Linux and related open source projects together to allow developers to create and ambitious beta testers to test its future Linux releases, Novell has used SUSE Linux Professional to give its customers and partners a snapshot every six months or so of the features that it has working in its Linux implementation.

According to David Patrick, vice president and general manager of Linux, open source platforms, and services at Novell, the advent of the openSUSE project is due to two factors. First, customers and partners wanted to have earlier access to beta code so they could play with it; second, some customers and partners wanted to actually have a say in the SUSE Linux roadmap and some even wanted to contribute code and help out. So the openSUSE project was created to facilitate this, and he was obviously not keen on admitting the similarities to the Fedora Project over at rival Red Hat. "We are opening up the front end of the product," Patrick explained. "This is about bringing outside developers earlier into the development process."

So why now instead of two years ago, when Novell acquired SUSE and bought its way into the Linux business? (And for the second time, if you count Ray Noorda's investment in Caldera Systems, now known as the SCO Group.) Patrick said that Novell believes that it has created the best and most-integrated version of a commercial Linux platform, and that it took two years for Novell to perfect its own internal processes for making sure the development process behind SUSE Linux worked properly. But if SUSE wants to make money, the company knows that it needs to make its entry Linux free and easy to get, just like Fedora Core releases are over at Red Hat. "You're going to see us get a lot more aggressive about getting SUSE Linux into people's hands," he said. "I think we need to work on the commodity part of the market--edge servers, the LAMP stack, and so forth. In the enterprise space, we are very happy with the momentum we have in the market."

To boost the installed base of any open source program that has fee-based services, software makers can trade beta testing services from enthusiasts in exchange for free but limited support and easy access to the open source code behind the full product. Like Red Hat with Fedora and Sun Microsystems with its open source OpenSolaris and freeware Solaris 10 downloads, Novell is gambling that it can quickly build a vast installed base of enthusiasts who would not pay for SUSE Linux Professional and who do not want to root around on the Novell site get find source code and bug fixes. The easier and quicker it is to get a Linux distribution, the more downloads Red Hat and Novell can get. And the enthusiasts who download the software end up recommending that brand of Linux at their companies or buying commercialized versions with full support when the situation demands it.


"Two years ago, the goal was to create the best Linux on multiple platforms," explained Patrick at the announcement of openSUSE at the LinuxWorld show last Tuesday after The Linux Beacon went to press. "At the time, we felt we needed a significant amount of control over the process for the sake of quality."

Novell has created a concurrent versions system repository called AutoBuild to manage the process of culling updates to the thousands of open source projects that are embodied in the SUSE Linux distribution. The package maintainers who work at Novell have been using AutoBuild to select code from the projects out there in the ether and deciding what goes into each SUSE Professional release; after a new feature and the code behind it makes it into SUSE Professional and is released commercially, it is tweaked, tested, and extended up to the SUSE Linux Enterprise Server edition and pushed down into the Novell Linux Desktop edition. The big change with openSUSE is that the package maintainers at Novell will be in contact with the openSUSE community, who will be submitting bug reports and fixes as well as suggestions for what should be included. The community will also have access to full roadmaps and a say in what goes in them, said Patrick. What they will not get immediately, however, is access to the AutoBuild system.

The openSUSE release does not replace SUSE Linux, which is the new name for what used to be called SUSE Linux Professional. Rather, openSUSE is the process by which SUSE Linux--the core code that eventually goes into servers and simple desktops but which is always released for regular desktops and laptops first--is going to be created. In order for the openSUSE community to get up to speed on where Novell is and where it is going, it only makes sense that the production code behind SUSE Professional 9.3 and the beta code behind SUSE 10 would both be released at the openSUSE site. The SUSE 10.0 beta software includes Novell's AppArmor security, an improved desktop search function, Xen virtualization, and updates to the Mono and Eclipse development tools.

According to the roadmap at the openSUSE site, SUSE Linux 10.0 beta 1 is released on August 9, with beta 2 coming out on August 18, beta 3 on August 25, and beta 4 on September 1. SUSE 10.0 Release Candidate 1 will come out on September 9, and then on September 28, the openSUSE community will start the whole process over again with alpha releases of SUSE Linux 10.1. Novell will port the SUSE Support Database to the openSUSE wiki in September, and sometime in early 2006 community members will be provided access to the AutoBuild system, allow them to participate in the build process. Patrick said that Novell would deliver in production-quality releases from Novell in 2006 in its Novell Linux Desktop, SUSE Linux, and SUSE Linux Enterprise Server implementations.

Sponsored By
LINUX NETWORX

Clusterworx® Whitepaper

High performance Linux clusters can consist of hundreds or thousands of individual components. Knowing the status of each CPU, memory, disk, fan, and other components is critical to ensure the system is running safely and effectively.

Likewise, managing the software components of a cluster can be difficult and time consuming for even the most seasoned administrator. Making sure each host's software stack is up to date and operating efficiently can consume much of an administrator's time. Reducing this time frees up system administrators to perform other tasks.

Though Linux clusters are robust and designed to provide good uptime, occasionally conditions lead to critical, unplanned downtime. Unnecessary downtime of a production cluster can delay a product's time to market or hinder critical research.

    Since most organizations can't afford these delays, it's important that a Linux cluster comes with a robust cluster monitoring tool that:
  • Provides essential monitoring data to make sure the system is operational.
  • Eliminates repetitive installation and configuration tasks to reduce
          periods of downtime.
  • Provides powerful features, but doesn't compromise on usability.
  • Automates problem discovery and recovery on would-be critical events.

This paper discusses the features and functions of Clusterworx® 3.2. It details how Clusterworx® provides the necessary power and flexibility to monitor over 120 system components from a single point of control. The paper also discusses how Clusterworx® reduces the time and resources spent administering the system by improving software maintenance procedures and automating repetitive tasks.

High Performance Monitoring

Each cluster node has its own processor, memory, disk, and network that need to be independently monitored. This means individual cluster systems can consist of hundreds or thousands of different components. The ability to monitor the status and performance of all system components in real time is critical to understanding the health of a system and to ensure it's running as efficiently as possible.

Because so many system components need to be monitored, one of the challenges of cluster management is to efficiently collect data and display system health status in an understandable format. For example, let's say a cluster system has 100 nodes and is running at 97 percent usage. It's very important to know whether 100 nodes are running at 97 percent usage or whether 97 nodes are running at 100 percent usage while three nodes are down.

Clusterworx® provides real-time analysis of over 120 essential system metrics from each node. Data is displayed in easy-to-read graphs, thumbnails, and value tables. Clusterworx® collects data from groups of nodes to spot anomalies, then drills down to single node view to investigate problems. This allows users to determine exactly what the problem is before taking corrective action.

Clusterworx® also tracks the power and health state of each node and displays its status using visual markers in a node tree view throughout the user interface. Power status shows whether the node is on, off, provisioning, or in an unknown state. The health state tracks informational or warning messages and critical errors. Health state messages are displayed in a message queue on the interface.

Clusterworx®'s comprehensive monitoring and easy-to-read charts and graphs allow users to quickly asses the state of each node and the overall system at a glance - while providing the necessary information to make informed decisions about the cluster system.

To read the rest of this whitepaper, please visit www.linuxnetworx.com


Editors: Dan Burger, Timothy Prickett Morgan, Alex Woodie
Publisher and Advertising Director: Jenny Thomas
Advertising Sales Representative: Kim Reed
Contact the Editors: To contact anyone on the IT Jungle Team
Go to our contacts page and send us a message.

Breaking News

BREAKING NEWS
ARCHIVE



Copyright © 1996-2008 Guild Companies, Inc. All Rights Reserved.
Guild Companies, Inc. (formerly Midrange Server), 50 Park Terrace East, Suite 8F, New York, NY 10034
Privacy Statement