pupistry 0.0.4 → 0.0.5
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +10 -4
- data/lib/pupistry/config.rb +9 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: fb015d29aead0f609e5cab660c3a6e8438565bd6
|
|
4
|
+
data.tar.gz: 7ac9aa4a7cd18d7bc3ea1fa6431d0636a8599c59
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: d1a9b7489858b33f69aa23dd10521cda71a721f428f00a97808dafab95f6c59c697cd250c1dbad27e2f44645fbdb97cfd72aca61f29e9176326d12fb96e62a4f
|
|
7
|
+
data.tar.gz: 50701a9b7a46b610353d809e16926e3526362a7408858c08f76e4793122bbc2a509e8898d9cea1ee531692fce8316db596dc85ff299b0ce63dac8dd1ead11f57
|
data/README.md
CHANGED
|
@@ -122,12 +122,10 @@ nice easy life, Pupistry can generate you a bootstrap script for your platform.
|
|
|
122
122
|
# Bootstrap for Red Hat Enterprise Linux Platform
|
|
123
123
|
# Compatible with RHEL 7, CentOS 7 and maybe other variations.
|
|
124
124
|
|
|
125
|
-
rpm -ivh
|
|
126
|
-
rpm -ivh http://download.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm
|
|
125
|
+
rpm -ivh https://yum.puppetlabs.com/puppetlabs-release-el-7.noarch.rpm
|
|
127
126
|
|
|
128
127
|
yum update --assumeyes
|
|
129
|
-
yum install --assumeyes puppet ruby-devel rubygems
|
|
130
|
-
yum install --assumeyes gcc zlib-devel libxml2-devel patch
|
|
128
|
+
yum install --assumeyes puppet ruby-devel rubygems gcc zlib-devel libxml2-devel patch
|
|
131
129
|
|
|
132
130
|
gem install pupistry
|
|
133
131
|
mkdir /etc/pupistry
|
|
@@ -325,6 +323,14 @@ The bootstrap script goal is to get you from stock OS to running Pupistry and
|
|
|
325
323
|
doing your first Puppet run. After that - it's up to you and your Puppet
|
|
326
324
|
skills to make your node actually do something useful. :-)
|
|
327
325
|
|
|
326
|
+
Note that the node initialisation process is still susceptable to weaknesses
|
|
327
|
+
such as a bug in a new version of Puppet or Pupistry, or changes to the OS
|
|
328
|
+
packages. If this is a concern/issue for you and you want complete reliability,
|
|
329
|
+
then use the user data to build a host pre-loaded with Puppet and Pupistry and
|
|
330
|
+
then create an image of it using a tool like Packer. Doing this, you can make
|
|
331
|
+
it possible to build all the way to Puppet execution with no dependencies on any
|
|
332
|
+
third parties other than your VM provider and AWS S3.
|
|
333
|
+
|
|
328
334
|
|
|
329
335
|
# Tutorials
|
|
330
336
|
|
data/lib/pupistry/config.rb
CHANGED
|
@@ -46,7 +46,15 @@ module Pupistry
|
|
|
46
46
|
|
|
47
47
|
def self.find_and_load
|
|
48
48
|
$logger.debug "Looking for configuration file in common locations"
|
|
49
|
-
|
|
49
|
+
|
|
50
|
+
# If the HOME environmental hasn't been set (which can happen when
|
|
51
|
+
# running via some cloud user-data/init systems) the app will die
|
|
52
|
+
# horribly, we should set a HOME path default.
|
|
53
|
+
unless ENV['HOME']
|
|
54
|
+
$logger.warn "No HOME environmental set, defaulting to /tmp"
|
|
55
|
+
ENV['HOME'] = "/tmp"
|
|
56
|
+
end
|
|
57
|
+
|
|
50
58
|
# Locations in order of preference:
|
|
51
59
|
# settings.yaml (current dir)
|
|
52
60
|
# ~/.pupistry/settings.yaml
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: pupistry
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.0.
|
|
4
|
+
version: 0.0.5
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Jethro Carr
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2015-04-
|
|
11
|
+
date: 2015-04-15 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: aws-sdk-v1
|