Skip to content

Deferred template - #458

Open
ben-grande wants to merge 5 commits into
QubesOS:mainfrom
ben-grande:deferred-template
Open

Deferred template#458
ben-grande wants to merge 5 commits into
QubesOS:mainfrom
ben-grande:deferred-template

Conversation

@ben-grande

Copy link
Copy Markdown
Contributor

For: QubesOS/qubes-issues#8070
Requires: QubesOS/qubes-core-admin-client#496

See individual commits messages.

@ben-grande

Copy link
Copy Markdown
Contributor Author

Marta, from all the "deferred template" PRs, I think this one is where most discussion regarding user facing changes will happen. Especially these commits:

  • 8129810 -> Some features needs to be queried from the active_template and others from the next/deferred template property.
  • d6dd7d9 -> No indication of the name of the active template. Where do you think it is a good idea to put? I discarded the idea of putting it in the "template" column because I think it will be two big to have long strings there.

@qubesos-bot

qubesos-bot commented Aug 18, 2026

Copy link
Copy Markdown

OpenQA test summary

Complete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2026082501-devel-archlinux&flavor=templates

Test run included the following:

Installing updates failed, skipping the report!

With a server that supports deferred template, clients don't need to
worry about the qube state to block template change, in this case, there
were only things to remove, as showing "active_template" is irrelevant
here, the user just wants to change the "template" property to a new
value.

For: QubesOS/qubes-issues#8070
Requires: QubesOS/qubes-core-admin#870
Requires: QubesOS/qubes-core-admin-client#496
There is now two warnings for the template value, but they rely on
different labels, as it makes it easier to enable them. On the other
hand, I could not make the labels be as close to each other, so the
label on the last column is much farther away than what would be
considered beautiful.
As the server gained support for deferred template, the client doesn't
need to worry about the qube state to block template change.
Some features are relevant for the current running qube, such as
seamless mode on Windows, in that case, the client needs to query from
the "active_template". In other cases, when it is related to a
responsibility that is only gained on the next boot, such as boot mode,
the query is made targeting the "template" property.
Ideally, we'd inform with icon plus a text description that the
"active_template" is different than the "template" property. For now,
only the VM settings does that, but still doesn't show the
"active_template", as the labels are controlled by the UI files.
@ben-grande

Copy link
Copy Markdown
Contributor Author

Once this PR is merged, it will unblock:

@ben-grande

Copy link
Copy Markdown
Contributor Author

@marmarek

Copy link
Copy Markdown
Member

Unsure what is breaking here:

The test expected running qubes not having dropdowns, which is no longer the case with deferred templates. I'll adjust it.

@ben-grande

Copy link
Copy Markdown
Contributor Author

Thanks. I see now that I click on the "eye" icon, what the needle was expecting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants