1. Deploying Siebel CRM Containers on Kubernetes using Siebel Cloud Manager
  2. Installing GitLab

Installing GitLab

Use this task to create and deploy the GitLab stack (that is, to install the GitLab instance in a virtual machine instance on OCI).

SCM uses GitLab to store the configuration of each deployment that it performs. In the lift and shift use case, GitLab stores the artifacts that were previously sourced from the source environment using the Siebel Lift utility, and then accessing the configuration files from GitLab to do the actual deployment. GitLab also stores configuration artifacts for the greenfield use case, including the one described in Customizing Configurations Prior to Greenfield Deployment.
Note: Only a single instance of GitLab is required for the OCI main compartment in which you are working. If GitLab is already installed and available to you, then you can skip this task.

During stack creation, review all default values displayed. Confirm each value or enter a new value as appropriate for your task.

To create and deploy the GitLab stack

  1. Go to the following OCI document about deploying GitLab:

    https://docs.oracle.com/en/solutions/deploy-gitlab-ci-cd-oci/index.html

  2. In the Deploy section, click the Deploy to Oracle Cloud link.

  3. Log in to your OCI tenancy.

  4. Choose the region (where the working directory will be created).

  5. Specify the working directory (from which the Terraform configuration scripts run) and specify the compartment in which to create the GitLab stack (the compartment you created in Creating a Compartment). Optionally, you can also specify the stack name and a product description or change them from defaults.

  6. Under GitLab Server Configuration, specify the external URL for accessing GitLab.

  7. In Compute Configuration, specify the compute compartment you specified in Step 5 of this procedure and the rest of the settings (availability domain, instance name, DNS hostname label, Flex Shape Oracle Compute Units (OCPUs), and compute image). For Flex Shape OCPUs, the maximum is 64 OCPUs.

  8. Specify the public SSH key by pasting it or by specifying an SSH key file. You use this key to access the virtual machine.

  9. Specify the Virtual Cloud Network (VCN) settings: the network compartment (in which all network resources are created) and network strategy (Create New VCN and Subnet or Use Existing VCN and Subnet).

  10. Verify your configuration variables and start creating the stack. To immediately provision the resources defined in the Terraform configuration, check Run Apply. Then click Create.

    A GitLab job will have run, with status Succeeded. You can also create and run jobs to perform tasks on the stack (using the Terraform configuration). The Compute Service displays the available instances (such as gitlab-server) in the compartment that you specified in Step 5 of this procedure.

  11. Launch the public URL. When prompted, specify the new GitLab password to use.

    Now you can log in to GitLab as an administrator or other user, specifying either the user ID or the email address and specifying the new password. The initial user is root.

  12. After installing GitLab, do the following:

    • Manually configure HTTPS for GitLab (creating key file and self-signed certificates), for greater security.

    • Upgrade GitLab, where necessary, such as for greater security. For more information, see:

      https://docs.gitlab.com/ee/update/