Skip to content

PAYG requirement clarified #4461

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 4, 2025
Merged

PAYG requirement clarified #4461

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .changelog
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@
# - Fixed error in Bat section of Upgrade Guide (bsc#1234567)
# For guidelines: https://en.opensuse.org/openSUSE:Creating_a_changes_file_(RPM)#Changelog_section_.28.25changelog.29

- Clarified requirement for PAYG in Installation and Upgrade
Guide (bsc#1236066)
- Added information for proxy migration to Installation and
Upgrade Guide (bsc#1214568)
- Added reference to dry run documentation (bsc#1223368)
Expand Down
4 changes: 2 additions & 2 deletions modules/installation-and-upgrade/pages/connect-payg.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@ Then the {productname} Server has access to products on the RMT host that are no

Before using {payg} feature make sure that:

* The {payg} instance is launched from the correct SUSE product image (for example, SLES, SLES for SAP, or SLE HPC) to allow access to the desired repositories
* The {payg} instance is launched from the correct SUSE product image (for example, SLES, SLES for SAP, or SLE HPC) to allow access to the desired repositories.

* {productname} Server has connectivity to the {payg} instance (ideally in the same region) either directly or via a bastion
* {productname} Server has connectivity, directly or via a bastion, to the {payg} connection endpoint, which must be in the same region as the Server.

* A basic {scc} account is required. Enter your valid {scc} credentials in menu:Admin[Setup Wizard > Organization Credentials]. This account is required for accessing the {productname} client tools for boostrapping regardless of {payg} instances.

Expand Down
Loading