SUSE Multi-Linux Manager on the Public Cloud: Deployment and Consumption Choices

Introduction

SUSE Multi-Linux Manager (SMLM) is a powerful tool for managing the lifecycle of Linux workloads in cloud environments. With version 4.x at the end of the general support phase, customers are now transitioning to SMLM 5. This transition presents an opportunity for organizations to evaluate their deployment, architectural, and procurement strategies for their SMLM environment in the cloud.  This blog explores the various choices available when deploying and managing SMLM in a public cloud setting.

Consumption Models for SUSE Multi-Linux Manager 5

The move to SUSE SMLM 5 necessitates a new deployment due to significant architectural enhancements that prevent in-place upgrades from v4.x. When deploying a new SMLM instance in the public cloud, customers have two primary consumption models:

1. Pay-Monthly / Pay-As-You-Go (PAYG)
Current Availability: AWS & Azure

The Pay-Monthly / PAYG model is our recommended deployment approach for cloud environments. It offers the convenience of monthly billing for SMLM subscriptions directly through the cloud marketplace. Charges are based on the number of instances (SMLM Clients) under management during the month. This model is highly flexible and cost-effective for all types of estates, whether relatively static or experiencing temporary bursts in instance counts, as you only pay for what you manage that month.

2. Bring Your Own Subscription (BYOS)

With the Bring Your Own Subscription (BYOS) model, customers purchase annual SMLM subscriptions based on the peak number of clients they anticipate managing. This model can be well-suited for organizations with relatively static Linux estates. However, for environments where the number of managed instances can fluctuate significantly, the Pay-Monthly / PAYG offer may provide greater efficiency.

Underlying Operating System Choices

The choice of underlying operating system for your SMLM instance varies depending on the consumption model.

SUSE Linux Micro (Default for PAYG and BYOS deployments)

The SMLM Pay-Monthly listing includes SUSE Linux Micro as the base operating system. SUSE Linux Micro is a lightweight, enterprise-ready Linux host designed for containerized and virtual workloads. It simplifies operations and development, offering a secure, reliable, and compliance-ready host for mission-critical workloads like SMLM in the cloud. Its read-only file system and transactional updates contribute to reduced maintenance and simplified management.
For BYOS deployments, SUSE Linux Micro is also the default OS and is included in the cost of your SMLM subscription.

SUSE Linux Enterprise Server (SLES) for BYOS

For customers who prefer the familiar and fully featured experience of SUSE Linux Enterprise Server (SLES) to host their Multi-Linux Manager Server, SLES can be used as the base OS for BYOS deployments. However, a separate SLES subscription will need to be purchased to act as the base operating system, with SMLM then deployed on top.

Deployment Methods in the Cloud

SUSE provides streamlined deployment options for SMLM in the cloud.

Using Provided Cloud Images

SUSE offers pre-configured cloud images for SUSE Multi-Linux Manager 5.x in the respective cloud provider marketplaces. These images include the default base OS (SUSE Linux Micro) and pre-installed, tested SMLM packages. Utilizing these images enables a rapid deployment of SUSE Multi-Linux Manager in just a few steps:

1. Provision the instance from the provided image.
2. Add recommended storage devices for the database and updates. Current recommendations are 100GB for the Root File System, 80GB for the Database volume, and a large disk for updates (typically 50GB for each SUSE product to be mirrored). Further details are available in the documentation: https://documentation.suse.com/multi-linux-manager/5.1/en/docs/specialized-guides/public-cloud-guide/payg/aws/payg-aws-requirements.html.
3. Verify the Multi-Linux Manager host name.
4. Execute the setup script to finalize the installation.

SMLM cloud images are available for both Pay-Monthly (AWS) and BYOS (AWS, Azure, Google). In Azure, the Pay-Monthly offering is deployed as a managed application from the Marketplace.

Manual Deployment on SLES (BYOS)

For BYOS deployments of SMLM on SLES, customers will need to deploy a SLES instance from one of our BYOS images, manually configure the required storage, and then deploy the Multi-Linux Manager packages on top.

Update Synchronization

Once SUSE Multi-Linux Manager is deployed in the cloud, the next crucial step is to mirror updates.

PAYG Connection

For customers utilizing PAYG workloads, SUSE Multi-Linux Manager leverages credentials from a PAYG SLES or SLES for SAP instance to directly mirror update channels from the Public Cloud Update Infrastructure. SUSE maintains update servers across multiple regions globally within each major cloud provider, enabling synchronization of updates from a source local to your SMLM instance.

Further information can be found at:
https://documentation.suse.com/suma/5.0/en/suse-manager/installation-and-upgrade/connect-payg.html
https://www.suse.com/c/suse-manager-update-good-news-if-you-are-a-payg-sles-for-sap-customer-in-the-cloud/

SUSE Customer Center (SCC) for BYOS

Customers with BYOS workloads in the cloud, who hold SLES and SLES for SAP subscriptions in the SUSE Customer Center (SCC), should mirror updates following the standard SUSE Multi-Linux Manager documentation.

Conclusion

So that’s it, choose your consumption model, deployment method and Base Operating System for SUSE Multi-Linux Manager and mirror your updates depending on your managed workloads and you’ll be ready to manage your Linux estate like a pro!  That said, if you need more assistance with setup check out our training courses.