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

Renaming VM Should Adjust Dependencies #3892

Closed
qubesissues opened this Issue May 10, 2018 · 5 comments

Comments

Projects
None yet
4 participants
@qubesissues

Qubes OS version:

4.0

Affected component(s):

Qubes Manager


Steps to reproduce the behavior:

Rename a Qube that provides Network.

Expected behavior:

The Qube should take the new name and all Qubes that depend on this Qube should automatically adjust so they use the new name. This happened in 3.2.

Actual behavior:

You are told that you are not allow to rename the Qube!

@3hhh

This comment has been minimized.

Show comment
Hide comment
@3hhh

3hhh May 31, 2018

This behaviour is currently wanted afaik, cf. #3576

3hhh commented May 31, 2018

This behaviour is currently wanted afaik, cf. #3576

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong May 31, 2018

Member

This behaviour is currently wanted afaik, cf. #3576

Can you elaborate? #3576 looks like it's about changing templates, not renaming VMs or changing NetVMs.

Member

andrewdavidwong commented May 31, 2018

This behaviour is currently wanted afaik, cf. #3576

Can you elaborate? #3576 looks like it's about changing templates, not renaming VMs or changing NetVMs.

@3hhh

This comment has been minimized.

Show comment
Hide comment
@3hhh

3hhh Jun 1, 2018

This behaviour is currently wanted afaik, cf. #3576

Can you elaborate? #3576 looks like it's about changing templates, not renaming VMs or changing NetVMs.

You're right, it was #2868

3hhh commented Jun 1, 2018

This behaviour is currently wanted afaik, cf. #3576

Can you elaborate? #3576 looks like it's about changing templates, not renaming VMs or changing NetVMs.

You're right, it was #2868

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jun 2, 2018

Member

You're right, it was #2868

I thought there was a new feature that "renames" by (under the covers) cloning to the new name and removing the old VM. From the user's perspective, this looks like a "rename." I interpreted the original report as saying that this new "rename" feature should automatically adjust dependencies and should be usable on VMs with dependents.

Member

andrewdavidwong commented Jun 2, 2018

You're right, it was #2868

I thought there was a new feature that "renames" by (under the covers) cloning to the new name and removing the old VM. From the user's perspective, this looks like a "rename." I interpreted the original report as saying that this new "rename" feature should automatically adjust dependencies and should be usable on VMs with dependents.

@qubesissues

This comment has been minimized.

Show comment
Hide comment
@qubesissues

qubesissues Jun 19, 2018

I interpreted the original report as saying that this new "rename" feature should automatically adjust dependencies and should be usable on VMs with dependents.
@andrewdavidwong

Yes that would be ideal. Maybe difficult but definitely ideal. Particularly useful when you rename a ProxyVM that 10 Qubes use for connectivity. Now you have to change all of their network VM manually to something else, then change the name, then change all 10 again to the newly-named Qube. Ack!

I interpreted the original report as saying that this new "rename" feature should automatically adjust dependencies and should be usable on VMs with dependents.
@andrewdavidwong

Yes that would be ideal. Maybe difficult but definitely ideal. Particularly useful when you rename a ProxyVM that 10 Qubes use for connectivity. Now you have to change all of their network VM manually to something else, then change the name, then change all 10 again to the newly-named Qube. Ack!

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