4 files changed, 136 insertions, 0 deletions
diff --git a/config/bootstrap.yaml b/config/bootstrap.yaml
new file mode 100644
index 0000000..ce72bfb
--- /dev/null
+++ b/config/bootstrap.yaml
@@ -0,0 +1,44 @@
+---
+#
+# Puppet Bootstrap Configuration Parameters.
+#
+# This file is responsible to set custom values to your new puppet repository
+# to reflect the custom configuration for your infrastructure.
+#
+# This configuration is useful mostly after you cloned the puppet-boostrap module
+# and want to configure it to boostrap a whole puppetmaster infrastructure.
+#
+
+# The base domain for your infrastructure.
+bootstrap::base_domain: 'vagrantup.com'
+
+#
+# Root password.
+#
+# Use "mkpasswd -m sha-512" to generate root and first user's passwords.
+bootstrap::root::password: ''
+
+#
+# First user account
+#
+# Do not include "ssh-rsa " into the sshkey definition.
+bootstrap::first_user:           ''
+bootstrap::first_user::password: ''
+bootstrap::first_user::sshkey:   ''
+bootstrap::first_user::email:    ''
+
+#
+# First nodes
+#
+
+# Hostname of the first server
+bootstrap:first_hostname: ''
+
+# Create manifests and config for the first nodes?
+bootstrap::first_nodes:   false
+
+# MySQL password
+mysql::server::rootpw: ''
+
+# Puppet master db password
+nodo::role::master::db_password: ''
diff --git a/config/common.yaml b/config/common.yaml
new file mode 100644
index 0000000..006c5a8
--- /dev/null
+++ b/config/common.yaml
@@ -0,0 +1,45 @@
+---
+#
+# General
+#
+nodo::subsystem::apt::include_src: false
+nodo::subsystem::apt::use_next_release: false
+nodo::subsystem::monitor::use_nagios: false
+nodo::subsystem::monitor::address: "%{::fqdn}"
+
+#
+# Firewall
+#
+firewall::ssl_ratelimit: "s:ssl:200/min:20"
+firewall::local_net: false
+firewall::local::manage_host: true
+firewall::local::manage_iface: false
+
+#
+# Mail
+#
+mail::sympa::subdomain: "listas"
+mail::sympa::lang: "pt_BR"
+
+#
+# Monitoring
+#
+nodo::munin_node::allow: '127.0.0.1:192.168.0.[0-9]*:192.168.1.[0-9]*'
+
+#
+# Timezone and ntp
+#
+ntp::zone: "Brazil/East"
+ntp::pool: "south-america.pool.ntp.org"
+ntp::servers:
+  - 'a.ntp.br'
+  - 'b.ntp.br'
+  - 'c.ntp.br'
+
+#
+# Nameservers
+#
+# OpenDNS
+nodo::subsystem::resolver::nameservers:
+  - '208.67.222.222'
+  - '208.67.220.220'
diff --git a/config/hiera.yaml b/config/hiera.yaml
new file mode 100644
index 0000000..2e5600c
--- /dev/null
+++ b/config/hiera.yaml
@@ -0,0 +1,33 @@
+---
+:backends:
+  - yaml
+:yaml:
+  # Right now vagrant and puppet are not fully supporting
+  # a relative datadir. For it to work, we were forced to
+  # create a manifests/hiera symlink. This should be
+  # reconsidered in the future.
+  #
+  # See http://docs.vagrantup.com/v2/provisioning/puppet_apply.html
+  :datadir: '%{settings::confdir}/config'
+:hierarchy:
+  #
+  # Put in the secrets folder all sensitive information that
+  # wont be spread into every system if you're using the Hydra Suite.
+  #
+  # We also recommend to leave only encrypted data in your hiera config.
+  #
+  - 'secrets/node/%{::clientcert}'
+  - 'secrets/role/%{::nodo::role}'
+  - 'secrets/location/%{::nodo::location}'
+  - 'secrets/domain/%{::domain}'
+
+  #
+  # All other stuff goes in regular YAML files.
+  #
+  - 'node/%{::clientcert}'
+  - 'role/%{::nodo::role}'
+  - 'virtual/%{::virtual}'
+  - 'location/%{::nodo::location}'
+  - 'domain/%{::domain}'
+  - bootstrap
+  - common
diff --git a/config/node/puppet-bootstrap.example.org.yaml b/config/node/puppet-bootstrap.example.org.yaml
new file mode 100644
index 0000000..c108e7d
--- /dev/null
+++ b/config/node/puppet-bootstrap.example.org.yaml
@@ -0,0 +1,14 @@
+---
+#
+# MySQL
+#
+# The following password is public information and therefore
+# shall not be user on production.
+mysql::server::rootpw: '9pRfteNbSFFyrHhackme'
+
+#
+# Backup
+#
+nodo::subsystem::backup::localhost: false
+nodo::subsystem::backup::encryptkey: 'none'
+nodo::subsystem::backup::password: 'hacked'