Cloud Native Workshop

[l0rd]

Description

There are a couple of events were we will do demos in December and we have the opportunity to show the latest coolest Che 7 Features: KubeCon and Paris JUG.

Goal: Show Che 7 extensible workspace model, VS Code extension compatibility, workflow with inner and outer loop. Given the che.openshift.io performance we may be forced to demo it in a local minikube.

Demo Script

• Create a Che 7 Dev workspace and clone our modified petclinic
• Test the application inside the workspace
• Change code, debug, run a maven build
• Restart the application (inner loop)
• Build the docker image and push it on DockerHub using github.com/ws-skeleton
• [Alternative] Build the image using JIB
• Set the kubectl context to connect to a remote cluster
• Use VSCode Kubernetes extension to deploy the to the remote cluster using kubectl apply, kubectl get events, kubectl logs (outer loop)

Subtasks

• Create VSCode extension broker for Theia Create VSCode extension broker for Theia #12026
• Update the registry meta.yaml model to have a sidecar-image attribute
• Publish the VSCode Kubernetes tooling extension in the plugin registry
• Implement the workspace commands to run the inner loop
• Implement a command to create the kubectl context to connect to a remote cluster
• (Optional) Use JIB to build the container image inside the container

[l0rd]

cc @garagatyi @azatsarynnyy

[l0rd]

cc @sunix

[benoitf]

hello, what is the difference between modified petclinicand https://github.com/che-samples/web-java-spring-petclinic (mysql branch) https://github.com/che-samples/web-java-spring-petclinic/tree/mysql ?
should it merged to che-samples ?

[l0rd]

@benoitf the difference are the Dockerfile, Dockerfile4che, App.yaml and App4Che.yaml that do not exist in the upstream project. Not sure if che-samples would be a good place to merge that code. @sleshchenko what do you think?

[sleshchenko]

@benoitf Actually modified petclinic is based on spring-petclinic repository but not web-java-spring-petclinic.
@l0rd I think our web-java-spring-petclinic may be updated and Dockerfile, Dockerfile4che, App.yaml, App4Che.yaml could be placed there as well. It would show how a sample web application can be run in che with different approaches. README.md could be updated to make it clear.

[benoitf]

@sleshchenko AFAIK it is based on the same repository (maybe fork link has been gone) but it's based on it (and surely it's an outdated one) but many ppl are using it in demos. so maybe it's worth to update/make it sync with latest petclinic UI
@slemeur ?

[slemeur]

Updating the repo with latest version would be indeed nice. It is used for a lot of demos indeed.

…

On Friday, November 23, 2018, Florent BENOIT ***@***.***> wrote: @sleshchenko <https://github.com/sleshchenko> AFAIK it is based on the same repository (maybe fork link has been gone) but it's based on it (and surely it's an outdated one) but many ppl are using it in demos. so maybe it's worth to update/make it sync with latest petclinic UI @slemeur <https://github.com/slemeur> ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#11972 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABj5oXqkpEp3CfvVw5caZWfYgPgqiHXMks5ux8iZgaJpZM4YmT9t> .

-- Stévan LeMeur // Product Manager // Developer Tools // +336-87-11-27-55

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.