Difference between revisions of "SUSE Manager/SLES 10 Betatest"

From MicroFocusInternationalWiki
Jump to: navigation, search
(Created page with "= Instructions how to enable Code10 support on SUSE Manager = Following these instructions will allow you to manage SLES10 (SP3 and SP4) clients with SUSE Manager = !! Attentio...")
 
 
(3 intermediate revisions by one other user not shown)
Line 14: Line 14:
 
== Prerequisites ==
 
== Prerequisites ==
  
# A fully updated SUSE Manager Server
+
* A fully updated SUSE Manager Server
## spacewalk-service stop
+
  spacewalk-service stop
## zypper ref
+
  zypper ref
## zypper up
+
  zypper up
  
# Make sure you have plenty of disk space, the SLES10 channels are huge (~10GB)
+
* Make sure you have plenty of disk space, the SLES10 channels are huge (~10GB)
  
 
== Detailed steps (Server side) ==
 
== Detailed steps (Server side) ==
 
 
2. Add the repo with latest SUSE Manager packages
 
  - zypper ar http://beta.suse.com/private/SUSE-Manager-Code10/Beta1/Server beta1
 
  - zypper ref beta1
 
  
3. Allow vendor change to openSUSE Build Service
+
=== Update to Code10-Beta1 ===
  - mkdir /etc/zypp/vendors.d
+
  - cat <<EOF > /etc/zypp/vendors.d/suse-manager
+
[main]
+
vendors = suse,openSUSE,openSUSE Build Service
+
EOF
+
  
4. Update Server to Beta1  
+
* Add the repo with Beta1 SUSE Manager packages
   - zypper up
+
   zypper ar http://beta.suse.com/private/SUSE-Manager-Code10/Beta1/Server beta1
 
+
   zypper ref beta1
5. Install SLES 10 SPx client repos
+
  - zypper in spacewalk-client-repository-sle-10-4
+
   - zypper in spacewalk-client-repository-sle-10-3
+
  - zypper in spacewalk-client-repository-sle-10-2
+
  
5. Upgrade the DB schema
+
* Allow vendor change to openSUSE Build Service
  - /etc/init.d/oracle-xe start
+
** (The packages are not yet signed with the SUSE key, this will follow in Beta2)
   - spacewalk-schema-upgrade
+
  mkdir /etc/zypp/vendors.d
 +
  cat <<EOF > /etc/zypp/vendors.d/suse-manager
 +
  [main]
 +
  vendors = suse,openSUSE,openSUSE Build Service
 +
  EOF
 +
 
 +
* Update Server to Code10-Beta1
 +
  zypper up
 +
 
 +
* Upgrade the database schema
 +
** this will add sles-10 and sled-10 to the list of allowed client operating systems
 +
  /etc/init.d/oracle-xe start
 +
   spacewalk-schema-upgrade
 
    
 
    
6. Restart the Server
+
* Restart the SUSE Manager Server
   - spacewalk-service start
+
   spacewalk-service start
 
+
7. Re-generate bootstrap.sh (with Code10 support)
+
  - Navigate to Admin -> SUSE Manager Configuration -> Bootstrap Script
+
  - Click on 'Update'
+
  
8. Add SLES 10 channels
+
=== Provide a minimal set of client packages on the server ===
  - ssh to the server
+
  - Update the channel configuration
+
    - mgr-ncc-sync
+
  - Verify that sles10-sp{3,4}-pool-* and sles10-sp{3,4}-updates-* are listed
+
    - mgr-ncc-sync -l
+
  - Add the SLES 10 channel you need
+
    - mgr-ncc-sync -c sles10-sp4-pool-x86_64
+
    - mgr-ncc-sync -c sles10-sp4-updates-x86_64
+
  
9. Add SLES 10 Client Tools
+
* During bootstrap, the client will retrieve a minimal set of packages directly from the server
  - Navigate to Channels -> Manage Software Channels -> Manage Repositories
+
** This set is installed via a "spacewalk-client-repository-*" package on the server side
  - click on 'create new repository'
+
** Run these commands on the server:
  - create sles-10-sp4-clienttools from
+
   zypper in spacewalk-client-repository-sle-10-4
    http://beta.suse.com/private/SUSE-Manager-Code10/Beta1/SLES-10-SP4-SUSE-Manager-Tools
+
   zypper in spacewalk-client-repository-sle-10-3
   - create sles-10-sp3-clienttools from
+
    http://beta.suse.com/private/SUSE-Manager-Code10/Beta1/SLES-10-SP3-SUSE-Manager-Tools
+
   - Navigate to Channels -> Manage Software Channels
+
  - click on 'create new channel'
+
  - create SLES 10 SP4 Tools, assign it to the correct parent
+
  - add the respective repository ('Respositories') and sync it
+
  
10. Create activation keys
+
=== Re-generate bootstrap.sh (with Code10 support) ===
  - assign Pool, Updates, and Tools channel
+
* Navigate to Admin -> SUSE Manager Configuration -> Bootstrap Script
 +
* Click on 'Update'
  
 +
You can either edit this file on the server or on the client (see below).
  
Client
+
 
 +
=== Sync the SLES 10 channels from NCC ===
 +
 
 +
* ssh to the server
 +
* Update the channel configuration
 +
  mgr-ncc-sync -s
 +
* Verify that sles10-sp{3,4}-pool-* and sles10-sp{3,4}-updates-* are listed
 +
  mgr-ncc-sync -l
 +
* Add the SLES 10 channel you need
 +
  mgr-ncc-sync -c sles10-sp4-pool-x86_64
 +
  mgr-ncc-sync -c sles10-sp4-updates-x86_64
 +
 
 +
 
 +
* Add SLES 10 Client Tools
 +
Pool and Update are already on NCC, the Client Tools channel not yet
 +
** Add repositories
 +
*** Navigate to Channels -> Manage Software Channels -> Manage Repositories
 +
*** click on 'create new repository'
 +
*** create sles-10-sp4-clienttools from http://beta.suse.com/private/SUSE-Manager-Code10/Beta1/SLES-10-SP4-SUSE-Manager-Tools
 +
*** create sles-10-sp3-clienttools from http://beta.suse.com/private/SUSE-Manager-Code10/Beta1/SLES-10-SP3-SUSE-Manager-Tools
 +
** Add channels
 +
*** Navigate to Channels -> Manage Software Channels
 +
*** click on 'create new channel'
 +
*** create SLES 10 SP4 Tools, assign it to the correct parent
 +
** Assign repositories to channels
 +
*** Go to channel details (thats what you see immediately after adding a channel)
 +
*** Follow 'Repositories'
 +
*** add the respective repository and sync it
 +
 
 +
* Create activation keys
 +
** and assign the respective Pool, Updates, and Tools channels
 +
 
 +
 
 +
== Client side ==
  
 
Supported is SLES 10 SP3 and SP4
 
Supported is SLES 10 SP3 and SP4
  
Register the client
+
* download bootstrap.sh
  - download bootstrap.sh
+
* edit bootstrap.sh
  - edit bootstrap.sh, fill in activation key
+
** remove the 'exit 1' line
  - run bootstrap.sh
+
** fill in activation key
 +
* run bootstrap.sh
 +
 
 +
= FAQ =
 +
 
 +
* Q: bootstrap fails with 'spacewalk-check not found'
 +
* A: install the respective 'spacewalk-client-repository-sle-10-{3,4}' package on the server (see above)

Latest revision as of 20:59, 16 August 2011

Instructions how to enable Code10 support on SUSE Manager

Following these instructions will allow you to manage SLES10 (SP3 and SP4) clients with SUSE Manager

!! Attention - this is part of a closed beta test

!! Do NOT try this on a production system

Quick outline

The majority of steps is around adding SLES 10 repositories and channels on the server side.

Client management (registering it with the SUSE Manager Server, etc.) is supposed to be identical to SLES 11 based clients.

Prerequisites

  • A fully updated SUSE Manager Server
 spacewalk-service stop
 zypper ref
 zypper up
  • Make sure you have plenty of disk space, the SLES10 channels are huge (~10GB)

Detailed steps (Server side)

Update to Code10-Beta1

  • Add the repo with Beta1 SUSE Manager packages
 zypper ar http://beta.suse.com/private/SUSE-Manager-Code10/Beta1/Server beta1
 zypper ref beta1
  • Allow vendor change to openSUSE Build Service
    • (The packages are not yet signed with the SUSE key, this will follow in Beta2)
 mkdir /etc/zypp/vendors.d
 cat <<EOF > /etc/zypp/vendors.d/suse-manager
 [main]
 vendors = suse,openSUSE,openSUSE Build Service
 EOF
  • Update Server to Code10-Beta1
 zypper up
  • Upgrade the database schema
    • this will add sles-10 and sled-10 to the list of allowed client operating systems
 /etc/init.d/oracle-xe start
 spacewalk-schema-upgrade
 
  • Restart the SUSE Manager Server
 spacewalk-service start

Provide a minimal set of client packages on the server

  • During bootstrap, the client will retrieve a minimal set of packages directly from the server
    • This set is installed via a "spacewalk-client-repository-*" package on the server side
    • Run these commands on the server:
 zypper in spacewalk-client-repository-sle-10-4
 zypper in spacewalk-client-repository-sle-10-3

Re-generate bootstrap.sh (with Code10 support)

  • Navigate to Admin -> SUSE Manager Configuration -> Bootstrap Script
  • Click on 'Update'

You can either edit this file on the server or on the client (see below).


Sync the SLES 10 channels from NCC

  • ssh to the server
  • Update the channel configuration
 mgr-ncc-sync -s
  • Verify that sles10-sp{3,4}-pool-* and sles10-sp{3,4}-updates-* are listed
 mgr-ncc-sync -l
  • Add the SLES 10 channel you need
 mgr-ncc-sync -c sles10-sp4-pool-x86_64
 mgr-ncc-sync -c sles10-sp4-updates-x86_64


  • Add SLES 10 Client Tools

Pool and Update are already on NCC, the Client Tools channel not yet

  • Create activation keys
    • and assign the respective Pool, Updates, and Tools channels


Client side

Supported is SLES 10 SP3 and SP4

  • download bootstrap.sh
  • edit bootstrap.sh
    • remove the 'exit 1' line
    • fill in activation key
  • run bootstrap.sh

FAQ

  • Q: bootstrap fails with 'spacewalk-check not found'
  • A: install the respective 'spacewalk-client-repository-sle-10-{3,4}' package on the server (see above)