Kris Wilson
03/03/2020, 6:32 AMschrockn
03/03/2020, 5:53 PMschrockn
03/03/2020, 5:54 PMschrockn
03/03/2020, 5:54 PMschrockn
03/03/2020, 5:55 PMKris Wilson
03/03/2020, 7:57 PMexecute_notebook(notebook_in) -> notebook_out
2) a development mode for defining adhoc (and maybe soon, productionized) Pipelines (and sub-components) for iterative development
the high level idea there is that if your Pipeline is encoded in a notebook (that is also parameterizable and schedulable, via an external orchestrator), that loading that notebook up to iterate on it allows for fluid movement from Experimentation <-> Production use cases. our Notebook environments also have full monorepo integration, so it’s also just as easy to load libraries up for iterative development all the way up to sending a Phabricator review and landing that.
prior art for ref/context:
TFX’s Iterative Notebook RFC: https://github.com/tensorflow/community/blob/master/rfcs/20190815-tfx-notebook.md
Kubeflow’s Fairing project: https://www.kubeflow.org/docs/fairing/fairing-overview/
Kubeflow’s Kale project: https://medium.com/kubeflow/automating-jupyter-notebook-deployments-to-kubeflow-pipelines-with-kale-a4ede38bea1fKris Wilson
03/03/2020, 7:59 PMThe pipeline viewer? The execution viewer?yes, both.
schrockn
03/03/2020, 8:07 PMschrockn
03/03/2020, 8:08 PMschrockn
03/03/2020, 8:12 PMKris Wilson
03/03/2020, 8:14 PM