Merge branch 'master' of ssh://git-annex.branchable.com
This commit is contained in:
commit
e2a4c49004
5 changed files with 65 additions and 0 deletions
|
@ -0,0 +1,25 @@
|
|||
I have a server on a network (```SRV1```), several clients (```CLI-N```) on another and a ```archive``` repo on AWS Glacier. ```CLI```s can access ```SRV1```, but ```SRV1``` cannot access ```CLI```s network. I'd like to use git-annex to synchronize files between clients and archival on Glacier.
|
||||
|
||||
My current setup:
|
||||
|
||||
- ```SRV1``` contains:
|
||||
- ```transfer``` repository (```T1```)
|
||||
- glacier ```archive``` repo (```G1```)
|
||||
- ```CLI-01``` contains:
|
||||
- ```user files``` repo (```U1```)
|
||||
- ```transfer``` repository (```T1```)
|
||||
- ```CLI-02``` contains:
|
||||
- ```user files``` repo (```U1```)
|
||||
- ```transfer``` repository (```T1```)
|
||||
- ```CLI-N``` (...)
|
||||
|
||||
- **OBS**:
|
||||
- ```SRV1``` uses ```aws tools``` and ```glacier-cli``` to access Glacier
|
||||
- *I would rather not to have to install ```aws tools``` & ```glacier-cli``` on client machines*
|
||||
- ```CLI```s use *ssh/rsync* with secret key to access ```SRV1```
|
||||
|
||||
I would like that ```T1```would serve as a gateway for *a)* synchronizing ```user files``` amongst clients; *a.1)* including moving and dropping files moved to ```archive``` by other clients; *b)* send ```archive``` files to ```G1```; and *c)* get files from ```G1``` and deliver to clients when content is moved out of ```archive```.
|
||||
|
||||
As is seem close to working, but when a ```CLI``` pulls a file out of ```archive``` the recovery processes *(c)* fails. I expected ```transfer``` to fetch the file and then ```CLI``` would sync eventually, but does not seem to happen.
|
||||
|
||||
Is this even possible with this setup? If not, what changes would you recommend for the scenario above to work?
|
|
@ -0,0 +1,14 @@
|
|||
[[!comment format=mdwn
|
||||
username="andrew"
|
||||
avatar="http://cdn.libravatar.org/avatar/acc0ece1eedf07dd9631e7d7d343c435"
|
||||
subject="transfer repos"
|
||||
date="2020-07-05T17:25:49Z"
|
||||
content="""
|
||||
[Transfer](https://git-annex.branchable.com/preferred_content/standard_groups/) repositories unfortunately do not behave that way. You can setup G1 to get content sitting in T1 since T1 will store content until G1 has it. But, in terms of the other direction, doing a `git annex get` from T1 won't ask SRV1 to get a file from G1 (I don't think).
|
||||
|
||||
The easiest way I can think of to achieve what you are looking for would be to create your own special remote on SRV1 (lets call it P1) that proxies the requests the way you need. Using [hook](https://git-annex.branchable.com/special_remotes/hook/) you could create a special remote that when asked for a file, ssh-es into SRV1 and then runs a script on SRV1 that does a `git annex get` on G1. Then, a few hours later, you can do a get again to get the file.
|
||||
|
||||
I think a reasonable workaround, that ensures some measure of safety would be to just create some read-only credentials for your Glacier. Then add your Glacier repo to all the clients, so you can at least do gets from your clients.
|
||||
|
||||
—Andrew
|
||||
"""]]
|
|
@ -0,0 +1,9 @@
|
|||
[[!comment format=mdwn
|
||||
username="jenkin.schibel@286264d9ceb79998aecff0d5d1a4ffe34f8b8421"
|
||||
nickname="jenkin.schibel"
|
||||
avatar="http://cdn.libravatar.org/avatar/692d82fb5c42fc86d97cc44ae0fb61ca"
|
||||
subject="problem fixed itself"
|
||||
date="2020-07-04T03:27:58Z"
|
||||
content="""
|
||||
so for some reason the problem fixed itself. chances are that I am just a noob at how SSL stuff works. If anyone could provide some possible insights as to why this might have happened so that I can learn from it, that would be much appreciated.
|
||||
"""]]
|
|
@ -0,0 +1,9 @@
|
|||
[[!comment format=mdwn
|
||||
username="jenkin.schibel@286264d9ceb79998aecff0d5d1a4ffe34f8b8421"
|
||||
nickname="jenkin.schibel"
|
||||
avatar="http://cdn.libravatar.org/avatar/692d82fb5c42fc86d97cc44ae0fb61ca"
|
||||
subject="problem fixed itself"
|
||||
date="2020-07-04T03:28:26Z"
|
||||
content="""
|
||||
so for some reason the problem fixed itself. chances are that I am just a noob at how SSL stuff works. If anyone could provide some possible insights as to why this might have happened so that I can learn from it, that would be much appreciated.
|
||||
"""]]
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="Ilya_Shlyakhter"
|
||||
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
|
||||
subject="comment 10"
|
||||
date="2020-07-03T19:55:36Z"
|
||||
content="""
|
||||
\"the key generated by import --fast is probably not be the same one generated by a regular import\" -- but that happens already with addurl; is the problem worse here?
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue