| #!/usr/bin/perl | |
| # set-guest-hypervisor-fact v0.1 | |
| # | |
| # (c)2018 Marcel Klapwijk | |
| # Please leave suggestions and bug reports at: | |
| # - https://gist.github.com/mdklapwijk/ | |
| # | |
| # This program is free software; you can redistribute it and/or | |
| # modify it under the terms of the GNU General Public License | |
| # as published by the Free Software Foundation; either version 2 |
Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.
You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.
| #!/bin/bash | |
| # checks if an array contains the specified element | |
| containsElement () { | |
| local e | |
| for e in "${@:2}"; do [[ "$e" == "$1" ]] && return 0; done | |
| return 1 | |
| } | |
| REPO="git@github.com:USER/YOUR_PUPPET_REPO" |
| #!/bin/bash | |
| ### BEGIN INIT INFO | |
| # Provides: zram | |
| # Required-Start: | |
| # Required-Stop: | |
| # Default-Start: 2 3 4 5 | |
| # Default-Stop: 0 1 6 | |
| # Short-Description: Virtual Swap Compressed in RAM | |
| # Description: Virtual Swap Compressed in RAM | |
| ### END INIT INFO |
When running Puppet in masterless mode, meaning there is no Puppet Master for the node to connect to, one of the problems you have to solve is how to get all your Puppet modules onto the node. Without going into all the possible ways of doing this, one nice and clean way to solve the problem is to use a Puppetfile.
If you know what a Ruby gemfile is, you can guess what a Puppetfile is. If you don't, think of a very simple list declaring the modules that a node should get, including ways to get those modules. Like this:
forge 'forge.puppetlabs.com'
For some reason, starting a PXE boot installation of RHEL6.4 on UEFI systems is poorly documented. Simultaneously, the process is not terribly verbose when it fails. Here's what I had to do to get this to work.
We going to use Cobbler to take care of a lot of the gruntwork (TFTP, DHCP, etc). It's entirely possible to do it without Cobbler, but even accounting for its warts it will make you more
This gist assumes: