Last Update: 2021-09-03
Table of Contents
Public Mailing list
Frequently Asked Questions
Beta Test Subscription and Registration Code
Migrating from SLE Micro 5.0 to SLE Micro 5.1 Beta X
Updating from SLE Micro 5.1 Beta X to SLE Micro 5.1 Beta X+N
Updating from SLE Micro 5.1 Beta X to SLE Micro 5.1 GM
Contact Beta Manager
Welcome to the dedicated web page for the beta of SUSE Linux Enterprise Micro (SLE Micro), the ultra-reliable, lightweight operating system purpose built for edge computing. It leverages the enterprise hardened security and compliance components of SUSE Linux Enterprise and merges them with a modern, immutable, developer-friendly OS platform.
- Web based System Management with Cockpit
As an immutable operating system designed for Edge use cases, SLE Micro does not support YaST for local system administration. We provide basic administration tools via the included web-based system management based on the Cockpit project.
- New deliverable: Real-Time
Real-Time – On Intel and AMD 64 SLE Micro provides a real-time kernel as an option.
- Security Framework
SLE Micro standardises on SELinux as the security and confinement framework and extents it with a fully supported SELinux policy.
- Based on SLE 15 SP3
SLE Micro 5.1 is based on SLE 15 SP3 where SLE Micro 5.0 was based on SLE 15 SP2. Please check out the Release Notes for SLES 15 SP3 x86_64, s390x and aarch64
- SUSEConnect re-write
The current implementation of SUSEconnect in SLE 15 is done with Ruby, which in turn requires SLE Micro to provide a Ruby stack.
As we strive to make SLE Micro as minimal as possible we decided to re-write SUSEConnect in a compiled language that does not come with a dependency on a scripting language stack
- Full 5G support (Planned, not yet included)
Initial testing with partners and customers has shown the support for 5G devices with the currently used networking stack based on wicked is limited.
With SLE Micro 5.1 the support for 5G client devices shall be improved and expand to cover selected devices.
- Secure Device Onboarding (SDO)
Secure Device Onboarding (SDO) will play a major role in upcoming edge deployments. We therefore will provide an SDO client on SLE Micro 5.1. The client will not be provided on the SLE Micro 5.1 images itself but outside of the images.
- LivePatching(Planned, not yet included)
With SLE Micro being introduced in datacenter as a container host OS, there is a need for specific datacenter feature, thus the availability of live patching.
We are going to provide LivePatching with the final product SLE Micro 5.1.
Our plan is to release only two Public Pre-Release ISOs, one Public Beta, one Public Release Candidate from August 2021 to September 2021.
Beta 2 — August 06, 2021 RC 2 — September 03, 2021
- First Customer Shipment — October 2021
Please note that we reserve the right to change or adapt this schedule depending on various factors. Rest assured that we will communicate if there is any change to the plan.
SLE Micro 5.1 is available on the following architectures: aarch64, s390x and x86_64.
Installation Media and a bootable images of SLE Micro are available for all architectures. Here is the description of each and every images:
- ISO images below are the usual Media which can be booted for interactive installation with YaST or unattended installation with AutoYaST:
- Default images below are ready-to-deploy raw disk images, including podman as container engine and KVM as virtualization stack for x86_64 machines and RaspBerry Pi. During initial boot, Ignition or Combustion configuration must be provided in order to perform basic configuration (e.g. set root password).
- Default image of SLE Micro utilizing the real-time kernel, without KVM virtualization stack
- Default images of SLE Micro, including podman as container engine and KVM as virtualization stack, for various types of hypervisor and storage on IBM system z.
Note: The following Documents are drafts.
And will remain as such through out the SLE Micro Beta Program. Documentation for Beta Products do not yet have the quality, accuracy and content of our official documentation. However we will update these documents on the fly during the SLE Micro Beta Program.
All documentations are available at https://susedoc.github.io/:
- Installation Quick Start
- AutoYaST Guide
- TBD: Deployement Guide. In the meantime please refer to our FAQ for Migrating from SLE Micro 5.0 to SLE Micro 5.1
- bsc#1188337 – SLE Micro 5.1 has two IPv4 addresses
- bsc#1189807 – [s390x] System doesn’t boot after enabling SELinux
- bsc#1190124 – libvirt fails to start default network with enabled SELinux
- bsc#1190063 – z/KVM SLEM5.1 image cannot run QEMU guest
- Our testing has revealed multiple bugs with the pre-built images for s/390x. We are working on analysing them, their impact and severity.
Whenever you find a bug or have a question while using SUSE Linux Enterprise Micro, we highly recommend that you use our mailing list first, then if it really make sense you should open a bug report.
In case you would like to share some sensitive data with us (data for bug reports, feedbacks, etc), please contact us at email@example.com, and we will review your case and provide a private channel with us.
Public Mailing List
firstname.lastname@example.org is our dedicated Public Mailing List to discuss SUSE Linux Enterprise Beta products. It is used by the SUSE Release Team to announce new beta images and technical information, as well as for general or technical questions, feedback, or defect reports related to SUSE Linux Enterprise Beta products from our beta testers community. Only subscribers can post to our mailing lists. To subscribe, please go to http://lists.suse.com/mailman/listinfo/micro-beta.
Only subscribers can post to our mailing lists. To subscribe, please go to http://lists.suse.com/mailman/listinfo/micro-beta.
Please refer to our Mailing Lists Guideline for more information.
Here are the links to the SLE Micro Bugzilla product that you will use for reporting the defects of the following products:
Create a new bug for:
Please refer to our complete Bugzilla guideline for more information and before creating your first bug report: how to use Bugzilla
Frequently Asked Questions
– Beta Subscription and Registration Code
Warning: Beta Registration Code
Registration is not working with your regular SLE Micro key, special Beta Registration Code is required. Thus, you don’t have access to the SLE online channels/repositories and Modules without a Beta Registration Code.
The Beta Registration Code is the key to unlock the Beta Subscription in our SUSE Customer Center. The Beta Subscription consist of giving access to our SLE Micro Beta Online Channels.
We will not provide a beta product subscription or beta product registration code by default for the SLE Micro 5.1 Beta Program. You might request one via email@example.com, please specify if you want a registration code for which architectures.
– Migrating from SLE Micro 5.0 to SLE Micro 5.1 Beta
Update from SLE Micro 5.0 to 5.1 is now supported. Unlike with SLES, which offers several methods, with SLE Micro there is only one method available, via transactional-update. To migrate from 5.0 to 5.1, follow these steps
- Install SLE Micro 5.0 and register it with the Beta registration code
- Install all updates patches of SLE Micro 5.0 via transactional-update. Reboot to new snapshot if needed, or perform next step from the not-yet-in-use snapshot
- Install the package ‘zypper-migration-plug-in’ via transactional-update. Reboot to recent snapshot
- Call ‘transactional-update migration’. The workflow will be similar as when calling ‘zypper migration’ with SLES
- Reboot the system
Warning: Packages being downgraded
You will be reported that some packages are getting downgraded during the migration process. For now, please, ignore this and proceed with upgrade.
Note: Deployment Guide not ready yet
Please note that we will of course have the migration process documented in our upcoming Deployment Guide! In the meantime please report any issue you are facing to our firstname.lastname@example.org Public micro-beta mailing list.
– Updating from SLE Micro 5.1 Beta to the next SLE Micro 5.1 Beta
Even if it’s completely feasible and working, we do not recommend to update from “SLE Micro 5.1 Beta X” to “SLE Micro 5.1 Beta X+N” for your thorough beta testing.
Because this scenario is specific to beta and can not be compared to any SLE Micro production update scenario. During the beta phase of our products, we need the flexibility of doing important changes to packages (libraries, configuration files, features, etc), like upgrading or downgrading to different versions.
Thus changes between SLE Micro Beta might look very different from regular updates we make in official SLE Micro releases.
We highly recommend to test the following scenarios, whenever a new Beta version is released:
- Fresh install of new SLE Micro 5.1 Beta,
- Migration from SLE Micro 5.0 to new SLE Micro 5.1 Beta.
– Updating from SLE Micro 5.1 Beta to SLE Micro 5.1 GM
Warning: Migration from Beta to Gold Master
Migrating from SLE Micro 5.1 Beta to SLE Micro 5.1 Gold Master (the final and official version) is NOT SUPPORTED. If you want to put the final version of our product in production, you need to do a fresh installation or a migration from an existing supported version. We will not support the migration from a beta product to a final release of the product.
As a reminder, our SUSE Beta EULA states that you should not put SUSE Beta Products in production.
– Contact Beta Manager
Do you have a question or an issue to report on our Beta Program? Want to get in touch with our Product Managers or Engineering team? Or simply share a feedback? Please do not hesitate to contact us via email@example.com!