Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-31960

Noteburst: investigate and begin porting mobu's notebook execution code

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      The purpose of this ticket is to begin porting mobu's notebook execute code into noteburst. A large part of this work will also be the inital investigation of mobu's code and architecting how this code should be structured in noteburst.

        Attachments

          Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-31910 Set up the noteburst package

          • Done

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            jsick Jonathan Sick added a comment -

            I've got the noteburst PR and an explanation of some of the issues at https://github.com/lsst-sqre/noteburst/pull/2

            Show
            jsick Jonathan Sick added a comment - I've got the noteburst PR and an explanation of some of the issues at  https://github.com/lsst-sqre/noteburst/pull/2
            Hide
            Permalink
            jsick Jonathan Sick added a comment -

            We've ported over the core mobu code with clients for Cachemachine and JupyterHub/Lab, with support for running code in the JupyterLab kernel through a websocket. There is also support for our notebook execution extension, as an alternative to executing notebooks cell-by-cell.

            This work includes prototype endpoints that demonstrate the functionality of noteburst, but will be replaced by the /v1/ API.

            Things still to do:

            1. Refactor the JupyterClient context manager
            2. Support packaging JupyterHub and JupyterLab status information to support mobu use cases
            3. Support building out a pool of long-running JupyterLab pods.
            Show
            jsick Jonathan Sick added a comment - We've ported over the core mobu code with clients for Cachemachine and JupyterHub/Lab, with support for running code in the JupyterLab kernel through a websocket. There is also support for our notebook execution extension, as an alternative to executing notebooks cell-by-cell. This work includes prototype endpoints that demonstrate the functionality of noteburst, but will be replaced by the /v1/ API. Things still to do: Refactor the JupyterClient context manager Support packaging JupyterHub and JupyterLab status information to support mobu use cases Support building out a pool of long-running JupyterLab pods.

              People

              Assignee:
              jsick Jonathan Sick
              Reporter:
              jsick Jonathan Sick
              Reviewers:
              Russ Allbery
              Watchers:
              Jonathan Sick, Russ Allbery
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.