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.

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

Add configuration option to write irods::access_time metadata to new files #27

Closed
JustinKyleJames opened this issue May 9, 2019 · 1 comment
Assignees

Comments

@JustinKyleJames
Copy link
Collaborator

To support the storage tiering interface with the time constraint violation policy while in direct mode, add a configuration option to add the irods::access_time metadata to the file.

When in policy mode this is performed by the PEP but policy mode is slower than direct mode. This enhancement will allow the use of storage tiering (time violation only) while using direct mode.

@JustinKyleJames JustinKyleJames self-assigned this May 9, 2019
JustinKyleJames added a commit that referenced this issue May 9, 2019
Configuration parameters are metadata_key_for_storage_tiering_time_violation and set_metadata_storage_tiering_time_violation
JustinKyleJames added a commit that referenced this issue May 9, 2019
Update readme with configuration settings to set the update time on data objects for storage tiering compatability when using direct mode.
JustinKyleJames added a commit that referenced this issue May 9, 2019
Configuration parameters are metadata_key_for_storage_tiering_time_violation and set_metadata_storage_tiering_time_violation
Update readme with configuration settings to set the update time on data objects for storage tiering compatability when using direct mode.
JustinKyleJames added a commit that referenced this issue May 9, 2019
Configuration parameters are metadata_key_for_storage_tiering_time_violation and set_metadata_storage_tiering_time_violation
Update readme with configuration settings to set the update time on data objects for storage tiering compatability when using direct mode.
JustinKyleJames added a commit that referenced this issue May 9, 2019
Configuration parameters are:
* metadata_key_for_storage_tiering_time_violation
* set_metadata_storage_tiering_time_violation.

Update readme with configuration settings to set the update time on data objects for storage tiering compatability when using direct mode.

Also fixed issues [#23][#25][#26].
@JustinKyleJames
Copy link
Collaborator Author

Changes made. Closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant