Skip to content
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.

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

Add diagram of installer-based provisioning with HTTP boot #3305

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Lennonka
Copy link
Contributor

@Lennonka Lennonka commented Sep 20, 2024

What changes are you introducing?

Adding a sequence diagram of installer-based provisioning with HTTP boot. Using PlantUML to build the diagram.

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

Preparation for improvements of Provisioning hosts. The diagram will be used later to explain the workflow of the provisioning method.

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

Checklists

  • I am okay with my commits getting squashed when you merge this PR.
  • I am familiar with the contributing guidelines.

Please cherry-pick my commits into: N/A

Copy link

github-actions bot commented Sep 20, 2024

The PR preview for ec1a4b5 is available at theforeman-foreman-documentation-preview-pr-3305.surge.sh

The following output files are affected by this PR:

show diff

show diff as HTML

@Lennonka Lennonka added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective labels Sep 20, 2024
@Lennonka
Copy link
Contributor Author

Lennonka commented Oct 8, 2024

Updated based on feedback from #3304

@Lennonka
Copy link
Contributor Author

Lennonka commented Oct 8, 2024

We should tweak the diagram in such way so that it doesn't contain TFTP. Foreman uses the TFTP folder to do some steps, but HTTP boot doesn't use the TFTP protocol.

@Lennonka Lennonka marked this pull request as draft October 8, 2024 15:24

!include foreman.pstyle

title Installer-based provisioning with HTTP boot on bare metal
Copy link
Contributor

Choose a reason for hiding this comment

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

Does this diagram describe the HTTP boot feature or iPXE boot over the HTTP?

Copy link
Contributor

Choose a reason for hiding this comment

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

Because to me, this is the same as the #3304, except the tftp/http.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

HTTP boot feature.

participant "Foreman" as Foreman
participant "Foreman\nProxy" as Proxy
'participant "Pulp\n(Katello)" as Pulp
participant TFTP
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
participant TFTP
participant HTTP

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Do we have to use an HTTP participant explicitly? Or can we say that HTTP is served by Foreman Proxy? I was rather going with the latter, but there may still be a few tweaks needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs style review Requires a review from docs style/grammar perspective Needs tech review Requires a review from the technical perspective
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants