Skip to content
Snippets Groups Projects
  1. Nov 20, 2024
  2. Nov 15, 2024
  3. Nov 14, 2024
  4. Oct 30, 2024
    • Josef Smrčka's avatar
      Merge branch 'jsmrcka-volume-migration-speedup' into 'master' · bd59ded5
      Josef Smrčka authored
      feat: speed-up volume migration procedure
      
      See merge request !34
      bd59ded5
    • Josef Smrčka's avatar
      feat: speed-up volume migration procedure · fd5828a3
      Josef Smrčka authored
      Modified the volume migration procedure - add option to skip the
      deep-copy step, in order to speed up the procedure:
        - old steps:
          - create src snapshot
          - delete dst volume
          - clone snapshot
          - flatten clone
          - deep-copy clone to dst volume
          - delete clone
          - delete snapshot
        - new steps:
          - create src snapshot
          - delete dst volume
          - clone snapshot to dst volume
          - flatten clone
          - delete snapshot
      fd5828a3
  5. Oct 15, 2024
  6. Oct 07, 2024
  7. Oct 04, 2024
    • Josef Smrčka's avatar
      Merge branch 'jsmrcka-migrations' into 'master' · 5c071e90
      Josef Smrčka authored
      feat: change volume migration procedure
      
      See merge request !31
      v1.7.0
      5c071e90
    • Josef Smrčka's avatar
      feat: change volume migration procedure · 970bb101
      Josef Smrčka authored
      Refactor volume migration.
      
      Split the volume migration into 2 separate steps:
      - `step1`: create snapshot of source volume
      - `step2`: clone snapshot + flatten clone + copy clone to destination
        volume
      
      Introduce a parameter which configures, whether `step2` is done while
      the VM is off.
      
      Original (non-default) flow:
      1. shutoff source VM
      2. perform `step1` + `step2` (originally not split)
      3. start source VM
      4. ...
      
      New default flow:
      1. shutoff source VM
      2. perform `step1`
      3. start source VM
      4. perform `step2`
      5. ...
      
      Rationale: There is no reason to keep the source VM off once the
      snapshot is created. The VM is started after the migration anyway, so
      the source and destination volumes will diverge eventually. The new
      default approach aims to reduce the time the VM is off.
      970bb101
  8. Sep 30, 2024
  9. Sep 20, 2024
  10. Aug 28, 2024
  11. Aug 22, 2024
  12. Aug 08, 2024
  13. Aug 07, 2024
  14. Aug 05, 2024
  15. Jul 25, 2024
Loading