openhpc / submissions

OpenHPC Component Submissions Project
8 stars 2 forks source link

rclone #41

Closed likueimo closed 4 years ago

likueimo commented 4 years ago

Software Name

rclone


Public URL

https://rclone.org/ https://github.com/rclone/rclone


Technical Overview

rclone is a very popular and simple command line tool for user download or upload files from cloud storage (ex: Google Drive, Amazon Drive, S3, Dropbox).
It offer an universal way modify cloud storage.
There are several HPC centers already installed rclone.

for example

NYU HPC: https://wikis.nyu.edu/display/NYUHPC/Transferring+files+between+the+HPC+Prince+Cluster+and+Google+Drive

berkeley HPC: http://research-it.berkeley.edu/services/high-performance-computing/transferring-data-between-savio-and-your-bdrive-google-drive

utah HPC: https://www.chpc.utah.edu/documentation/software/rclone.php


Latest stable version number

1.48.0, 2019/06/16 https://github.com/rclone/rclone/releases/tag/v1.48.0


Open-source license type

This is free software under the terms of MIT the license ref : https://github.com/rclone/rclone/blob/master/COPYING


Relationship to component?

If other, please describe:


Build system

If other, please describe:

build with golang

Does the current build system support staged path installations? For example: make install DESTIR=/tmp/foo (or equivalent)


Does component run in user space or are administrative credentials required?


Does component require post-installation configuration.

If yes, please describe briefly:


If component is selected, are you willing and able to collaborate with OpenHPC maintainers during the integration process?


Does the component include test collateral (e.g. regression/verification tests) in the publicly shipped source?

If yes, please briefly describe the intent and location of the tests.


Does the component have additional software dependencies (beyond compilers/MPI) that are not part of standard Linux distributions?

If yes, please list the dependencies and associated licenses.


Does the component include online or installable documentation?

If available online, please provide URL. https://rclone.org/install/

Linux installation from precompiled binary or Install from source


[Optional]: Would you like to receive additional review feedback by email?

- [x] yes - [ ] no
adrianreber commented 4 years ago

@likueimo On CentOS based OpenHPC installations EPEL is activated and already contains rclone. As rclone is not built against any optimized compiler or other libraries I am just curious why it should be part of OpenHPC if it is already available via EPEL.

likueimo commented 4 years ago

@adrianreber Thanks your fast reply! I am a very new HPC system admin, so I am less experience and maybe not accurate knowledge of HPC.

  1. Sorry, I do not notice that EPEL repo already contains rclone.
  2. Althoght I find that OpenHPC contains "singularity" #11 and so is EPEL repo. And I believe that singularity is also not built against any optimized compiler (build by golang).
  3. I learn a lot of packages from OpenHPC repo. So I just think that if OpenHPC include rclone, maybe someone like me will learn rclone from OpenHPC repo.
  4. It's ok if not include rclone :) It's just minor suggestion :)
adrianreber commented 4 years ago
1. Sorry, I do not notice that EPEL repo already contains rclone.

No need to apologize. I was just asking.

2. Althoght I find that OpenHPC contains "singularity" #11 and so is [EPEL repo](https://centos.pkgs.org/7/epel-x86_64/singularity-3.2.1-1.1.el7.x86_64.rpm.html). And I believe that singularity is also not built against any optimized compiler (build by golang).

Interesting example. With singularity I think it was actually that OpenHPC first provided it before EPEL.

3. I learn a lot of packages from OpenHPC repo. So I just think that if OpenHPC include rclone, maybe someone like me will learn rclone from OpenHPC repo.

My questions was just to make sure to avoid unnecessary work without much benefit.

4. It's ok if not include rclone :) It's just minor suggestion :)

I am no authority. I was just trying to understand you request better. Thanks for your clarification. Let's see what the others are thinking about it.

likueimo commented 4 years ago
Interesting example. With singularity I think it was actually that OpenHPC first provided it before EPEL.

Yes, you are right ! I forget to check the build time of rpm !

Thanks your fast reply :)

koomie commented 4 years ago

Hello @likueimo. One additional comment on this for other distributions. For our 2.0 release, in addition to continue to do builds on CentOS (and leveraging EPEL as @adrianreber mentioned), we will be switching to the Leap 15 variant of SUSE. I have a system with that booted now, and can confirm that rclone is also available on that distro.

sms003:~ # cat /etc/os-release 
NAME="openSUSE Leap"
VERSION="15.1 "
ID="opensuse-leap"
ID_LIKE="suse opensuse"
VERSION_ID="15.1"
PRETTY_NAME="openSUSE Leap 15.1"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.1"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
sms003:~ # rclone --version
2019/09/11 07:51:03 NOTICE: Config file "/root/.config/rclone/rclone.conf" not found - using defaults
rclone v1.39
- os/arch: linux/amd64
- go version: go1.12.2

So, if there is no specific need to do a build that is different than what the distro(s) and EPEL are providing, I'd suggest we drop this addition request if you are ok with that.

likueimo commented 4 years ago

@koomie Thanks for replying ! Yes, I think it could be dropped. So I close this issue ~