/qubes-issues

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

Consider keeping VM API compatibility with R3.x #1812

Open
marmarek opened this Issue Mar 6, 2016 · 0 comments

Comments

Assignees

@marmarek marmarek

Labels
Projects
None yet
Milestone
  Release 4.1
2 participants
@marmarek @andrewdavidwong
@marmarek
Member

marmarek commented Mar 6, 2016

If possible, it would be good to keep backward API compatibility R3.x->R4.0. In other words, keep it possible to start (template) VM from R3.x on R4.0 without any change inside of its root.img.

The plan minimum is to have network (and GUI) working in such a case to be able to update the template. Otherwise upgrade procedure will be much more fragile and complex (which will be already quite complex because of qubes.xml format change).

This is mainly about QubesDB entries.

@marmarek marmarek added C: core P: major task labels Mar 6, 2016

@marmarek marmarek added this to the Release 4.0 milestone Mar 6, 2016

@marmarek marmarek self-assigned this Mar 6, 2016

marmarek added a commit to marmarek/old-qubes-core-admin that referenced this issue Mar 7, 2016

@marmarek
ext/r3compatibility: create R3.x QubesDB entries 
This allows the user to start VM based on "old" system (from R3.x) in
R4.0. For example after restoring from backup, or migration. This also
makes upgrade instruction much easier - no need complex recovery
instruction if one upgrade dom0 before upgrading all the templates.

QubesOS/qubes-issues#1812
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
5a03cb8

marmarek added a commit to marmarek/old-qubes-core-admin that referenced this issue Mar 7, 2016

@marmarek
ext/r3compatibility: move old firewall code to R3.x compat layer 
QubesOS/qubes-issues#1812
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
b261f90

marmarek added a commit to marmarek/old-qubes-core-admin that referenced this issue Mar 7, 2016

@marmarek
ext/r3compatibility: features/services 
QubesOS/qubes-issues#1812
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
d98bac0

woju added a commit to woju/qubes-core-admin that referenced this issue Mar 11, 2016

@marmarek @woju
ext/r3compatibility: create R3.x QubesDB entries 
This allows the user to start VM based on "old" system (from R3.x) in
R4.0. For example after restoring from backup, or migration. This also
makes upgrade instruction much easier - no need complex recovery
instruction if one upgrade dom0 before upgrading all the templates.

QubesOS/qubes-issues#1812
976c374

woju added a commit to woju/qubes-core-admin that referenced this issue Mar 11, 2016

@marmarek @woju
ext/r3compatibility: move old firewall code to R3.x compat layer 
QubesOS/qubes-issues#1812
8018e7d

woju added a commit to woju/qubes-core-admin that referenced this issue Mar 11, 2016

@marmarek @woju
ext/r3compatibility: features/services 
QubesOS/qubes-issues#1812
ee09394

woju added a commit to woju/qubes-core-admin that referenced this issue Mar 21, 2016

@marmarek @woju
ext/r3compatibility: create R3.x QubesDB entries 
This allows the user to start VM based on "old" system (from R3.x) in
R4.0. For example after restoring from backup, or migration. This also
makes upgrade instruction much easier - no need complex recovery
instruction if one upgrade dom0 before upgrading all the templates.

QubesOS/qubes-issues#1812
afd4573

woju added a commit to woju/qubes-core-admin that referenced this issue Mar 21, 2016

@marmarek @woju
ext/r3compatibility: move old firewall code to R3.x compat layer 
QubesOS/qubes-issues#1812
c9fd57e

woju added a commit to woju/qubes-core-admin that referenced this issue Mar 21, 2016

@marmarek @woju
ext/r3compatibility: features/services 
QubesOS/qubes-issues#1812
b6d8c7f

marmarek added a commit to marmarek/old-qubes-core-admin that referenced this issue Sep 8, 2016

@marmarek
Revert "qubes/vm/qubesvm: remove prefixes from qubesdb keys" 
There is no point in changing *public API* for just a change without any
better reason. It turned out most of those settings will be the same in
Qubes 4.0, so keep names the same.

This reverts commit 2d6ad3b.

QubesOS/qubes-issues#1812
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
d5a41e8

marmarek added a commit to marmarek/old-qubes-core-admin that referenced this issue Sep 8, 2016

@marmarek
qubes/vm: make VM QubesDB interface as much compatible as possible 
All the base keys can be kept easily the same, so do it.

QubesOS/qubes-issues#1812
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
aa0674e

@andrewdavidwong andrewdavidwong modified the milestones: Release 4.0, Release 4.1 Mar 31, 2018

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