Skip to content

[release-3.1] metal3: downstream cluster EIB example fixes #1086

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
hardys merged 1 commit into from
Mar 23, 2026
Merged

[release-3.1] metal3: downstream cluster EIB example fixes #1086

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
12 changes: 9 additions & 3 deletions asciidoc/product/atip-automated-provision.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,12 +128,18 @@ operatingSystem:
- time-sync.target
users:
- username: root
encryptedPassword: ${ROOT_PASSWORD}
encryptedPassword: $ROOT_PASSWORD
sshKeys:
- ${USERKEY1}
- $USERKEY1
packages:
packageList:
- jq
sccRegistrationCode: $SCC_REGISTRATION_CODE
----

`$\{ROOT_PASSWORD\}` is the encrypted password for the root user, which can be useful for test/debugging. It can be generated with the `openssl passwd -6 PASSWORD` command
Where `$SCC_REGISTRATION_CODE` is the registration code copied from https://scc.suse.com/[SUSE Customer Center], and the package list contains `jq` which is required.

`$ROOT_PASSWORD` is the encrypted password for the root user, which can be useful for test/debugging. It can be generated with the `openssl passwd -6 PASSWORD` command

For the production environments, it is recommended to use the SSH keys that can be added to the users block replacing the `$\{USERKEY1\}` with the real SSH keys.

Expand Down
15 changes: 12 additions & 3 deletions asciidoc/quickstart/metal3.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -238,14 +238,23 @@ operatingSystem:
systemd:
disable:
- rebootmgr
- transactional-update.timer
- transactional-update-cleanup.timer
users:
- username: root
encryptedPassword: ${ROOT_PASSWORD}
encryptedPassword: $ROOT_PASSWORD
sshKeys:
- ${USERKEY1}
- $USERKEY1
packages:
packageList:
- jq
sccRegistrationCode: $SCC_REGISTRATION_CODE
Copy link
Collaborator

@ranjinimn ranjinimn Mar 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add the indentation here ?

Suggested change
sccRegistrationCode: $SCC_REGISTRATION_CODE
- $USERKEY1
createHomeDir: true
packages:
packageList:
- jq
sccRegistrationCode: $SCC_REGISTRATION_CODE

or should I rebase once this PR is merged?

Copy link
Contributor Author

@hardys hardys Mar 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To preserve the history it's best to merge this, then rebase your PR if that's OK for you?

----

`$\{ROOT_PASSWORD\}` is the encrypted password for the root user, which can be useful for test/debugging. It can be generated with the `openssl passwd -6 PASSWORD` command
Where `$SCC_REGISTRATION_CODE` is the registration code copied from https://scc.suse.com/[SUSE Customer Center], and the package list contains `jq` w
hich is required.

`$ROOT_PASSWORD` is the encrypted password for the root user, which can be useful for test/debugging. It can be generated with the `openssl passwd -6 PASSWORD` command

For the production environments, it is recommended to use the SSH keys that can be added to the users block replacing the `$\{USERKEY1\}` with the real SSH keys.

Expand Down
Loading