The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
This guide can be used to help new GitLab Dedicated customers prepare for the creation of their GitLab Dedicated instance.
While the GitLab Dedicated engineering team is responsible for completing the tenant creation process, there are key pieces of information needed from the customer in order to ensure their GitLab Dedicated tenant environment is ready for them as soon as the sales process is complete.
More information about the GitLab Dedicated new customer process including onboarding can be found [here](https://internal.gitlab.com/handbook/engineering/horse/#new-customer-process (internal only).
For transparency, we have made this available in our public handbook so it can be shared with customers directly as needed to provide visibility into our onboarding process.
The checklists below can be provided to customers (along with the related documentation) to set expectations for what configurations can be made as part of the initial tenant creation process and what information and/or input is needed from them for each configuration.
The information a customer provides can then be transferred to the GitLab Dedicated new tenant onboarding issue (internal only) which will be assigned to a GitLab Dedicated team member once ready for engineering.
Before opening an onboarding issue, be sure that you will be able to provide the required information in the first two sections of the onboarding issue.
NOTE: This information must all be included in the description of the new tenant onboarding issue before engineering can begin tenant provisioning.
Please confirm the following with your customer - feel free to copy the list below as is and send to your customer to complete.
- Email of the person/people who should receive the root credentials for their instance once created. - Number of users - this should correspond with the number of Ultimate licenses being purchased. - Primary, secondary, and backup AWS regions - note that for an instance to be geo-enabled, a secondary region must be provided. - Instance subdomain - see documentation linked above for syntax - Initial repository size - this should correspond with what has been agreed upon during the quoting process. - Weekly maintenance window - see documentation linked above for available windows and select one from the list.
These additional configurations can be made by the GitLab Dedicated team while the tenant is being provisioned.
NOTE: These must also be included in the corresponding sections in the description of the new tenant onboarding issue.
If not included in the description, they will not be added to the customer's GitLab dedicated tenant model and will need to be requested via subsequent support tickets using the corresponding issue template.
Configurations not listed here can be requested via subsequent issues using the corresponding issue template.
These will not be configured in the customer's GitLab Dedicated instance during the initial provisioning, but can be completed as soon as the customer's first weekly maintenance window. If needed sooner, please specify in the issue.
Contact the GitLab Dedicated team via #f_gitlab_dedicated Slack channel.