Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds tooling for creating kernel specifications that utilize the various provisioners. Each "provisioner" will have its own console script that knows about that provisioner's requirements (parameters, launcher, etc.). However, most of the implementation occurs within a base class of each script class.
The current set of console scripts are:
jupyter-k8s-spec
(corresponding toKubernetesProvisioner
)jupyter-docker-spec
(corresponding to eitherDockerProvisioner
orDockerSwarmProvisioner
)jupyter-yarn-spec
(corresponding toYarnProvisioner
)jupyter-ssh-spec
(corresponding toDistributedProvisioner
)Kernel specifications are essentially assembled from the set of parameters. We will not provide OOTB kernel specs as part of the release assets. Instead, kernel specs can be built using this tool.
Here are some example commands (and their outputs):
Note that we still need to bring over the
SparkOperatorProcessProxy
as a provisioner and implement (most likely) ajupyter-crd-spec
script.