Bare metal deployment guide #222
Conversation
r0ckarong
added
DeploymentGuide
|
@Klaven could you please allow maintainer edits for this pull request: This makes work a lot easier. Thanks |
There was a problem hiding this comment.
LGTM, but I think it should be extended to mention:
- The node will have only a root user enable, with no password set due to security reasons
- The user must edit the template and include his own ssh keys (maybe show a snippet with multiple identities added)
- Point out the only way to connect to the node, in the beginning, is to ssh as root
- Point out the root user can be enabled after the 1st login by using the
passwdcommand - Explain how to perform the registration against a SMT/RMT server. What are the values that have to be entered. The point is, the snippet we generate is for SCC, how different is it to connect to a SMT server/RMT?
As always, we don't have to rewrite the existing documentation of SLES. If there's already some existing documentation let's just point to it (for example: the registration against SMT/RMT should already be part of some manual)
|
I looks like @dcoopr has already spotted this issue and proposed the same remediation I was suggesting: https://bugzilla.suse.com/show_bug.cgi?id=1135998 |
r0ckarong
removed
Blocked
Klaven
force-pushed
the
bare-metal
branch
2 times, most recently
from
70f4146
to
443bc88
Compare
|
You may need to review the docs based on the result of this SUSE/skuba#279 |
|
@jordimassaguerpla the person who completes #279 should update the documentation once it is complete. nothing to hold this PR for. |
Includes documentation on where to find an example autoyast file as well as links to the other required documentation.
There was a problem hiding this comment.
LGTM, thanks - I will provide another PR once SUSE/skuba#283 will be enhanced by caasp-node pattern installation and merged.
Not needed anymore - Markus uses general "placeholder" word and also added ntp_server note.
fixes SUSE/avant-garde#389 Signed-off-by: Jordi Massaguer Pla <jmassaguerpla@suse.de>
|
see Klaven#1 for fixing https://github.com/SUSE/avant-garde/issues/389 |
Take autoyast file from package
|
@Klaven I'm missing several things in the current version:
|
|
I'm involved in autoyast as well so I will try to answer...
There is no difference, master and worker nodes are using the very same pattern
If you are talking about item order in autoyast.xml file it doesn't matter - SLE will handle the item order automatically during installation.
yup, just repeat these steps for as many nodes you need (or how many machines you have) |
|
|
||
| The default production scenario consists of 8 nodes: | ||
|
|
||
| * 2 Load Balancers |
There was a problem hiding this comment.
I don't think that skuba command supports more than one load-balancer.
There was a problem hiding this comment.
This is how it's described in the architecture description. Any idea how this would be handled?
There was a problem hiding this comment.
No idea, maybe it can be achievable by using round-robin DNS entry (two lb hosts with the same public IP) but I would describe only a case with 1 LB. After clarifying we can modify again.
There was a problem hiding this comment.
I talked to Rafa we need to clarify the load balancer stuff more.
|
|
||
| [NOTE] | ||
| ==== | ||
| To account for hardware/platform specific setup criteria (legacy BIOS vs. (U)EFI, drive partitioning, networking etc.), |
There was a problem hiding this comment.
I've verified that current ay file is compatible with BIOS and EFI as well.
|
Apart of the unclear LBs count LGTM |
|
The LB topic will be clarified at a later date with: #261. |
@r0ckarong I'm struggling here. for some reason the references are not working. Also, I refereed to it as
skuba, not sure if I should be doing that orcaaspctl. I feel like the one section about where/how to get the autoyast file should go away and we should just link the example when the code is open sourced.