Skip to content
This repository has been archived by the owner on May 17, 2024. It is now read-only.

Include output files in time/cost calculations #17

Open
vaniisgh opened this issue Aug 12, 2019 · 0 comments
Open

Include output files in time/cost calculations #17

vaniisgh opened this issue Aug 12, 2019 · 0 comments
Labels
priority: low Low priority status flag: discuss Needs input from various people status: on hold Won't be fixed for now type: feature New feature or request type flag: spec change Proposed change requires spec changes workload: days Likely takes days to resolve

Comments

@vaniisgh
Copy link
Collaborator

vaniisgh commented Aug 12, 2019 •
edited by uniqueg
Loading

Is your feature request related to a problem? Please describe.
Currently there is no provision to assign DRS instances for writing output files, partly because the current DRS specs do not include an endpoint for adding new data and coining new DRS IDs. This restricts the accuracy of (transfer) time and cost estimates and should eventually be considered.

Several issues need to be discussed/handled in order to come up with a detailed solution:

  • Can the size of output objects be estimated? How?
  • How can output objects be assigned DRS IDs (for them to be used in subsequent steps)?
@uniqueg uniqueg changed the title Handle Output Files Handle output files Sep 11, 2019
@uniqueg uniqueg removed hold labels Feb 20, 2020
@uniqueg uniqueg changed the title Handle output files Include output files in time/cost calculations Feb 23, 2020
@uniqueg uniqueg added priority: low Low priority status flag: discuss Needs input from various people status: on hold Won't be fixed for now type flag: spec change Proposed change requires spec changes type: feature New feature or request workload: days Likely takes days to resolve labels Feb 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
priority: low Low priority status flag: discuss Needs input from various people status: on hold Won't be fixed for now type: feature New feature or request type flag: spec change Proposed change requires spec changes workload: days Likely takes days to resolve
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@uniqueg @vaniisgh