Skip to content
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.

Sign up for GitHub

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

Jump to bottom

File modification / deletion in AG disk-polling driver #73

Open
iychoi opened this issue Mar 13, 2014 · 3 comments
Open

File modification / deletion in AG disk-polling driver #73

iychoi opened this issue Mar 13, 2014 · 3 comments
Assignees
@iychoi

Comments

@iychoi
Copy link
Member

iychoi commented Mar 13, 2014

When there's a file modification or deletion at target directory, AG disk-polling driver needs to update or remove MS entry properly.
@iychoi iychoi self-assigned this Mar 13, 2014
@iychoi
Copy link
Member Author

iychoi commented Mar 13, 2014

Implemented and committed to GitHub. But still need to test.

  • Possible error : file modification notification may not be in the correct order. (If a parent directory is removed).
  • Possible solution : change parameters to nftw().

@jcnelson
Copy link
Member

I'm looking into this as part of the AG refactoring (not committed yet). The driver will be able to signal the AG to republish files. I'll update the driver to do so.

jcnelson pushed a commit that referenced this issue Aug 28, 2014
The Big AG Refactor, WIP.
da8c79d 
* The AG now keeps track of all path metadata.  Previously, drivers had
done this.
* The AG keeps path metadata consistent automatically.  Previously,
drivers had to do this.  This fixes issues #73 and #74.
* The AG will match "query_type" file/directory tag attributes to the
appropriate driver to load and use to access information.  The AG will
ship with all drivers as a whole unit, and only download the spec file
from the MS.
* Drivers are kept as separate from the AG as possible.  The AG
implements a stable driver API, and drivers no longer interact with
Syndicate-specific data strutures (like manifests).
* Revamped driver API.  Handle manifests separately from blocks, and
have the AG take care of signing, verifying, etc. and filling in the
appropriate information.
* The AG returnes hashed blocks.  This fixes issue #62.

More to come: bringing all the drivers up to speed, more testing, and
updates to syntool.py to support pushing just the spec file.  Also,
under AG/tools, we'll put utilities for generating specfiles from more
easily-managed data structures (because I doubt curators will want to
write raw XML, in specifically the way the AG expects).
@jcnelson
Copy link
Member

Partially addressed by da8c79d.

Now, to re-factor the disk_polling driver to use the new API...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iychoi iychoi

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jcnelson @iychoi