3 SUSE Linux Enterprise Point of Service 11 to SUSE Manager for Retail

3.1 Migration from SUSE Linux Enterprise Point of Service 11 to SUSE Manager for Retail
3.2 Migration from SUSE Linux Enterprise Point of Service 11 to SUSE Manager for Retail with SUSE Manager Installed Independantly

3.1 Migration from SUSE Linux Enterprise Point of Service 11 to SUSE Manager for Retail #

This section describes migrating from an existing SUSE Linux Enterprise Point of Service 11 installation, to a new SUSE Manager installation. You can perform this migration all at once by creating a data dump in a single file, then moving it to the new server; see Section 3.1.1, “Migration with Complete Data Dump”. Alternatively, you can perform the migration in stages by creating a data dump for each branch, and moving them to the new server one by one; see Section 3.1.2, “Migration with Branch by Branch Data Dump”. Importing and deploying the converted data can also be done in one step, or multiple steps, depending on your environment.

3.1.1 Migration with Complete Data Dump #

In this procedure, you create a single data dump in an XML file, convert it to YAML, and migrate it to the new infrastructure all at once.

Install a SUSE Manager server 3.2 (with the Retail pattern). For more information, see https://www.suse.com/documentation/suse-manager-for-retail-3-2/retail-getting-started/retail.chap.install.html.
On the SLEPOS Admin server export all the data stored in LDAP to an XML file. Run this command as an administrator:
```
posAdmin --export --type xml --file dumpfile.xml
```
The resulting dumpfile.xml file will contain global information, with parts about images, hardware and its partitioning, and the description of the branch servers with networking data, services, and attached terminals.
Move the XML file to the newly created SUSE Manager server, and convert it to YAML:
```
retail_migration dumpfile.xml retail.yml
```
Review the generated YAML file (retail.yml) and adjust it as necessary. Consider HWTYPE group naming and image name and version changes in the partitioning data. Group names must not exceed the 56 character limit. You can shorten the names as needed, and the image names must match the images in SUSE Manager. The --save-mapping option can help you with this task.
Also check whether there are duplicate MAC addresses of the terminals in the generated YAML file. Choose which entry you want to keep. If there are duplicate MAC addresses, importing the YAML file will fail.
Note
SUSE Linux Enterprise Point of Service images will not be migrated. You must rebuild the images using the OS image building functionality. For more information about building images, see https://www.suse.com/documentation/suse-manager-3/3.2/susemanager-advanced-topics/html/book.suma.advanced.topics/at.images.html#at.images.kiwi.
Import the complete data (YAML) with:
```
retail_yaml --from-yaml retail.yml
```
You can see statistical data while importing. Then check the results in the Web UI. In Main Menu → Systems → Systems → All, find empty profiles, and in Main Menu → Systems → Groups, the groups for the hardware configuration, the branches, servers, and terminals.

To finalize the branch server migration, you must install the branch server machines as Salt-based minions and bootstrap them as proxies. For more information about proxy installation, see Installing and Registering. For more information about using an activation key to assign the required channels, see Configuring Server. After onboarded to SUSE Manager, the branch servers machines are connected with the empty profiles (by FQDN), and so they will get the Retail configuration.

After all the branches are migrated, shutdown and remove the old SLEPOS Admin Server.

3.1.2 Migration with Branch by Branch Data Dump #

In this procedure, you migrate the SLEPOS infrastructure and the branches one by one, first exporting and then importing.

Install a SUSE Manager server 3.2 (with the Retail pattern). For more information, see https://www.suse.com/documentation/suse-manager-for-retail-3-2/retail-getting-started/retail.chap.install.html.
On every branch server:
```
posAdmin --export --type xml --file dumpfile.xml
```
These dumps will contain only the LDAP data of the branch, and any global data.
Similarily, you can export the LDAP data of every branch if you run the command on the Admin server with the branch credentials explicitly specified:
```
posAdmin --export --type xml --file dumpfile.xml --user $branch_dn \
    --password $password
```
For background information about SLEPOS branch server configuration, see https://www.suse.com/documentation/slepos11/book_slepos/data/cha_slepos_branchserv.html.
Review the generated YAML file (retail.yml) and adjust it as necessary. Consider HWTYPE group naming and image name and version changes in the partitioning data. You can shorten the names as needed, and the image names must match the images in SUSE Manager. The --save-mapping option can help you with this task.
Check whether there are duplicate MAC addresses of the terminals in the generated YAML file. Choose which entry you want to keep. As long as there are duplicate MAC addresses, SUSE Manager will refuse importing the YAML file.
Note
SUSE Linux Enterprise Point of Service images will not be migrated. You must rebuild the images using the OS image building functionality. For more information about building images, see https://www.suse.com/documentation/suse-manager-3/3.2/susemanager-advanced-topics/html/book.suma.advanced.topics/at.images.html#at.images.kiwi.

The data can be imported branch by branch. For each branch perform the following steps:

Run the import command for one branch after the other:
```
retail_yaml --from-yaml retail.yml --branch <branch_name>
```
Repeat the command for every branch.
To finalize each branch server migration, you must install the branch server machine as a Salt-based minion and bootstrap it as a proxy. For more information about proxy installation, see Installing and Registering. For more information about using an activation key to assign the required channels, see Configuring Server. After onboarded to SUSE Manager for Retail, the branch server machine is connected with the empty profile (by FQDN), and so it will get the Retail configuration.
Apply Highstate on the branch server; this will happen automatically if Configuration File Deployment is enabled.
Boot the terminals of the branch.

After all the branches are migrated, shut down and remove the old SLEPOS Admin Server.

3.1.3 Converting XML to YAML #

When you perform a migration using one of the methods in this chapter, one of the steps takes the XML data dump file from SUSE Linux Enterprise Point of Service, and converts it to a YAML file for SUSE Manager for Retail. The tool that performs this conversion has additional features, which are outlined in this section.

To validate the XML file before conversion, and print any errors:

retail_migration dumpfile.xml

To write a mapping file called map.yml:

retail_migration dumpfile.xml  --save-mapping map.yml

The mapping file contains two dictionaries: . images, which maps old SUSE Linux Enterprise Point of Service images to new images built in SUSE Manager. . groups, which maps legacy SUSE Linux Enterprise Point of Service scCashRegister objects to SUSE Manager HWTYPE groups. Group names must not exceed the 56 character limit.

The mapping file should be edited as required for your environment.

To perform a conversion using a mapping file:

retail_migration dumpfile.xml  retail.yml --mapping map.yml

If you are performing a branch-by-branch migration, the resulting retail.yml file will contain a new version of SUSE Linux Enterprise Point of Service LDAP data. If you want to preserve any global changes in your {sme} settings, remove the global hardware types from the resulting retail.yml file before importing it. Alternatively, you can import retail.yml using this command to import only the new systems and groups defined in the file, and leave any existing configuration settings untouched:

retail_yaml --only-new

3.2 Migration from SUSE Linux Enterprise Point of Service 11 to SUSE Manager for Retail with SUSE Manager Installed Independantly #

Proceed as follows if you want to migrate an existing SLEPOS installation to SUSE Manager that was already installed independantly.

Check the version number of the installed SUSE Manager. If needed migrate SUSE Manager to version 3.2.
Check whether the Retail extension is already installed. If not, see SUSE Manager for Retail Installation and install the Retail extension.
Continue as in Scenario 1, Step 2.

Print this page