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

Handle actions for different target TM_MADs #3244

Closed
7 tasks
kvaps opened this issue Apr 17, 2019 · 3 comments
Closed
7 tasks

Handle actions for different target TM_MADs #3244

kvaps opened this issue Apr 17, 2019 · 3 comments

Comments

@kvaps
Copy link
Contributor

kvaps commented Apr 17, 2019

Description

Following this discussion. We've decided that better way to implement cross datastore transfer actions is to add check for action.<TM_MAD> file in the source tm driver directory. Where TM_MAD is destination datastore variable.

Use case

This change will allow to implement actions to transfer volumes between datastores with different TM_MADs. eg. copy images from shared to fs_lvm and from ceph to shared datastores and etc.

Interface Changes

If source datastore have TM_MAD=ssh, destination datastore TM_MAD=fs_lvm and user started clone operation. tm_mad.rb should check is tm/ssh/clone.fs_lvm file exist (it might be symlink), and call it instead standard one. If not exist, then call standard action tm/ssh/clone.

The same goes for all other tm actions and drivers.

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches
@kvaps kvaps changed the title Implement hook to handle different target TM_MAD actions Handle actions for different target TM_MADs Apr 17, 2019
@xorel xorel self-assigned this Jul 18, 2019
xorel added a commit to xorel/one that referenced this issue Jul 23, 2019
xorel added a commit to xorel/one that referenced this issue Jul 23, 2019
xorel added a commit to xorel/one that referenced this issue Jul 23, 2019
xorel added a commit to xorel/one that referenced this issue Jul 23, 2019
xorel added a commit to xorel/one that referenced this issue Jul 24, 2019
xorel added a commit to xorel/one that referenced this issue Jul 24, 2019
xorel added a commit that referenced this issue Jul 24, 2019
xorel added a commit to OpenNebula/docs that referenced this issue Aug 6, 2019
xorel added a commit that referenced this issue Aug 6, 2019
@xorel
Copy link
Member

xorel commented Aug 6, 2019

PRs:
one: #3574
infra: https://github.com/OpenNebula/infra/pull/303
docs: OpenNebula/docs#716

all to master

@xorel
Copy link
Member

xorel commented Aug 6, 2019 via email

rsmontero pushed a commit to OpenNebula/docs that referenced this issue Aug 7, 2019
@rsmontero
Copy link
Member

Every thing is now merged in master, closing...

@rsmontero rsmontero added this to the Release 5.10 milestone Aug 7, 2019
xorel added a commit to xorel/one that referenced this issue Oct 8, 2019
xorel added a commit to xorel/one that referenced this issue Oct 8, 2019
* reintroduce shared/mvds as mvds.ssh (deleted by mistake)
* adapt also shared/ln
xorel added a commit that referenced this issue Nov 5, 2019
Don't require the image datastore to be available on the hypervisor but still
utilize qcow2 format features.
xorel added a commit that referenced this issue Nov 5, 2019
Don't require the image datastore to be available on the hypervisor but still
utilize qcow2 format features.
xorel added a commit that referenced this issue Nov 5, 2019
Don't require the image datastore to be available on the hypervisor
but still utilize qcow2 format features.
xorel added a commit that referenced this issue Nov 5, 2019
xorel added a commit that referenced this issue Nov 5, 2019
xorel added a commit that referenced this issue Nov 6, 2019
xorel added a commit that referenced this issue Nov 6, 2019
xorel added a commit that referenced this issue Nov 6, 2019
xorel added a commit that referenced this issue Nov 6, 2019
xorel added a commit that referenced this issue Nov 6, 2019
xorel added a commit that referenced this issue Nov 6, 2019
xorel added a commit to xorel/one that referenced this issue Nov 12, 2019
Don't evaluate presence of the SRC_SNAP_DIR on hypervisor,
but rather on the frontend to prevent race condition.
xorel added a commit to xorel/one that referenced this issue Nov 12, 2019
Don't evaluate presence of the SRC_SNAP_DIR on hypervisor,
but rather on the frontend to prevent race condition.
rsmontero pushed a commit that referenced this issue Nov 12, 2019
Don't evaluate presence of the SRC_SNAP_DIR on hypervisor,
but rather on the frontend to prevent race condition.
rsmontero pushed a commit that referenced this issue Oct 4, 2024
Signed-off-by: dcarracedo <dcarracedo@opennebula.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants