Allocate per-class resources#

datahub knows which bCourse courses that users are affiliated with, and can assign users extra resources if defined in the hub configuration. Currently the main datahub is the only deployment that is using the CanvasOAuthenticator so is the only one that can allocate extra resources. However, this will be changed for Spring ‘23.

Defining course profiles#

  1. Obtain the bCourses course ID from course staff. This ID is found in the course’s URL, e.g. It should be a large integer.

  2. Edit deployments/{deployment}/config/common.yaml.

  3. Find an existing stantax, or create a new one, for hub.custom.canvas_courses and insert yaml of the form:

      123456: # Name of Class 100, Fall '22
        mem_limit: 4096M
        mem_guarantee: 2048M
      234567: # Some other class 200, Spring '23
        - mountPath: /home/rstudio/.ssh
          name: home
          subPath: _stat131a/_ssh
          readOnly: true

    where 123456 and 234567 are example integers from the first step. Memory limits and extra volume mounts are specified as in the examples above. It is recommended that you provide a comment indicating the name and term of the course so that they can be easily identified and removed after the course is over.

  4. Commit the change, then ask course staff to verify the increased allocation on staging. It is recommended that they simulate completing a notebook or run through the assignment which requires extra resources.


Currently the code that accomplishes this is in our CustomKubeSpawner, however we will migrate it to the CanvasOAuthenticator. The latter will put the user into a JupyterHub group for each course they are affiliated with. The spawner will then allocate resources based on which groups the user is a member of.