Difference between revisions of "SUSE Linux Enterprise Server"

From MicroFocusInternationalWiki
Jump to: navigation, search
(High-Availability Storage Foundation)
(High-Availability Storage Foundation)
Line 29: Line 29:
 
*** Feeding two order constraints into CIB with one XML file only succeeds for one order constraint
 
*** Feeding two order constraints into CIB with one XML file only succeeds for one order constraint
 
**** In the document, in the section "Ordering resource startup in the cluster", we ask you to load an XML file in the CIB which we call "vm1orderconstraints.xml". This file contains two order constraints, one for the virtual machine to the imagestore, and one for the virtual machine to the configstore. When you run the command as indicated in the document, it might be possible THAT ONLY THE FIRST CONSTRAINT IS LOADED IN THE CIB. To check this, you need to run the command "cibadmin -Ql" after having loaded the file in the CIB. Check the output, and verify that both constraints were added to the CIB. If this is not the case, you need to copy the vm1orderconstraints.xml to a second file, e.g. vm1orderconstraints_workaround.xml, remove the first line in that file, and then load this second file in the CIB with the command "cibadmin -C -o constraints -x ./vm1orderconstraints_workaround.xml. The goal is to get the second constraint loaded in the CIB. Only then should you continue the procedure as described in the document.
 
**** In the document, in the section "Ordering resource startup in the cluster", we ask you to load an XML file in the CIB which we call "vm1orderconstraints.xml". This file contains two order constraints, one for the virtual machine to the imagestore, and one for the virtual machine to the configstore. When you run the command as indicated in the document, it might be possible THAT ONLY THE FIRST CONSTRAINT IS LOADED IN THE CIB. To check this, you need to run the command "cibadmin -Ql" after having loaded the file in the CIB. Check the output, and verify that both constraints were added to the CIB. If this is not the case, you need to copy the vm1orderconstraints.xml to a second file, e.g. vm1orderconstraints_workaround.xml, remove the first line in that file, and then load this second file in the CIB with the command "cibadmin -C -o constraints -x ./vm1orderconstraints_workaround.xml. The goal is to get the second constraint loaded in the CIB. Only then should you continue the procedure as described in the document.
 +
*** Issues when running version 2.07 of Hearbeat 2
 +
**** If you have update your Heartbeat 2 software with the patch that Novell released on August 21, then you might encounter some changes in behaviour. See http://support.novell.com/techcenter/psdb/898d4f4e7a472004cbc68e65f5a941a0.html for information on the patch.
 +
***** Configuring the demo cluster resource requires netmask and broadcast address
 +
****** When you configure the demo cluster resource, either don't specify the NIC as described in the document, or specify the nic AND the netmask (255.255.255.0) and broadcast address (192.168.0.255) for the demo cluster resource.
  
 
* Conquering the High-Availability Storage Foundation : to be released.
 
* Conquering the High-Availability Storage Foundation : to be released.

Revision as of 16:03, 5 October 2006

Welcome to the SUSE Linux Enterprise Server Wiki!!

As already mentioned on the wiki main page, please feel free to join in. You can read anything in here without logging in, but if you feel like commenting on something, or starting a new topic, you'll need to use a Novell Login account (which you'll be prompted to create if you don't already have one). If you are unfamiliar with using Wiki's in general, please visit Novell Wiki or the grandaddy wiki info site www.wiki.org for some background info.

Several areas of the Novell webspace provide information regarding the SUSE LINUX Enterprise Server (commonly abbreviated as SLES).

General SLES Information

Some general information on SLES is available at the Novell and Linux page.

SLES 10

SLES 10 is released, and can be downloaded here:

New with SLES 10 is the Novell Customer Center. See Getting to know the Novell Customer Center

High-Availability Storage Foundation

The High-Availability Storage Foundation (HASF) is a combination of several Open Source projects, plus Novell donated source code, integration tested and delivered in SLES 10. The HASF allows for the creation of a server and storage infrastructure that enables service-level availability by running individual services in cluster-managed relocatable virtual machines.

Documentation :

  • Exploring the High-Availability Storage Foundation : download here
    • Known issues regarding this document
      • Initial node2 NTP time grab might fail (leo@kangaroot.net, jdebaer@novell.com)
        • In the document we ask you to make node1 come up after node2, because node2 is running the iSCSI target. Making the nodes (re)boot in this order makes sure that node1 finds the iSCSI target on node2. However, as a result of this, node2 (NTP client) cannot grab it's initial time from node1 (NTP server). Normally this should not be a problem, since a mere reboot of both systems should not cause a large time drift. However, if the hardware clock of node2 is not ok, then node2 can come up with a time drift. When this time drift is too big, then this will cause the STONITH operation to fail when you perform the final test of killing heartbeat on node1. Solution is to run "/etc/init.d/ntp restart" on node2 right before killing the heartbeat on node1. In "Conquering the High-Availability Storage Foundation" we will probably reverse client and server to resolve this potential issue.
      • Feeding two order constraints into CIB with one XML file only succeeds for one order constraint
        • In the document, in the section "Ordering resource startup in the cluster", we ask you to load an XML file in the CIB which we call "vm1orderconstraints.xml". This file contains two order constraints, one for the virtual machine to the imagestore, and one for the virtual machine to the configstore. When you run the command as indicated in the document, it might be possible THAT ONLY THE FIRST CONSTRAINT IS LOADED IN THE CIB. To check this, you need to run the command "cibadmin -Ql" after having loaded the file in the CIB. Check the output, and verify that both constraints were added to the CIB. If this is not the case, you need to copy the vm1orderconstraints.xml to a second file, e.g. vm1orderconstraints_workaround.xml, remove the first line in that file, and then load this second file in the CIB with the command "cibadmin -C -o constraints -x ./vm1orderconstraints_workaround.xml. The goal is to get the second constraint loaded in the CIB. Only then should you continue the procedure as described in the document.
      • Issues when running version 2.07 of Hearbeat 2
        • If you have update your Heartbeat 2 software with the patch that Novell released on August 21, then you might encounter some changes in behaviour. See http://support.novell.com/techcenter/psdb/898d4f4e7a472004cbc68e65f5a941a0.html for information on the patch.
          • Configuring the demo cluster resource requires netmask and broadcast address
            • When you configure the demo cluster resource, either don't specify the NIC as described in the document, or specify the nic AND the netmask (255.255.255.0) and broadcast address (192.168.0.255) for the demo cluster resource.
  • Conquering the High-Availability Storage Foundation : to be released.
  • Linux-World demo : four-node Cluster hosting two Virtual Machines.

Add-ons

SLES 9

The current version of SLES9 is SLES9 SP3.

SLES 9 is available for a number of architectures and contains numerous packages (see the package list).

For a current installation, both the general release CDs and the current service pack CDs are needed. There are no overlay images available for SLES9.

Download SLES 9

Links to the unpatched ISOs can be found on the SLES 9 Download page.

SLES 9 Support Packs

Links to the support pack ISOs can also be found on the SLES 9 Download page.

Add-ons

Articles

  • Newicon.gif Securing SLES9 - Details some very basic actions you can take to make SLES9 even more secure.
  • Deploying SUSE Linux using autoyast: download here

SLES8

SLES8 is an older version of SLES which is still supported.

Support for SLES

There are a number of support options for SLES.

Certifications and hardware compatibility

Related products