-
Notifications
You must be signed in to change notification settings - Fork 1
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
Sharing data across FAIRiCUBE UCs on EOXHub #80
Comments
Related to #61 |
I have now tried both routes on the jupyterlab terminal: pip install awscli s3cmd cp s3://source-bucket-name/file.txt s3://destination-bucket-name/file.txt I guess this has something to do with privileges / access rights in both buckets (by design), I now have to find out how to get something like scp user@destination_server:file user@target_server:file |
@jetschny sorry to hear your struggle. We're trying to improve and simplify the setup based on your feedback. For this we've implemented a new feature that allows us to mount 2 buckets in parallel. We've configured this for testing in the fairicubeuc1 profile and mounted the common bucket to Please have a look and let us know if we should roll out this configuration to the other use case and profiles and maybe the training profiles as well. In general we recommend using the buckets to share data as the shared folder is also used to store system files and wrong use might lead to side effects. I've update the documentation accordingly (see https://fairicube--10.org.readthedocs.build/en/10/user_guide/storage/). The Please let me know if you want me to adjust any configuration like for example directory names where buckets are mounted. |
Hello @Schpidi, I think it is a viable solution. Side note: Having now multiple profiles, I realized it is not obvious to know which one is active while inside the workspace. For example, which s3 bucket is mounted to |
@jetschny since we didn't get an answer from you we simply assume that the setup is ok and will roll it out the configuration to mount the common bucket to all 8 currently configured teams and all profiles therein. @mari-s4e thanks for your feedback. Yes, we could easily change the name of the directory where the team or use case specific bucket is mounted. However, I'd like to point out that all scripts and notebooks would need to be updated to reflect that change and in addition you couldn't easily write a script that works across use cases anymore. I'd recommend to simply put an empty file in the root of the bucket that shows the use case name instead. Anyway, please let me know if you still want to change the name. |
I asked @BachirNILU to test as I was / am on schoolvacation break. As it seems to work fine and is confirmend by Maria, it is good to have this rolled out to all profiles. Many thanks. if there is no further development missing (apart from changing the name of the bucket), we can close the ticket? |
Hi @Schpidi I see your point on losing interoperability between profiles ;) no need to change the name |
I have just had a meeting with @mari-s4e to confirm that everything works. |
the buckets are now configured for all profiles |
Thanks @eox-cs1! |
In preparation of the training days, I am testing how to share / exchange data from one UC to another.
as described in https://fairicube--8.org.readthedocs.build/en/8/guide/storage/#file-storage
there is the
shared folder mounted under /shared/fairicube/
but the folder has only read-access which makes it impractical for adding new data for exchange. can this folder please get write rights as well?
common FAIRiCUBE bucket
where I once found the email instructions
The new S3 bucket (s3://fairicube) is accessible using standard S3 tools and got created in eu-central-1.
Access can be verified/tested e.g. in the Terminal using (in one line):
s3cmd ls --access_key=${S3_FAIRICUBE_STORAGE_KEY} --secret_key=${S3_FAIRICUBE_STORAGE_SECRET} --region=eu-central-1 s3://${S3_FAIRICUBE_STORAGE_BUCKET}
but how to actually us the common FiC bucket in command line commandos to copy files is something that I have to find out. Both surely needs to be documented somewhere.
the "team-extra" folder? What is this? A shared folder across members of a use case? could be included in the RtD if seen relevant.
The text was updated successfully, but these errors were encountered: