This repository has been archived by the owner on Sep 12, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 96
iRODS transfer support for application_to_provider #318
Merged
steve-gregory
merged 15 commits into
cyverse:xylotomous-xenops
from
c-mart:application-to-provider-irods-xfer
Apr 13, 2017
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
88b295c
arguments, docs, parsing for iRODS xfer support
a81af85
Abstracted out migrate_image_data() function from a particular method…
43e6c92
MVP implementation of iRODS xfer support, needs testing
b4ec1ac
Implemented and minimally tested
e365d60
more caveats
df6bdfe
removing todo
977a2be
fixing pip requirements
1c97e4f
New features in changelog
73ae24d
rtwo version increment
8c0ffd6
Warning user about checksum issue
9440eaa
Move migrate_image_data() out of main() function and explicitly pass …
d06513f
docstring for migrate_image_data_irods()
7c91f5d
migrate_image_data_irods() now returns True if success
91dbf9d
refactoring sprov and dprov to src and dst for succinctness
708b7d5
More appropriate error message
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would seem that only one of the two collections would be required if someone wanted to go
iRODS -> Glance
orGlance -> iRODS
?Just curious how far we are away from Many-to-many relationship 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@steve-gregory, I don't know what you mean. Downloading an image from provider A using iRODS and then uploading it to provider B using Glance, and vice versa? I haven't built support for that. Regardless of which storage back-end is in use, why would someone want to do that over Glance's preferred way of using the API for the entire migration? The only reason to use iRODS transfer is for the speedup of iRODS data object copy, and for that you wouldn't want to be uploading or downloading image data via Glance API.
I don't know what you mean by "many-to-many relationship" in this context. Can you please clarify?