The GitLab Demo Systems provide infrastructure for the GitLab Customer Success, Marketing, Sales, and Training teams to demonstrate GitLab features, value propositions, and workflows in a variety of asynchronous and live capacities.
Please consider this handbook documentation to be the single source of truth ("SSOT") for all resources that use the
gitlabdemo.cloud domain names.
Why shouldn’t we just use GitLab.com? Although you can use GitLab.com for showing most of the value of GitLab use cases, there are some administrative features that require the deployment of GitLab Omnibus infrastructure in AWS, GCP, or local VM/container. Many of our enterprise customers opt for self-managed over GitLab.com so we are mindful of “showing the customer what they’ll see in production”.
Why shouldn’t each team member build their own demos? It is inefficient for Solutions Architects team members to spend a lot of time building the infrastructure and configuring servers needed for delivering demos to customers, so the Demo Systems team provides an economies-of-scale platform for Customer Success team members to simplify the provisioning of infrastructure and access to demo environments.
What’s special about our infrastructure? The demo systems infrastructure doesn’t do anything special that a customer or partner company couldn’t do themselves with the appropriate staffing and engineering investment. We will be open sourcing our infrastructure-as-code methods, scripts and tools for the wider community to use to streamline their deployment of Omnibus infrastructure.
To self-provision an individual AWS account, see the instructions on the Sandbox Cloud handbook page. To have a group AWS account provisioned, create an access request issue in the Sandbox Cloud issue tracker.
If you are planning a workshop and are looking for the process on using invitation codes and sample projects, see the Training Cloud How it Works handbook section.
For all other questions or requests, please ask in
#demo-systems on Slack and tag Jeff Martin. If Jeff is not available, please tag James Sandlin (North America) or Cristiano Casella (Europe) depending on your timezone.
The Demo Systems are architected and maintained by Jeff Martin (Senior Demo Systems Engineer). We have other team members in the Customer Success team that volunteer part-time to help support our users and infrastructure. Please contact Jeff on Slack with any questions or requests. We also collaborate with counterparts in other departments for broader GitLab infrastructure configuration in AWS, GCP, etc and security incident response.
You can see the shared projects that have been published in the Demo Cloud in the Community Projects or Training and Workshop Sample Projects groups, or explore the Demo Systems Users group to discover other team memer's projects.
These are the projects that make the Demo Systems possible behind the scenes. You are welcome to study and learn from any of our source code. Each project is classified as
Private depenending on the security risk of the source code or information contained within.
PrivateDemo and Training Cloud v1
Privatedemosys-terraform - Terraform configuration for demo systems infrastructure. Not for end users.
Privatedemosys-ansible - Ansible configuration for demo systems infrastructure.
Privatedemosys-portal (gitlabdemo.com) - Full stack application for demo reservation management.
PublicDemo Cloud v2
PublicTraining Cloud v2
PublicHackyStack Portal - Open Source
PublicHackyStack Portal - GitLab Inc Clone
Private - OpsGCP HackyStack Portal Production - Terraform (gitlabsandbox.cloud)
Private - OpsGCP HackyStack Portal Production - Ansible (gitlabsandbox.cloud)
Private - OpsGCP sandbox Cloud DNS - Terraform (gitlabsandbox.cloud)
Private - OpsCloud Realms Runbook Docs
We use Slack for real-time support and quick fixes. If in doubt of how to get help, ask in
#demo-systems. The issue trackers are used for tasks and projects that take longer than 30 minutes. We do not use email for internal team communications.
#demo-systemsSlack channel (for Demo Cloud announcements, questions, and technical support with Demo Cloud)
#demo-systems-workshops-noramSlack channel (for workshop support in North America)
#demo-systems-workshops-emeaSlack channel (for workshop support in Europe and surrounding regions)
#demo-systems-workshops-apacSlack channel (for workshop support in Asia, Australia and surrounding regions)
#sandbox-cloudSlack channel (for Sandbox Cloud announcements)
#sandbox-cloud-questionsSlack channel (for Sandbox Cloud questions and technical support)
email@example.com(for GitLab community members)