Description

This article lists the steps required to migrate existing SUSE Enterprise Linux Server (SLES) v11 servers deployed on the Managed Cloud Platform to the SUSE Linux Update Infrastructure used by the Managed Cloud Platform.

It is important to note that SLES servers that have been migrated to use SUSE Linux Update Infrastructure will not work outside of the MCP network. That is, if you export the server and import it into another Cloud provider or into an on premise hypervisor, the server will not be able to access the CDS servers that comprise our Update Infrastructure. You will be required to re-license the server with another provider or directly with SUSE.

Prerequisites:

  1. Disable 'susecloud' service and Amazon hosted repositories:

    # rm -f /etc/zypp/repos.d/susecloud*.repo
    
    # rm -f /etc/zypp/services.d/susecloud.*
  2. Disable CD/DVD repository:

    # sed -i -e 's/enabled=1/enabled=0/' "/etc/zypp/repos.d/SUSE-Linux-Enterprise-Server-11-SP1 11.1.1-1.152.repo"
  3. Remove any previous registration data:

    # suse_register -E
  4. Download to your server the following ZIP file which contains RPM packages for SUSE's Public Cloud Module and certificates required to grant access to the Update Infrastructure. The RPM packages are intended for SUSE Linux Enterprise Server v11 SP3+ 64-bit. sles11_public_cloud_module.zip

    1. cloud-regionsrv-client-6.4.6-18.1.x86_64.rpm
      [SHA1 sum: ab2b7f6273d47938a9da993e1c3c8f08407f9a95]
    2. cloud-regionsrv-client-mcp-config-1.0.0-1.x86_64.rpm
      [SHA1 sum: 73b78828d9a31fb326235af0e006f2dfa6073bbe]
    3. python-lxml-2.3.6-0.13.1.x86_64.rpm
      [SHA1 sum: c231010d01fc4eff52ed68db74c14a72a774200d]
    4. python-m2crypto-0.21.1-2.4.1.x86_64.rpm
      [SHA1 sum: 8a805fecae6f6ade5f0fe2b6fc5c4adfec1f1d25]
    5. python-requests-2.0.1-0.9.37.x86_64.rpm
      [SHA1 sum: 05627a2b4d6d6e6b6b79a391b0e10aec562e6092]

Content / Solution:

  1. Install the RPM packages, using the 'rpm' command:

    # rpm -ivh cloud-regionsrv-client-6.4.6-18.1.x86_64.rpm \
    cloud-regionsrv-client-mcp-config-1.0.0-1.x86_64.rpm \
    python-lxml-2.3.6-0.13.1.x86_64.rpm \
    python-m2crypto-0.21.1-2.4.1.x86_64.rpm \
    python-requests-2.0.1-0.9.37.x86_64.rpm



  2. Enable the 'guestregister' service:

    # chkconfig guestregister --level 235 on 



  3. Start 'guestregister' service, which will initiate registration:

    # service guestregister start



  4. If prompted during Step 3, regarding a "New repository or package signing key", answer always (a) after you've confirmed the fingerprint:

    • Retrieving repository 'MCP_SLE11_Public_Cloud_Module' metadata [/]
      New repository or package signing key received:
      Key ID: 0E7A71FA269A7AA5
      Key Name: MCP SLUI Package Signing Key (MCP SLUI Repository Key) <itaas.noc@dimensiondata.com>
      Key Fingerprint: 8D600CE85361F331805AA6970E7A71FA269A7AA5
      Key Created: Mon Jun 20 17:16:26 2016
      Key Expires: Sat Jun 19 17:16:26 2021
      Repository: MCP_SLE11_Public_Cloud_Module
      Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r): a 

       

  5. Enable the "SLE11-Public-Cloud-Module" repository:

    # zypper modifyrepo -e SLE11-Public-Cloud-Module

     

     

  6. Relocating a Server to a different Geo:

    Any SUSE Linux Servers that are moved to a new GEO will need to be (re)registered within that GEO / Region in order to continue receiving updates and / or software from SUSE repositories:
    1. Remove previous registration data:
      # suse_register –E
    2. Register system with SLUI:

      # service guestregister start