allow notebook resources composition

[proppy]

Is your feature request related to a problem? Please describe.

Currently when user instanciate modules with notebooks, rad-lab will provision notebook_count x notebooks with the same resource parameters.

While this convenient for simple deployment using the radlab cli/gui, terraform root module managing rad-lab deployment often need to tweak instance classes and other parameter like disk size per notebooks associated to a given project (see for example proppy/rad-lab-deploy#5).

Describe the solution you'd like

I wonder if we could expose the terraform configuration as separate module (similar to what's discussed in https://developer.hashicorp.com/terraform/language/modules/develop/composition):
a. project creation or reuse
b. network
c. image building
d. service accounts
e. notebook instances
and provide a parent a rad-lab environment that compose (a, b, c, d) and leave the management of e. to the root module?

Describe alternatives you've considered

While terraform supports object input variables, it sounds cumbersome and error prone to maintain a direct mapping between user-provided variable and notebooks_instance to allow fine grained customization.

Related feature requests

This could also allow easier integration in other terraform based project like https://github.com/GoogleCloudPlatform/hpc-toolkit.

Priority
Low

Labels
Notebooks, Silicon

[github-actions]

Thank you for raising the request! RAD Lab admins have been notified.