Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
Applies to SUSE Linux Enterprise Server 15 SP1

2 Migrate from SMT to RMT Edit source

This chapter describes the migration from SMT on SLES 11 or 12 to RMT on SLES 15.

2.1 Important Notes Edit source

Warning
Warning: Read This Section Carefully

Carefully read this section. It contains vital information about the migration process.

Use New Host

We recommend that you install RMT on a newly-installed SLES 15 host. RMT is not a complete replacement for SMT. It has a different workflow than SMT and only supports registering SUSE Linux Enterprise Server 12 systems and newer.

Repository Metadata and Settings

The settings of staged repositories will not be exported from SMT. Repositories that have been marked to be mirrored will be exported.

Custom Repositories

It's only possible to export repositories that are marked for mirroring.

Expired Subscriptions

Products no longer available on the organization subscriptions will not be available on RMT.

Client Information

Systems and their activated products will be exported. SMT client jobs and patch status will not be exported from SMT.

Table 2.1: Feature Comparison

Feature

SMT

RMT

Available on SLES 11

yes

no

Available on SLES 12

yes

no

Available on SLES 15

no

yes

Synchronize products with SUSE Customer Center

yes

yes

Mirror RPMs from repositories

yes

yes

Selective mirroring (specifying products to mirror)

yes

yes

Serve RPMs via HTTP

yes

yes

Registration of SLE 15 systems

yes

yes

Registration of SLE 12 systems

yes

yes

Registration of SLE 11 systems

yes

no

Migration from SLE 12 to 15

yes

yes

Staging repositories

yes

no1

Offline mirroring

yes

yes

NTLM Proxy support

yes

yes

Custom repositories

yes

yes

YaST installation wizard

yes

yes

YaST management wizard

yes

no

Client management

yes

no

RedHat support (Extended Support)

yes

yes

Files deduplication

yes

yes

Data transfer from SMT to RMT

n/a

yes

Transfer registration data to SUSE Customer Center

yes

no

Reporting

yes

no

Custom TLS certificates for Web server

yes

yes

Web server

Apache2

Nginx

Platform

Perl

Ruby

1) Functionality is offered by SUSE Manager.

2.2 Exporting SMT Data Edit source

Procedure 2.1: Export SMT Data
  1. Update your SMT server installation by running zypper up.

  2. If you want to export your SSL certificates along with the rest of the data, run smt-data-export. Remember to keep your certificates in a safe place.

    If you do not want to export the SSL certificates from SMT, run smt-data-export --no-ssl-export.

  3. The exported configuration is now saved to smt-export.TIMESTAMP.tar.gz. Copy the file to a location that can be accessed by the new RMT server.

2.3 Importing SMT Data to RMT Edit source

  1. To make sure your RMT installation is up to date, run zypper up.

  2. Copy the exported .tar.gz file to an empty directory and unpack it. Then enter the new directory:

    tux > mkdir EMPTY_DIR
    tux > cd EMPTY_DIR
    tux > tar xf /PATH/TO/smt-export.TIMESTAMP.tar.gz
    tux > cd smt-export
  3. If you chose to export the SSL certificates from SMT, copy the CA private key and certificate to /etc/rmt/ssl/:

    tux > sudo cp ssl/cacert.key /etc/rmt/ssl/rmt-ca.key
    tux > sudo cp ssl/cacert.pem /etc/rmt/ssl/rmt-ca.crt
  4. Run the YaST RMT configuration module as described in Section 1.3, “RMT Configuration with YaST”. If you imported the SMT CA certificate, add the domain of the SMT server to the common names of the new SSL certificate.

  5. Run the RMT synchronization to get the products and repositories data from SUSE Customer Center.

    tux > sudo rmt-cli sync
  6. Import the data from the SMT server.

    tux > sudo rmt-data-import -d ./
  7. Optional: If the URL of the RMT server changed, change the URL parameter of clients in /etc/SUSEConnect to point to the new RMT server. Alternatively, change the DNS records to re-assign the host name to the RMT server.

  8. Optional: Move the mirrored repository data from SMT to RMT, and adjust the ownership of the copied data.

    tux > sudo cp -r /var/www/htdocs/repo/* /usr/share/rmt/public/repo/
    tux > sudo chown -R _rmt:nginx /usr/share/rmt/public/repo
    Tip
    Tip

    The path for storing custom repositories' data on the RMT server is different from that of SMT. With RMT, it replicates the directory structure of the source server's URL into a top level directory. For example, if the URL of the custom repository is

    http://download.opensuse.org/debug/distribution/leap/15.1/repo/oss

    its path on the RMT server will be

    /usr/share/rmt/public/repo/debug/distribution/leap/15.1/repo/oss
  9. Custom repositories on the SMT server are disabled be default. If you want to mirror them to the RMT enable them before mirroring.

    1. Check for custom repositories by running:

      tux > sudo rmt-cli repos custom list

      A table of all custom repositories will be shown. the first column contains the ID of each repository and the Mirror? column will show false.

    2. Enable each custom repository you would like to mirror by running:

      tux > sudo rmt-cli repos custom enable ID
  10. Update the packages in the repositories by starting the mirroring process:

    tux > sudo rmt-cli mirror
Print this page