Skip to content
Snippets Groups Projects
New issue look: Off

[Epic] Iteration of Vision Demo: Idea to Production

    • Closed Issue created by Mark Pundsack @markpundsack

    We have a draft video of the vision demo. This issue tracks the next iteration with the goal of integrating feedback, making the demo look better, and fitting it into 15 minutes.

    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 15 minute video that looks like a live demo, starting from scratch.
    • Making stubbed plugins and branches where necessary to show off features that don't exist yet.
    • Focusing on what we can ship this year, with emphasis on deliverables in the next 3 months.

    Team

    Links

    Proof of concept / Mocked interfaces / Other steps to pull the demo together

    • Register dockersaurus.com?
    • Add environment variables for production secrets
    • Remove redundancy, for example revisiting the container registry
    • Find a better way to copy the Velociraptor logo (currently manually put into Koding off-camera)
    • Slack integration
      • Add delayed deploy succeeded message
      • Turn into Slack app
      • Install app/commands to new team
    • Integrate issue board prototype into branch to share header, just replace main content area
    • Koding
      • Install Koding on some cloud (DO)
      • Give Koding AWS creds to spin up stacks
    • Embed Cycle Analytics screen in branch in GitLab CE
    • Embed deployment status in branch in GitLab CE
    • Install 2 shared runners on some cloud (DO), and configure in GitLab CE instance @zj
    • Connect GitLab CE with Koding
    • Integrate staging and production Velociraptor with Openshift (make deploy target the container scheduler)
      • Set up new template to look like production and staging environments of Velociraptor app
      • Either change demo to use .apps.origin.gitlap.com domain, or explain how to configure variables to set custom domains, or explain custom DNS
      • Add kubernetes configuration to template app, or
      • Add kubernetes templates to GitLab as another special file type, or
      • Write a kubernetes file on the fly, or
      • Demo automatic configuration of Openshift/kubernetes production/staging/review apps in project settings
    • Mock up picking Openshift during project creation, including checking production, staging, and review apps
    • Move deploy actions to buttons on environments page?
    • Use .gitlab-ci.yml from template picker rather than copy from kubernetes example
    • Create an even simpler app from scratch?
    • Show pipeline graphs, including parallel tests
    • Mock up pipeline that extends post-merge?
      • have a deploy to production button from a merge request, even after merge
    • Explain why this is amazing up-front (show a new GitLab install, new app install, no need to tie the tools together)?

    Timeline for real demo (for reference, out of scope for this issue)

    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: #20199 (moved)
    2 of 30 checklist items completed

    Designs

      Child items ...

      2. Activity

      Please register or sign in to reply