My Favorites

Close

Please to see your favorites.


Software repositories for building images on SUSE Linux Point of Service 11 Service Pack 2

This document (7006649) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Point of Service Service Pack 2

Situation

Since SUSE Linux Point of Service 11 Service Pack 2, the Subsciption Management Tool (SMT) is used to make the necessary repositories available.
In addition to that,  with the release of SUSE Linux Enterprise Server 11 Service Pack 2, a new  maintenance model has been introduced.

Resolution

To build SUSE Linux Point of Service 11 Service Pack 2 images, which has including all maintenance patches, the following repositories are needed:

SLES11-SP1-Pool
SLES11-SP2-Core
SLES11-SP1-Updates
SLES11-SP2-Updates
SLE11-POS-SP2-Pool
SLE11-POS-SP2-Updates
repo (local repository)
After an update to Service Pack 2, the already built images with Service Pack 1 or earlier, have to be adjusted according the new maintenance model above.

To build a new image based on minimal, graphical or branchserver, the repositories are already included as local SMT server paths. This information is stored in the image templates and here is normaly no additional action needed.

However, if an external SMT server is used, the path has to be changed from:

/srv/www/htdocs/repo/$RCE/*
to
http://server.name/repo/$RCE/*

The image templates can be found at:
 /usr/share/kiwi/image/SLEPOS/branchserver-3.4.0/
 /usr/share/kiwi/image/SLEPOS/graphical-3.4.0/
 /usr/share/kiwi/image/SLEPOS/minimal-3.4.0/

All paths for the repositories are stored in the kiwi description file (config.xml).

To avoid overwriting these files by one of the next update, it is recommened to
make you own copy of the template first. This can be done with the following steps on a root terminal:

Suppose you want to copy the graphical templates to a new one called mygraphical:

1. Go to the template directory:
# cd /usr/share/kiwi/image/SLEPOS/
2. Do a copy of the template:
# cp -a graphical-3.4.0/ mygraphical-3.4.0/
3. Create the symlink:
# ln -s mygraphical-3.4.0 mygraphical-3
4. Change the name of the template to the new one:
To do this, open mygraphical-3.4.0/config.xml and search for the line (should be the second line):
<image schemeversion="2.4" name="graphical">
and change it to:
<image schemeversion="2.4" name="mygraphical">
5. Change the repos to the external SMT server:
Suppose the name of the SMT server is „http://server.org“ change following section of the same file from:
[...]
<!--   SLE POOL REPOSITORY -->
        <repository type="rpm-md">
                <source path="/srv/www/htdocs/repo/$RCE/SLES11-SP1-Pool/sle-11-i586"/>
        </repository>
<!--   SLE CORE REPOSITORY -->
        <repository type="rpm-md">
                <source path="/srv/www/htdocs/repo/$RCE/SLES11-SP2-Core/sle-11-i586"/>
        </repository>
<!--   SLE UPDATES REPOSITORY -->
        <repository type="rpm-md">
                <source path="/srv/www/htdocs/repo/$RCE/SLES11-SP1-Updates/sle-11-i586"/>
        </repository>
        <repository type="rpm-md">
                <source path="/srv/www/htdocs/repo/$RCE/SLES11-SP2-Updates/sle-11-i586"/>
        </repository>
<!--   SLEPOS REPOSITORY -->
        <repository type="rpm-md">
                <source path="/srv/www/htdocs/repo/$RCE/SLE11-POS-SP2-Pool/sle-11-i586"/>
        </repository>
<!--   SLEPOS UPDATES REPOSITORY -->
        <repository type="rpm-md">
                <source path="/srv/www/htdocs/repo/$RCE/SLE11-POS-SP2-Updates/sle-11-i586"/>
        </repository>
<!--    CUSTOM REPOSITORY -->
       <repository type="rpm-dir">
                <source path="this://repo"/>
        </repository>
[...]

to:  

[...]
<!--   SLE POOL REPOSITORY -->
        <repository type="rpm-md">
                <source path="http://server.org/repo/$RCE/SLES11-SP1-Pool/sle-11-i586"/>
        </repository>
<!--   SLE CORE REPOSITORY -->
        <repository type="rpm-md">
                <source path="http://server.org/repo/$RCE/SLES11-SP2-Core/sle-11-i586"/>
        </repository>
<!--   SLE UPDATES REPOSITORY -->
        <repository type="rpm-md">
                <source path="http://server.org/repo/$RCE/SLES11-SP1-Updates/sle-11-i586"/>
        </repository>
        <repository type="rpm-md">
                <source path="http://server.org/repo/$RCE/SLES11-SP2-Updates/sle-11-i586"/>
        </repository>
<!--   SLEPOS REPOSITORY -->
        <repository type="rpm-md">
                <source path="http://server.org/repo/$RCE/SLE11-POS-SP2-Pool/sle-11-i586"/>
        </repository>
<!--   SLEPOS UPDATES REPOSITORY -->
        <repository type="rpm-md">
                <source path="http://server.org/repo/$RCE/SLE11-POS-SP2-Updates/sle-11-i586"/>
        </repository>
<!--    CUSTOM REPOSITORY -->
        <repository type="rpm-dir">
               <source path="this://repo"/>
        </repository>
[...]

Additional Information

The following Technical Information Document describes the new maintenance model in detail:
TID 7010225  Software repositories in SUSE Linux Enterprise 11 Service Pack 2


Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7006649
  • Creation Date:08-MAY-12
  • Modified Date:04-DEC-12
    • SUSESUSE Linux Enterprise Point of Service

Did this document solve your problem? Provide Feedback