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

[Self] Snapshots #3304

Open
24 of 34 tasks
pdonias opened this issue Aug 13, 2018 · 2 comments
Open
24 of 34 tasks

[Self] Snapshots #3304

pdonias opened this issue Aug 13, 2018 · 2 comments

Comments

@pdonias
Copy link
Member

pdonias commented Aug 13, 2018

  • Create snapshot:

    • self users can snapshot their VMs
    • a snapshot uses all the types of resources even if it was created by an admin
    • a self user can't snapshot if there aren't enough resources available
    • an admin is always able to snapshot even if it uses more than the available resources
    • a "snapshot with memory" uses the same resources as a standard snapshot
  • Delete snapshot:

    • self users can only delete their snapshots
    • deleting a snpashot releases its resources
  • Delete VM:

    • deallocate the VM's resources
    • deallocate the snapshots' resources
  • Revert:

    • a self user can revert any snapshot on their VMs
    • reverting a snapshot updates the quotas
    • if reverting a snapshot means using more than the available resources, then the revert fails
    • an admin is always able to revert even if it uses more than the available resources
    • the VM keeps its original resource set (if any) through the reverting process
    • properly re-alloc the snapshot's IP addresses
  • "Snapshot before": (moved to client side, thus behaves as normal snapshot)

  • Remove user from resource set:

  • Add a VM to a resource set:

    • its snapshots are also added to the resource set, except the backup-related ones
    • all the quotas allocations are forced because this is always done by an admin
  • Remove a VM from a resource set

    • all the resource set's subjects have their permissions on the VM revoked
    • all the resource set's subjects have their permissions on the VM's snapshots revoked
    • the VM's resource usage is removed from quotas
    • the VM's snapshots' are removed from the resource set
    • the VM's snapshots' resource usages are removed from the quotas
  • Share a VM within a resource set

    • "share" its snapshots (ie the RS subjects get permissions on them) except the backup-related ones
  • Convert to template

    • self-users can't convert their VMs
    • when an admin converts a VM to a template, the VM is removed from the resource set
  • self-users can create a VM from a snapshot

  • self-users can export a snapshot

  • Recompute all limits:

    • take snapshots into account but
    • ignore backup-related snapshots
@olivierlambert
Copy link
Member

Should not ignore self user snapshot but ignore admin snapshots

@pdonias
Copy link
Member Author

pdonias commented Aug 13, 2018

Check list updated 👍

@badrAZ badrAZ modified the milestones: [Frozen] 19.14, 19.15 Jul 22, 2019
@badrAZ badrAZ modified the milestones: [Frozen] 19.15, 19.16 Aug 8, 2019
@pdonias pdonias modified the milestones: 19.16, [Frozen] 19.17 Aug 22, 2019
@badrAZ badrAZ modified the milestones: [Frozen] 19.17, 19.18 Sep 5, 2019
@badrAZ badrAZ modified the milestones: [Frozen] 19.18, 19.19 Sep 20, 2019
@Rajaa-BARHTAOUI Rajaa-BARHTAOUI modified the milestones: [Frozen] 19.19, 19.20 Sep 27, 2019
@Rajaa-BARHTAOUI Rajaa-BARHTAOUI modified the milestones: 19.20, [Frozen] 19.21 Oct 11, 2019
@Rajaa-BARHTAOUI Rajaa-BARHTAOUI modified the milestones: [Frozen] 19.21, 19.22 Oct 28, 2019
@Rajaa-BARHTAOUI Rajaa-BARHTAOUI modified the milestones: 19.22, 19.23 Nov 22, 2019
@pdonias pdonias removed this from the [Frozen] 19.23 milestone Dec 2, 2019
phil-flex pushed a commit to phil-flex/xen-orchestra that referenced this issue Apr 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment