diff --git a/docs/source/operators/deploy-distributed.md b/docs/source/operators/deploy-distributed.md index a7b95cb07..91782df18 100644 --- a/docs/source/operators/deploy-distributed.md +++ b/docs/source/operators/deploy-distributed.md @@ -37,12 +37,12 @@ Entries in the remote hosts configuration should be fully qualified domain names All the kernel *specifications* configured to use the `DistributedProcessProxy` must be on all nodes to which there's a reference in the remote hosts configuration! With YARN cluster node, only the Python and R kernel _packages_ are required on each node, not the entire kernel specification. ``` -The following installs the sample `python_distributed` kernel specification relative to the 3.1.0 release on the given node. This step must be repeated for each node and each kernel specification. +The following installs the sample `python_distributed` kernel specification relative to the 3.2.0 release on the given node. This step must be repeated for each node and each kernel specification. ```Bash -wget https://github.com/jupyter-server/enterprise_gateway/releases/download/v3.1.0/jupyter_enterprise_gateway_kernelspecs-3.1.0.tar.gz +wget https://github.com/jupyter-server/enterprise_gateway/releases/download/v3.2.0/jupyter_enterprise_gateway_kernelspecs-3.2.0.tar.gz KERNELS_FOLDER=/usr/local/share/jupyter/kernels -tar -zxvf jupyter_enterprise_gateway_kernelspecs-3.1.0.tar.gz --strip 1 --directory $KERNELS_FOLDER/python_distributed/ python_distributed/ +tar -zxvf jupyter_enterprise_gateway_kernelspecs-3.2.0.tar.gz --strip 1 --directory $KERNELS_FOLDER/python_distributed/ python_distributed/ ``` ```{tip} diff --git a/docs/source/operators/deploy-kubernetes.md b/docs/source/operators/deploy-kubernetes.md index 3cef4ac25..27cfc6883 100644 --- a/docs/source/operators/deploy-kubernetes.md +++ b/docs/source/operators/deploy-kubernetes.md @@ -993,10 +993,10 @@ kubectl logs -f pod/alice-5e755458-a114-4215-96b7-bcb016fc7b62 Note that if using multiple replicas, commands against each pod are required. -- The Kubernetes dashboard is useful as well. It's located at port `3.1.0` of the master node +- The Kubernetes dashboard is useful as well. It's located at port `3.2.0` of the master node ```bash -https://elyra-kube1.foo.bar.com:3.1.0/dashboard/#!/overview?namespace=default +https://elyra-kube1.foo.bar.com:3.2.0/dashboard/#!/overview?namespace=default ``` From there, logs can be accessed by selecting the `Pods` option in the left-hand pane followed by the _lined_ icon on diff --git a/docs/source/operators/deploy-yarn-cluster.md b/docs/source/operators/deploy-yarn-cluster.md index cd61ef7ec..284033075 100644 --- a/docs/source/operators/deploy-yarn-cluster.md +++ b/docs/source/operators/deploy-yarn-cluster.md @@ -56,9 +56,9 @@ We recommend installing kernel specifications into a shared folder like `/usr/lo Considering we would like to enable the IPython kernel to run on YARN Cluster and Client mode we would have to copy the sample configuration folder **spark_python_yarn_cluster** to where the Jupyter kernels are installed (e.g. jupyter kernelspec list) ```bash -wget https://github.com/jupyter-server/enterprise_gateway/releases/download/v3.1.0/jupyter_enterprise_gateway_kernelspecs-3.1.0.tar.gz +wget https://github.com/jupyter-server/enterprise_gateway/releases/download/v3.2.0/jupyter_enterprise_gateway_kernelspecs-3.2.0.tar.gz KERNELS_FOLDER=/usr/local/share/jupyter/kernels -tar -zxvf jupyter_enterprise_gateway_kernelspecs-3.1.0.tar.gz --strip 1 --directory $KERNELS_FOLDER/spark_python_yarn_cluster/ spark_python_yarn_cluster/ +tar -zxvf jupyter_enterprise_gateway_kernelspecs-3.2.0.tar.gz --strip 1 --directory $KERNELS_FOLDER/spark_python_yarn_cluster/ spark_python_yarn_cluster/ ``` For more information about the IPython kernel, please visit the [IPython kernel](https://ipython.readthedocs.io/en/stable/) page. @@ -68,9 +68,9 @@ For more information about the IPython kernel, please visit the [IPython kernel] Considering we would like to enable the Scala Kernel to run on YARN Cluster and Client mode we would have to copy the sample configuration folder **spark_scala_yarn_cluster** to where the Jupyter kernels are installed (e.g. jupyter kernelspec list) ```bash -wget https://github.com/jupyter-server/enterprise_gateway/releases/download/v3.1.0/jupyter_enterprise_gateway_kernelspecs-3.1.0.tar.gz +wget https://github.com/jupyter-server/enterprise_gateway/releases/download/v3.2.0/jupyter_enterprise_gateway_kernelspecs-3.2.0.tar.gz KERNELS_FOLDER=/usr/local/share/jupyter/kernels -tar -zxvf jupyter_enterprise_gateway_kernelspecs-3.1.0.tar.gz --strip 1 --directory $KERNELS_FOLDER/spark_scala_yarn_cluster/ spark_scala_yarn_cluster/ +tar -zxvf jupyter_enterprise_gateway_kernelspecs-3.2.0.tar.gz --strip 1 --directory $KERNELS_FOLDER/spark_scala_yarn_cluster/ spark_scala_yarn_cluster/ ``` For more information about the Scala kernel, please visit the [Apache Toree](https://toree.apache.org/) page. @@ -80,9 +80,9 @@ For more information about the Scala kernel, please visit the [Apache Toree](htt Considering we would like to enable the IRkernel to run on YARN Cluster and Client mode we would have to copy the sample configuration folder **spark_R_yarn_cluster** to where the Jupyter kernels are installed (e.g. jupyter kernelspec list) ```Bash -wget https://github.com/jupyter-server/enterprise_gateway/releases/download/v3.1.0/jupyter_enterprise_gateway_kernelspecs-3.1.0.tar.gz +wget https://github.com/jupyter-server/enterprise_gateway/releases/download/v3.2.0/jupyter_enterprise_gateway_kernelspecs-3.2.0.tar.gz KERNELS_FOLDER=/usr/local/share/jupyter/kernels -tar -zxvf jupyter_enterprise_gateway_kernelspecs-3.1.0.tar.gz --strip 1 --directory $KERNELS_FOLDER/spark_R_yarn_cluster/ spark_R_yarn_cluster/ +tar -zxvf jupyter_enterprise_gateway_kernelspecs-3.2.0.tar.gz --strip 1 --directory $KERNELS_FOLDER/spark_R_yarn_cluster/ spark_R_yarn_cluster/ ``` For more information about the iR kernel, please visit the [IRkernel](https://irkernel.github.io/) page. diff --git a/docs/source/other/troubleshooting.md b/docs/source/other/troubleshooting.md index 9d5417c74..8bb1eae44 100644 --- a/docs/source/other/troubleshooting.md +++ b/docs/source/other/troubleshooting.md @@ -33,8 +33,8 @@ a "Kernel error" and State: 'FAILED'.** 1. Check the output from Enterprise Gateway for an error message. If an applicationId was generated, make a note of it. For example, you can locate the applicationId - `application_15065522733.1.0011` from the following snippet of message: - `[D 2017-09-28 17:13:22.675 EnterpriseGatewayApp] 13: State: 'ACCEPTED', Host: 'burna2.yourcompany.com', KernelID: '28a5e827-4676-4415-bbfc-ac30a0dcc4c3', ApplicationID: 'application_15065522733.1.0011' 17/09/28 17:13:22 INFO YarnClientImpl: Submitted application application_15065522733.1.0011 17/09/28 17:13:22 INFO Client: Application report for application_15065522733.1.0011 (state: ACCEPTED) 17/09/28 17:13:22 INFO Client: client token: N/A diagnostics: AM container is launched, waiting for AM container to Register with RM ApplicationMaster host: N/A ApplicationMaster RPC port: -1 queue: default start time: 1506644002471 final status: UNDEFINED tracking URL: http://burna1.yourcompany.com:8088/proxy/application_15065522733.1.0011/` + `application_15065522733.2.0011` from the following snippet of message: + `[D 2017-09-28 17:13:22.675 EnterpriseGatewayApp] 13: State: 'ACCEPTED', Host: 'burna2.yourcompany.com', KernelID: '28a5e827-4676-4415-bbfc-ac30a0dcc4c3', ApplicationID: 'application_15065522733.2.0011' 17/09/28 17:13:22 INFO YarnClientImpl: Submitted application application_15065522733.2.0011 17/09/28 17:13:22 INFO Client: Application report for application_15065522733.2.0011 (state: ACCEPTED) 17/09/28 17:13:22 INFO Client: client token: N/A diagnostics: AM container is launched, waiting for AM container to Register with RM ApplicationMaster host: N/A ApplicationMaster RPC port: -1 queue: default start time: 1506644002471 final status: UNDEFINED tracking URL: http://burna1.yourcompany.com:8088/proxy/application_15065522733.2.0011/` 1. Lookup the YARN log for that applicationId in the YARN ResourceManager UI: ![YARN ResourceManager UI](../images/yarnui.jpg) 1. Drill down from the applicationId to find logs for the failed attempts and take appropriate actions. For example, for the error below, diff --git a/etc/docker/docker-compose.yml b/etc/docker/docker-compose.yml index 5a17c5ae3..0de7fc535 100644 --- a/etc/docker/docker-compose.yml +++ b/etc/docker/docker-compose.yml @@ -10,7 +10,7 @@ version: "3.5" # 3. We only use one replica since session affinity is another point of investigation in Swarm services: enterprise-gateway: - image: elyra/enterprise-gateway:dev + image: elyra/enterprise-gateway:3.2.0 user: root volumes: - "/var/run/docker.sock:/var/run/docker.sock" diff --git a/etc/kubernetes/helm/enterprise-gateway/Chart.yaml b/etc/kubernetes/helm/enterprise-gateway/Chart.yaml index 8acf52f2d..2ee4853a3 100644 --- a/etc/kubernetes/helm/enterprise-gateway/Chart.yaml +++ b/etc/kubernetes/helm/enterprise-gateway/Chart.yaml @@ -4,7 +4,7 @@ description: A helm chart to deploy Jupyter Enterprise Gateway # This is the chart version. This version number should be incremented each time you make changes # to the chart and its templates, including the app version. # Versions are expected to follow Semantic Versioning (https://semver.org/) -version: 3.2.0-dev0 +version: 3.2.0 # This is the version number of the application being deployed. This version number should be # incremented each time you make changes to the application. Versions are not expected to diff --git a/etc/kubernetes/helm/enterprise-gateway/values.yaml b/etc/kubernetes/helm/enterprise-gateway/values.yaml index 4fb3b6b29..492420687 100644 --- a/etc/kubernetes/helm/enterprise-gateway/values.yaml +++ b/etc/kubernetes/helm/enterprise-gateway/values.yaml @@ -23,7 +23,7 @@ imagePullSecretsCreate: # --set imagePullSecretsCreate.secrets[1].data="UHJvZCBTZWNyZXQgSW5mb3JtYXRpb24K" # Enterprise Gateway image name and tag to use. -image: elyra/enterprise-gateway:dev +image: elyra/enterprise-gateway:3.2.0 # Enterprise Gateway image pull policy. imagePullPolicy: IfNotPresent # K8s Enterprise Gateway Service @@ -156,7 +156,7 @@ kip: create: false annotations: {} # Kernel Image Puller image name and tag to use. - image: elyra/kernel-image-puller:dev + image: elyra/kernel-image-puller:3.2.0 # Kernel Image Puller image pull policy. imagePullPolicy: IfNotPresent # Determines whether the Kernel Image Puller will pull kernel images it has previously pulled