[INSTRM-347] Provide file service for images Created: 21/Apr/18 Updated: 01/May/18 |
|
| Status: | Open |
| Project: | Instrument control development |
| Component/s: | ics_production |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | cloomis | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
[ I did not see anything in ics_doc or ics_ansible – sorry if I missed it. ] We need to provide file service for the OCS archiving process to pick up from to. I suppose other transports would work, but ftp is a tested one. Based on Eric's recommendation I have been using vsftpd, with username daquser. I think we should publish all of /data. We do send the full pathname w.r.t. that root, so are pretty flexible. [ Note high priority: we need this by 2018-04-23 ] |
| Comments |
| Comment by cloomis [ 01/May/18 ] |
|
This was implemented and tested on shell-ics, but with the pfs account. Eric will know the details. I confess that I would have used sense=allow, and with a dedicated vsftp user. If changed, need to let Eric know so that the OCS side is changed to match. |