distribution client enhancements needed
summary list of distribution client enhancements needed / desired (based on conversation with paul 4/17)
- md5sum : client is not currently checking the MD5sum
- block / delay update : the client needs to download and insert data for the stages in the correct sequence (chip->camera->fake, etc). The client needs to delay update of one stage until preceding stages are done.
- munge/don't munge paths : currently, the client modifies the resulting file names based on a desired workdir template. it should be optional to keep the nebulous names used on the server side.
- handshaking : the client needs to send back the handshaking info to the server so the server can auto-clear its outgoing bundles
Change History
(4)
| Owner: |
changed from Paul Price to bills
|
| Severity: |
normal → critical
|
| Status: |
new → assigned
|
| Cc: |
Paul Price added; bills removed
|
| Resolution: |
→ fixed
|
| Status: |
assigned → closed
|
* md5sum : client is not currently checking the MD5sum
Fixed now
* block / delay update : the client needs to download and insert data for the * stages in the correct sequence (chip->camera->fake, etc). The client needs to delay update of one stage until preceding stages are done.
I'm not sure this is necessary. The update system will not queue files for
processing unless the depenedent runs exist and are in full state.
* munge/don't munge paths : currently, the client modifies the resulting file names based on a desired workdir template. it should be optional to keep the nebulous names used on the server side.
This is in progress
* handshaking : the client needs to send back the handshaking info to the server so the server can auto-clear its outgoing bundles
If the recieveSource has a non-null status product, an empty fileset with status information in the product list data will be posted to that data store product.
This is only done of the download succeeds. We need to think about the critera
that will be used to notify the server of errors.