Skip to content

Latest commit

 

History

History
251 lines (186 loc) · 10.1 KB

09-Install-GitLab.md

File metadata and controls

251 lines (186 loc) · 10.1 KB
Raw

<-- Back to Lab #8 - More about Environments

Lab #9 - Install GitLab

Overview

Note: if you're running with less than 10GB of memory (like on an 8GB system), you may want to start only the puppet and gitlab virtual machines for this lab to save memory (don't start the agent VM, as we wont need it.) When running all 3 VM's on an 8GB system, you may start to swap and your workstation may start to crawl and/or freeze up...Close any applications you don't need running to help conserve memory, or get a better workstations. Geesh.

Start up your GitLab VM

You should have already created your gitlab VM, but if not, go ahead and do it now...

     vagrant up gitlab     # bring up your VM
     vagrant ssh gitlab    # ssh in to get a shell
     sudo su -             # become root

Install the Puppet Agent

Although not required for our training environment, let's install the Puppet Agent on our GitLab VM so that our timezone is set, and NTP is configured to run. Review Lab #4 for more details, but it's basically just this:

     curl -k --tlsv1 https://puppet:8140/packages/current/install.bash | bash -s main:certname=gitlab.example.com

Sign the cert on the puppet master, and then run puppet agent -t on gitlab...

     Error: Could not retrieve catalog from remote server: Error 500 on SERVER:
     Server Error: Evaluation Error: Error while evaluating a Function Call, Could
     not find data item location in any Hiera data file and no default supplied at
     /etc/puppetlabs/code/environments/production/manifests/site.pp:31:13 on node
     gitlab.example.com

We need to create a node yaml file for gitlab.example.com on the puppet master...

[root@puppet ~]# cd /etc/puppetlabs/code/environments/production/hieradata/node/
[root@puppet node]# cp agent.example.com.yaml gitlab.example.com.yaml
[root@puppet node]# cat gitlab.example.com.yaml
---

location: amsterdam

classes:
   - ntp
   - timezone

timezone::timezone: 'US/Pacific'

That should be fine for now...Run puppet again and you should get a clean run...

GitLab Installation Instructions

A summary of the minimal installation structions for GitLab follow... (Full instructions are here)

  • Install and configure the necessary dependencies
     # Postfix should already be installed and running, but just in case...
     puppet resource package postfix ensure=present
     puppet resource service postfix ensure=running enable=true
     
     # The above puppet commands do the equivalent of the following, but abstract away from the OS flavor:
     yum install -y postfix
     systemctl enable postfix
     systemctl start postfix
  • Open the host firewall to allow in-bound HTTP. Although GitLab uses HTTP by default, it is possible to re-configure it to use HTTPS. We won't go through that process in this training, but you may find the instructions HERE
     # There is a firewall module that could help us do this with Puppet itself, but for now, let's just be lazy and...
     # Let inbound HTTP through the firewall so we can hit the GitLab web interface
     firewall-cmd --permanent --add-service=http
     systemctl reload firewalld
  • Add the GitLab package server and install the package
     curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.rpm.sh | bash
     yum install -y gitlab-ce
  • Configure and start GitLab
     gitlab-ctl reconfigure

  • Browse to http://127.0.0.1:24080/ and login

    • You'll be prompted to change the root password, so go ahead and do that.
    • Then login with:
      • Username: root
      • Password: <the password you just set>

  • As the 'root' user, create a non-root-user account for yourself

    • Click the wrench icon in the top-right corner called the Admin Area
    • Click Users sub-tab in the Overview section
    • Click New User in the main pane and fill out the required info
      • Use a valid email, as the account creation process will send you a password reset link
      • In the Access section, check the Admin box to make this account and admin account
      • Also make sure Can create a group is checked
    • Click on the Create User button at the bottom of the form
    • Logout the root user
    • You should receive an email to the e-mail address you provided in the account creation form
      • The link to set your password will not work, but you may copy it and edit it to point to localhost like this:
      http://localhost:24080/users/password/edit?reset_password_token=Zo9b6dFY4Ld7YvvW7iCC
    • Next try logging in as yourself using the account you just created and set the password for
      • Note: if unable to get the reset link to work, you can also set the password via the webGUI as the root user
      • Click on the Wrench icon again
      • Click Users
      • Click the Edit button next to your account
      • Scroll a bit down, and you'll find where you can set your password
      • Enter your choice of password twice, and click Save Changes

  • Once your are logged in as yourself (as the user you just created) the continue...

  • Click the GitLab icon top/center (the Orange Origami Fox Head thingy) to get to the Dashboard

  • Create a group called puppet

    • Click on New Group
    • Enter the group name puppet
    • Select Public
    • click Create Group
    • Note: since you've created the group, you are the Owner and will have access to any projects (repos) within that group

  • Create a project called control and set the Namespace to be the puppet group

    • Click New Project and change the Namespace to puppet instead of yourself
    • Select Public visibility here too
    • The remaining options can be left at their defaults
    • Click Create Project

  • Configure your GitLab account to allow you to clone/pull/push to the puppet/control repo

    • You should see a notice that says "You won't be able to pull or push project code via SSH until you add an SSH key to your profile"
    • Click the link add an SSH key
    • If you already have your own personal public/private key pair for SSH, you may use it
    • If you don't already have a key, you can generate one with ssh-keygen
    • Add your public key to your GitLab account under Profile Settings -> SSH Keys
    • Add a config section to your ~/.ssh/config to tell ssh what private key to use, as well as what user and port
  Host localhost
    User git
    Port 24022
    IdentityFile /Users/Mark/.ssh/id_rsa.gitlab-mark

You should now be able to clone your repo. But first, make sure you've set your Name and Email in your Git client config so that your commits show who you are:

For example:

git config --global user.name "Mark Bentley"
git config --global user.email "[email protected]"

Next, try to clone the puppet/control repo from GitLab:

[/Users/Mark/Puppet-Tutorial] $ mkdir -p gitlab/puppet
[/Users/Mark/Puppet-Tutorial] $ cd gitlab/puppet
[/Users/Mark/Puppet-Tutorial/gitlab/puppet] $ git clone ssh://localhost/puppet/control.git
Cloning into 'control'...
The authenticity of host '[localhost]:24022 ([127.0.0.1]:24022)' can't be established.
RSA key fingerprint is 25:cb:6c:9c:da:4e:6f:46:72:75:46:ac:18:19:31:ee.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[localhost]:24022' (RSA) to the list of known hosts.
warning: You appear to have cloned an empty repository.
Checking connectivity... done.

[/Users/Mark/Puppet-Tutorial/gitlab/puppet] $ cd control
[/Users/Mark/Puppet-Tutorial/gitlab/puppet/control] $ git remote -v
origin  ssh://localhost/puppet/control.git (fetch)
origin  ssh://localhost/puppet/control.git (push)

[/Users/Mark/Puppet-Tutorial/gitlab/puppet/control] $ vi README.md

Put some text in to your README.md such as 'Hello World' then add that file and commit it.

[/Users/Mark/Puppet-Tutorial/gitlab/puppet/control] *$ git add README.md

[/Users/Mark/Puppet-Tutorial/gitlab/puppet/control] *$ git commit -m 'First commit'
[master (root-commit) 276c800] First commit
 1 file changed, 2 insertions(+)
 create mode 100644 README.md

[/Users/Mark/Puppet-Tutorial/gitlab/puppet/control] (master)$ git push
Counting objects: 3, done.
Writing objects: 100% (3/3), 231 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
To ssh://localhost/puppet/control.git
 * [new branch]      master -> master

Now go back to the GitLab webGUI and take a look at the file you just pushed.

You'll have to explore the GitLab WebGUI a bit, and figure out things on your own. Some key things:

  • Click on the orange oragami fox head icon to return to the main dashboard
  • Click on puppet/control to see your new empty Puppet "Control Repo"
  • Click on the sub-tab Files to see the files in the repo
  • Click on the sub-tab Commits to see individual commit history
  • Click on an individual commit to see what changed

At this point you have a GitLab server running, and ready to be used. You have a single group called 'puppet' containing a single project (or repo) called 'control'. In the next lab we will work to move our puppet code in to GitLab so we don't have to make manual edits on the puppet master itself.

Continue on to Lab #10 --> Move Puppet Code under Git Control

See Also:

- Installation Instructions:      <https://about.gitlab.com/downloads/#centos7>
- GitLab Omnibus Documentation:   <http://doc.gitlab.com/omnibus/>
- Configure GitLab to use HTTPS:  <https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/settings/nginx.md>

<-- Back to Contents

Copyright © 2016 by Mark Bentley