[Epic] Real demo: Idea to Production for world tour

We have a draft video of the vision demo. There's a trimmed-down 9-minute demo video that is now public. This issue tracks the work to make the "real" demo, where Sid can run through the entire flow, live, on stage at Websummit.

Why are we doing this?

It’s about communicating a compelling vision that helps align us internally and with partners, so we’re building towards the same thing, and understanding the complete context; not just individual parts.

For example, our direction page already lists the scope, but it’s hard to see the big picture from that.

What are we doing? / Scope

• Making a script and all backing materials for a 15-minute live demo, starting from scratch.
• Pre-recording at least one dry run.
• Shipping all features needed to fulfill the vision.

When?

Real demo during GitLab World Tour London, 19th of October

Steps to pull the demo together

• OpenShift:
  • Prepare GitLab template
  • Add GitLab Runner to template
  • Add GitLab Mattermost to template
  • Auto register GitLab Runner against GitLab
  • Auto register GitLab Mattermost against GitLab
  • Make GitLab Runner to use Kubernetes cluster
  • Auto-scale GitLab Runner on Kubernetes
  • Optimise start-up time of GitLab on OpenShift
  • Add default hostnames for the gitlab and gitlab-mattermost services
• ChatOps
  • Implement /issue create and /deploy command: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6705
  • Integrate slash commands with Mattermost: https://github.com/mattermost/platform/pull/4151
  • Ship own fork of Mattermost with GitLab?: omnibus-gitlab!1019 (closed)
• Demo: https://docs.google.com/document/d/1TJIn4FwezD2PmSRdSUj9oAhquMd3GJltnFhhJ04uhzk/edit (original)
  • Create OpenShift template: https://gitlab.com/gitlab-org/gitlab-ce/issues/22956
  • We use .apps.tanukionline.com Use .apps.origin.gitlap.com domain, or use custom DNS
  • Create template for OpenShift configuration that will be part of GitLab
  • Create Dockerfile templates stored in GitLab (this is currently part of I2P branch: https://gitlab.com/gitlab-org/gitlab-ce/tree/idea-to-production-demo)
• Issues:
  • Change default labels to be To Do and Doing
• Pipelines:
  • Automatically refresh / update pipeline graph: https://gitlab.com/gitlab-org/gitlab-ce/issues/5983
• Environments:
  • Review apps: #20255 (closed) #21971 (closed)
  • Allow to close environments: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6669
  • Retouch enviromnet list and deployment list and expose clickable URL: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6691
• Terminal access to deployments (https://gitlab.com/gitlab-org/gitlab-ce/issues/22864)
  • Make Workhorse to execute kubectl exec: gitlab-workhorse!72 (closed)
  • Let gitlab-rails pass openshift project/app to workhorse: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6770
  • gitlab-workhorse: query Kubernetes for some pod matching openshift project/app and spawn shell in first container of that pod
• Velocity analytics
• Record demo and publish to YouTube

Links

• Demo script: https://about.gitlab.com/handbook/sales/vision-demo/
• Previous iteration of video
• 9-minute demo video as presented in the Master Plan
• Issue for previous iteration
• First real demo
• Slideware Demo
• Demo script MR
• Demo project - Velociraptor
• Openshift instance: origin.gitlap.com:8443 (Admin password in 1Password)
• Dockersaurus team Slack
• ChatOps integration (for Mattermost only)

Additional features that haven't been scheduled, but add to the demo

Just for reference, out of scope of this issue, but also part of real vision

• Run GitLab with one click on all major Container Schedulers
• Environment-specific variables
• Button to create/view Kubernetes configuration file from template (similar to .gitlab-ci.yml templates)