Application requirements

If your solution is designed to work with the SUSE Virtualization platform, it must be validated as SUSE Ready for SUSE Virtualization. To achieve this, you must demonstrate:

• Primary Development Ownership:
  • Your organization is the primary developer or maintainer of the software.
• Platform Testing:
  • You have tested the software on a supported version of SUSE Virtualization managed by SUSE, using recommended deployment practices (including VM lifecycle management, storage integration, networking models, and/or GPU management, as applicable).
• Commercial Support Commitment:
  • You provide commercial support for the software on the declared SUSE Virtualization versions and supported configurations.
• Published Support Matrix:
  • You publish documentation specifying the supported versions of SUSE Virtualization for the software, along with guest operating system requirements if applicable.
• Active Maintenance and Security Responsiveness:
  • You actively maintain and proactively update the software so that:
    • Critical vulnerabilities are patched in a timely manner.
    • Release notes disclose serious bugs, known issues, or vulnerabilities.
• Clear Licensing Terms:
  • You publish a clear software license and/or terms and conditions for the software.
• Maintain validation against current versions
  • Continue to validate new versions of your software against the latest versions of SUSE Virtualization
• Non-Competitive Alignment:
  • Your software must not compete commercially with SUSE Virtualization, SUSE Rancher Prime, SUSE Edge, or SUSE AI platforms.

Platform Testing Requirements for SUSE Harvester

You must demonstrate that your application has been tested on a supported version of SUSE Virtualization, with verification across the following key areas:

1. Installation & Deployment

• Ensure your application can be deployed onto a virtual machine(s) (VMs) provisioned by SUSE Virtualization.
• If the application integrates with cloud-init or other VM bootstrap methods, validate those workflows.
• Provide customer-facing document for any installation dependencies, preconditions, or special configurations required within a SUSE Virtualization-managed VM.

2. Guest OS Compatibility

• Verify your application runs correctly on at least one of the SUSE-supported guest operating systems.
• Document supported guest OS versions and required packages or kernel modules.

3. Storage Integration

• Test your application with SUSE Virtualization’s default storage backend (Longhorn) as required.

4. Networking Compatibility

• Validate your application works with SUSE Virtualization's default Layer 2 bridge network.
• If the application requires static IPs, VLANs, or SR-IOV, test with SUSE Virtualization’s Multus and VLAN support.
• Document any required network ports and protocols.

6. Lifecycle Operations

• Test your application across the full VM lifecycle.
• Ensure your application handles shutdown signals gracefully if the VM is stopped from the Harvester UI or CLI.