Details
-
Type:
Improvement
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: ctrl_mpexec
-
Labels:
-
Team:Ops Middleware
Description
It would be useful to have a dedicated API for being able to call CmdLineFwk (or some other activator) from Python code. My own application for this is ap_verify, which in Gen 3 combines some repository management with running a Pipeline on the repository it set up.
Desirable features:
- clear separation of concerns
- ability to edit the Pipeline object before committing to graph generation
- ability to delegate repository details (in particular, the collections to run on) to an existing Butler object
- uniform interface, allowing different activators to serve as drop-in replacements for each other
Attachments
Issue Links
- blocks
-
DM-27940 Replace Click cmdline tests in jointcal with new API
- Won't Fix
- relates to
-
DM-27099 Re-bridge ap_verify and ctrl_mpexec
- Done
-
- Done
-
- To Do
-
- Done
-
- Done
-
- Won't Fix
- links to
Activity
+1 from me as well for reasons similar to Gregory's
I have allocated DMTN-206 for outlining the proposal for the API and to address whether we should take this opportunity to reorganize the relationship between ctrl_bps/ctrl_mpexec/pipe_base.
As I'm debugging jointcal gen3 tests right now (part of adding gen3 metric measurements), having to run the tests through click is again proving to be an annoyance: the click cliRunner swallows pdb.set_trace() calls. Being able to use an API instead of a cliRunner would be very useful.
I'd like to cast a +1 for this as well. The ability to invoke a pipeline from a service process is, I believe, going to become an important part of the image service architecture, particularly for things like diffim- and PVI-recreation-on-demand. It would be useful for this not to have to invoke an external command-line executable in all cases.
This capability was part of the original SuperTask design, though it may have been deprioritized in the mean time.