You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The gateway_provisioners repo currently resides in the gateway-experiments organization, which is where a few experimental projects reside to complete POCs, etc. With its 0.1.0 release, I would like to propose that it be moved into the jupyter-server organization so it can reside alongside the existing Gateway projects (Enterprise Gateway and Kernel Gateway). In addition to perhaps making the project more available to contributions, we can also more safely leverage things like jupyter-releaser (and its use of tokens during release builds, etc.).
gateway_provisioners provides kernel provisioners for launching and managing kernel lifecycles in Kubernetes, Docker, DockerSwarm, SSH, and Hadoop Yarn clusters. Because these are merely kernel provisioners, they are available to projects other than the Gateway projects. (Fun fact, they are NOT currently available to EG until its 4.0 release.) This repo was originally named remote-provisioners, but I felt that name was too generic, among other things.
I'd like to add this topic to this week's Server/Kernels Team Meeting, at which time I'm hoping we can reach a consensus.
The text was updated successfully, but these errors were encountered:
Hello,
The gateway_provisioners repo currently resides in the gateway-experiments organization, which is where a few experimental projects reside to complete POCs, etc. With its 0.1.0 release, I would like to propose that it be moved into the jupyter-server organization so it can reside alongside the existing Gateway projects (Enterprise Gateway and Kernel Gateway). In addition to perhaps making the project more available to contributions, we can also more safely leverage things like jupyter-releaser (and its use of tokens during release builds, etc.).
gateway_provisioners provides kernel provisioners for launching and managing kernel lifecycles in Kubernetes, Docker, DockerSwarm, SSH, and Hadoop Yarn clusters. Because these are merely kernel provisioners, they are available to projects other than the Gateway projects. (Fun fact, they are NOT currently available to EG until its 4.0 release.) This repo was originally named remote-provisioners, but I felt that name was too generic, among other things.
I'd like to add this topic to this week's Server/Kernels Team Meeting, at which time I'm hoping we can reach a consensus.
The text was updated successfully, but these errors were encountered: