docs: restructure deployment guide#310
Conversation
✅ Deploy Preview for metal-stack-io ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
c534aa8 to
bdb6362
Compare
82b6b06 to
a2164b5
Compare
|
Still working on the guide, now streamlining and connecting this to an overhauled concepts section PR. |
|
I am now ready for a nitpicky review. @vknabel @majst01 @simcod @l0wl3vel I tried to improve depth and consistency. There are still blind spots like the deployment guide, but there are separate issues for that, like #247. Just imagine a great concepts part already to be there, explaining the birds-eye-view - because this is what I am now working on. It will be the next PR to review. This PR focuses on deployment and tries not to double information, that should be under concepts. |
There was a problem hiding this comment.
The partition deployment looks much better already. Left a few minor remarks.
One thing I'm not sure about is whether we should include management spines and management leaves in the reference topology. There are metal-stack environments that simply have management switches without any differentiation. The role of any management switch is to relay OR answer DHCP requests from the productive switches' management interfaces as well as from the worker machines' IPMI interfaces. And they provide access to the management interfaces and IPMI interfaces. Whether or not they are split into spines and leafs is not that important.
| - Provide destination NAT to the management server and its IPMI interface | ||
| - Provide DHCP options for Onie Boot and ZTP of the management spine | ||
| - Provide DHCP management addresses for the management spine, management server, and IPMI interfaces | ||
| - Perform Hairpin-NAT so the management server can access itself via its public IP (required by the CI runner to delegate jobs) |
There was a problem hiding this comment.
Not sure a mgmtserver can access its public IP. I'll try that.
There was a problem hiding this comment.
Came from the existing docs, just let me know.
5 participants
Description
We had a discussion in the team about restructuring the deployment guide.
Parts of the concept area do not belong there, but should go under the deployment guide.
For the guide not to get too bloated, this PR splits the guide into sub pages and moves parts from the concepts area to the regarding sub pages.
The concepts should come before the deployment guide, so there is a separate issue:
#312
Please do only merge this together with the concepts PR, as the changes are heavily intertwined.
Used AI-Tools ✨
References: