Operations guide to enable assesment of the Q12026 PoC #24

Open
opened 2026-01-12 08:14:48 +00:00 by janhalen · 5 comments
janhalen commented 2026-01-12 08:14:48 +00:00 (Migrated from github.com)

When #22 and #23 has reached "Done" state, a potential operator of the system should be able to perform a set of operations steps. These should be decided and refined, BUT as a minimum it should be described, how to "boot-strap" a bare metal device and an update of an image + verification of the following auto update.

This work should serve to identify gaps in knowledge and skills of operators and other stakeholders that need to operate this on a day to day basis.

This work will not strive to prove a 1:1 alignment or compatibility with previous systems, but serve as an anchor for showing the benefits and quality improvement of OpenGitOps.

When #22 and #23 has reached "Done" state, a potential operator of the system should be able to perform a set of operations steps. These should be decided and refined, BUT as a minimum it should be described, how to "boot-strap" a bare metal device and an update of an image + verification of the following auto update. This work should serve to identify gaps in knowledge and skills of operators and other stakeholders that need to operate this on a day to day basis. This work will not strive to prove a 1:1 alignment or compatibility with previous systems, but serve as an anchor for showing the benefits and quality improvement of OpenGitOps.
agnetemoos commented 2026-01-12 09:20:11 +00:00 (Migrated from github.com)

I agree that these are essential for the assessment of the Q1 2026 POC:

"boot-strap" a bare metal device and an update of an image + verification of the following auto update.

Further assessment criteria could include some of the following tasks, which are frequently applied to BorgerPCs:

  • Install programs such as Firefox or LibreOffice
  • Set the browser start page
  • Add a desktop shortcut (for example, to the browser or logout)
  • Add a menu item (for example, to the browser or logout)
  • Set a desktop background image
  • Activate Num Lock
I agree that these are essential for the assessment of the Q1 2026 POC: > "boot-strap" a bare metal device and an update of an image + verification of the following auto update. Further assessment criteria could include some of the following tasks, which are frequently applied to BorgerPCs: - Install programs such as Firefox or LibreOffice - Set the browser start page - Add a desktop shortcut (for example, to the browser or logout) - Add a menu item (for example, to the browser or logout) - Set a desktop background image - Activate Num Lock
janhalen commented 2026-01-12 09:48:16 +00:00 (Migrated from github.com)

Yes, we definately need to define the final capabilites for the end-goal of the system in more detail. But lets work iteratively, instead of blocking Hackathon or PoC work until at "complete" definition has been agreed upon and verified.

To start a dialogue about this, I recommend we open a couple of User-story issues, that describes the value delivered by such technical tasks as described above. A user-story is an iterative process and a dialogue... so I recommend that we get started ASAP and that we invite more participants to discussing the story. @ChatBotBerg any inputs for how this could be done in an OS2 context?

I can help by creating a couple of stories that will encompass the above technical tasks... and add the first relevant question as a comment to get the discussion started. @agnetemoos: How do you like that way of working?

Yes, we definately need to define the final capabilites for the end-goal of the system in more detail. But lets work iteratively, instead of blocking Hackathon or PoC work until at "complete" definition has been agreed upon and verified. To start a dialogue about this, I recommend we open a couple of User-story issues, that describes the value delivered by such technical tasks as described above. A user-story is an iterative process and a dialogue... so I recommend that we get started ASAP and that we invite more participants to discussing the story. @ChatBotBerg any inputs for how this could be done in an OS2 context? I can help by creating a couple of stories that will encompass the above technical tasks... and add the first relevant question as a comment to get the discussion started. @agnetemoos: How do you like that way of working?
janhalen commented 2026-01-12 11:40:23 +00:00 (Migrated from github.com)

@agnetemoos: I have created this user-story issue to start the dialogue and highlight how this way of working with stories before technical tasks can deliver hideen value and avoid making the wrong dessicions at a specific time in a products life cycle.

@agnetemoos: I have created [this user-story issue](https://github.com/OS2sandbox/openclient-poc/issues/25) to start the dialogue and highlight how this way of working with stories before technical tasks can deliver hideen value and avoid making the wrong dessicions at a specific time in a products life cycle.
agnetemoos commented 2026-01-13 07:59:35 +00:00 (Migrated from github.com)

@agnetemoos: I have created this user-story issue to start the dialogue and highlight how this way of working with stories before technical tasks can deliver hideen value and avoid making the wrong dessicions at a specific time in a products life cycle.

Great idea. Lets do that.
I will produce a handful of user stories. I will ask the OS2BorgerPC koordinationsgruppe to contribute. Perhaps we can allocate time to work on them at our next meeting on February 2.

> [@agnetemoos](https://github.com/agnetemoos): I have created [this user-story issue](https://github.com/OS2sandbox/openclient-poc/issues/25) to start the dialogue and highlight how this way of working with stories before technical tasks can deliver hideen value and avoid making the wrong dessicions at a specific time in a products life cycle. Great idea. Lets do that. I will produce a handful of user stories. I will ask the OS2BorgerPC koordinationsgruppe to contribute. Perhaps we can allocate time to work on them at our next meeting on February 2.
janhalen commented 2026-03-11 09:35:43 +00:00 (Migrated from github.com)

As a starting point of getting to grips with "how to operate" -
I will recommend this video 👇🏻

⚠️ Be aware that bootc and the ecosystem around it (podman, systemd, greenboot, bcvk etc.) is a modern iteratively developed technology, so the video, being one year old, could be outdated in some technical details..

bootc: GitOps for Noobs

bootc -GitOps for Noobs

This video runs through the concepts and moving parts of a system based on the reference architecture I have recommended!

@dekov @agnetemoos @ChatBotBerg : you might be able to use this video-guide?
As a starting point of getting to grips with "how to operate" - I will recommend this video 👇🏻 > ⚠️ Be aware that bootc and the ecosystem around it (podman, systemd, greenboot, bcvk etc.) is a modern iteratively developed technology, so the video, being one year old, could be outdated in some technical details.. ### bootc: GitOps for Noobs [![bootc -GitOps for Noobs](https://img.youtube.com/vi/5ZN_7NDvavY/0.jpg)](https://www.youtube.com/watch?v=5ZN_7NDvavY) This video runs through the concepts and moving parts of a system based on the reference architecture I have recommended! ###### @dekov @agnetemoos @ChatBotBerg : you might be able to use this video-guide?
Sign in to join this conversation.
No description provided.