-
Notifications
You must be signed in to change notification settings - Fork 1
Home
-
Create a SUSE Manager Content Lifecycle Management project for your distribution, carefully choosing a short-but-descriptive prefix in the name, including ALL source channel modules. Add Filters as needed, and at least one Environment.
-
Create an Activation Key that includes the filtered project channels
-
(Optional) Create a bootstrap script - although the profile will not need it, since it is managed in the AutoYaST
-
Create an Autoinstallation Distribution in SUSE Manager for each base channel to which you will migrate. You will create more Distributions than Profiles, though you can re-use the same Tree Path for the boot media. In the Distribution, reference the specific Base Channel to match the base to which you might migrate - i.e, the base channel of your CLM project Environment Lifecycle. Label the Distribution something that references your specific prefix. Set the Installer Generation to match your specific version of SLES (12,15,etc).
-
Create an Autoinstallation Profile for each SLES distribution and service pack you wish to migrate TO - distinguishing only between a salt minion/traditional client FROM which you will migrate. Thus you should only need one SLES12 SP4 - you can use the variable to distinguish between the CLM environments. Edit the profile in a tool where you can use cut-and-paste for the channels in your profile. Use variables for the profiles where possible.
Some tested profiles for in-place migrations are here: https://github.com/dvosburg/in-place_migrations
Sample Variables:
registration_key=1-15sp1-demo-test org=1 channel_prefix=15sp1-demo-test distrotree=15sp1-demo-test
Sample use in the profile:
<listentry> <ask_on_error config:type="boolean">true</ask_on_error> <media_url>https://$redhat_management_server/ks/dist/child/$channel_prefix-sle-module-web-scripting15-sp1-pool-x86_64/$distrotree</media_url> <name>$channel_prefix SLE-Module-Web-Scripting15-SP1 Pool for x86_64 </name> <product>Web Scripting Module 15 SP1 x86_64 Pool</product> </listentry>`
-
Assign your Autoinstallation Profile in System Details>Provisioning for one system, or in the Provisioning tab in SSM for as many systems as you need. For migrations, there is no special requirement for PXE - the kernel and initrd are copied to the system and reinstallation is set to occur via grub.
-
You can create an ISO to install (if needed) with cobbler commands using the SUSE Manager server CLI. Copy the ISO file output to the machine you wish to migrate and boot from it. View all the profiles with this:
cobbler profile list 15sp1-demo-test:1:Demosite
Then build the ISO file with this command:
cobbler buildiso --iso=/tmp/15sp1-demo-test.iso --profiles=15sp1-demo-test:1:Demosite