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 assesment docs #323

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from
Draft

Add assesment docs #323

wants to merge 7 commits into from

Conversation

Itxaka
Copy link
Member

@Itxaka Itxaka commented Dec 5, 2024

No description provided.

Signed-off-by: Itxaka <[email protected]>
@Itxaka Itxaka requested a review from a team December 5, 2024 11:48
Copy link

netlify bot commented Dec 5, 2024

Deploy Preview for kairos-io ready!

Name Link
🔨 Latest commit 1c9110d
🔍 Latest deploy log https://app.netlify.com/sites/kairos-io/deploys/6751c5c16fe02e0008f3ad63
😎 Deploy Preview https://deploy-preview-323--kairos-io.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

content/en/docs/Architecture/trustedboot.md Outdated Show resolved Hide resolved
content/en/docs/Architecture/trustedboot.md Outdated Show resolved Hide resolved
content/en/docs/Examples/boot_assessment_trusted_boot.md Outdated Show resolved Hide resolved

# Enabling Automatic Boot Assessment with Trusted Boot

In this tutorial, we will walk through how to configure Kairos to enable **automatic boot assessment**, where the boot loader can determine the health of a boot entry. Specifically, we'll configure systemd services to trigger the `boot-complete.target` to mark boot entries as *good* or *bad*. We'll also cover how to implement automatic reboots when a service fails, allowing retries of a boot entry until success or exhaustion of attempts.
Copy link
Member

@mudler mudler Dec 5, 2024

Choose a reason for hiding this comment

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

By reading it entirely something is not really clear to me: here we say that the example is on how to enable the automatic boot assessment, but later we talk about marking an arbitrary service failure impacting the boot assessment - I think we should be explicit here in answering the following questions:

  • what are system defaults ? is boot assessment enabled?
  • is Kairos having a default boot assessment strategy?
  • if Kairos does have a default , how it behaves, what are the limitations?
  • If it doesn't, why we don't have a default for it?
  • finally, how can we extend the boot assessment by including our own custom services to impact the system state check?

Copy link
Member Author

Choose a reason for hiding this comment

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

we currently dont have any assesment strategy...yet.

The idea was to write the docs first and then start enabling it ourselves, plus adding e2e tests for it.

Current boot assessment is set as the default, i.e. if multi-user.target is reached, then it considers the system as good and marks it as such.

But I get what you mean, I will redo this to extend to introduce first the current states of assesment on kairos and then keep this as how can be extended to support more things.

Copy link
Member Author

Choose a reason for hiding this comment

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

Expanded!

Itxaka and others added 2 commits December 5, 2024 16:10
@Itxaka Itxaka requested a review from mudler December 5, 2024 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants