feat(gitlab_runner): init project

Author: wikitops

.gitignore

@@ -0,0 +1,2 @@
+.vagrant/*
+ubuntu-xenial-16.04-cloudimg-console.log

LICENCE.md

@@ -0,0 +1,9 @@
+MIT License
+
+Copyright (c) 2018 wikitops
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

README.md

@@ -0,0 +1,76 @@
+# Ansible : Playbook Gitlab Runner
+
+The aim of this project is to deploy a simple Gitlab Runner instance on Vagrant.
+
+## Getting Started
+
+These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.
+
+### Prerequisites
+
+What things you need to run this Ansible playbook :
+
+*   [Vagrant](https://www.vagrantup.com/docs/installation/) must be installed on your computer
+*   Update the Vagrant file based on your computer (CPU, memory), if needed
+*   You must have download the ubuntu Xenial64 vagrant box :
+
+```
+vagrant box add https://app.vagrantup.com/ubuntu/boxes/xenial64
+```
+*   If you want to register the Gitlab Runner, you have to get a token from your Gitlab server and configure it in the playbook file
+
+### Usage
+
+A good point with Vagrant is that you can create, update and destroy all architecture easily with some commands.
+
+Be aware that you need to be in the Vagrant directory to be able to run the commands.
+
+#### Build Environment
+
+Vagrant needs to init the project to run and build it :
+
+```
+vagrant up
+```
+
+After build, you can check which virtual machine Vagrant has created :
+
+```
+vagrant status
+```
+
+If all run like it is expected, you should see something like this :
+
+```
+$ vagrant status
+
+Current machine states:
+
+runner01               running (virtualbox)
+```
+
+#### Deployment
+
+To deploy the Gitlab Runner instance, you just have to run the Ansible playbook gitlab-runner.yml with this command :
+
+```
+ansible-playbook gitlab-runner.yml
+```
+
+If everything run as expected, the runner should be register on your Gitlab server.
+
+#### Destroy
+
+To destroy on what Vagrant has created, just run this command :
+
+```
+vagrant destroy
+```
+
+## Author
+
+Member of Wikitops : https://www.wikitops.io/
+
+## Licence
+
+This project is licensed under the Apache License, Version 2.0. For the full text of the license, see the LICENSE file.

Vagrantfile

@@ -0,0 +1,25 @@
+# -*- mode: ruby -*-
+# vi: set ft=ruby :
+
+Vagrant.configure("2") do |config|
+
+  config.vm.box = "ubuntu/xenial64"
+
+  # Gitlab Runner
+  (1..1).each do |i|
+    config.vm.provider "virtualbox" do |vb|
+      vb.memory = 2048
+      vb.cpus = 2
+    end
+
+    config.vm.define "runner0#{i}" do |master|
+      master.vm.hostname = "runner0#{i}"
+      master.vm.network "private_network", ip: "10.0.4.3#{i}"
+    end
+  end
+
+  # Provision
+  config.vm.provision "shell", path: "provision.sh"
+  config.vm.provision "file", source: "~/.ssh/id_rsa.pub", destination: "/home/vagrant/.ssh/authorized_keys"
+
+end