-
Notifications
You must be signed in to change notification settings - Fork 492
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
Milestone
Comments
kvaps
changed the title
Implement hook to handle different target TM_MAD actions
Handle actions for different target TM_MADs
Apr 17, 2019
xorel
added a commit
that referenced
this issue
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
PRs: all to master |
Yes, should work for every TM action if the action script exists.
…On Tue, Aug 6, 2019 at 3:35 PM kvaps ***@***.***> wrote:
@xorel <https://github.com/xorel> will it also work for cpds mvds actions?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3244?email_source=notifications&email_token=AAIMEBS4GPN3GCJBMVLACG3QDF43DA5CNFSM4HGT7KSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3VE6CI#issuecomment-518672137>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIMEBVZY3UUHEMAFBYUV4DQDF43DANCNFSM4HGT7KSA>
.
--
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Jan Orel
Cloud Engineer at OpenNebula Systems
OpenNebula.Systems | @OpenNebula
--
Confidentiality Warning: The information contained in this e-mail and
any accompanying documents, unless otherwise expressly indicated, is
confidential and privileged, and is intended solely for the person
and/or entity to whom it is addressed (i.e. those identified in the
"To" and "cc" box). They are the property of OpenNebula.Systems S.L..
Unauthorized distribution, review, use, disclosure, or copying of this
communication, or any part thereof, is strictly prohibited and may be
unlawful. If you have received this e-mail in error, please notify us
immediately by e-mail at abuse@opennebula.systems and delete the
e-mail and attachments and any copy from your system. OpenNebula's
thanks you for your cooperation.
|
rsmontero
pushed a commit
to OpenNebula/docs
that referenced
this issue
Aug 7, 2019
Every thing is now merged in master, closing... |
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
rsmontero
pushed a commit
that referenced
this issue
Oct 8, 2019
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
rsmontero
pushed 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
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
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
tofs_lvm
and fromceph
toshared
datastores and etc.Interface Changes
If source datastore have
TM_MAD=ssh
, destination datastoreTM_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
The text was updated successfully, but these errors were encountered: