falkorlib 0.8.5 → 0.8.6

data/templates/mkdocs/docs/README.md.erb

@@ -10,10 +10,10 @@
 
 This is the main page of the documentation for this repository, which relies on [MkDocs](http://www.mkdocs.org/) and the [Read the Docs](http://readthedocs.io) theme. It proposes to detail the following elements:
 
-* The [organization and directory layout](layout.md)
-* Complete [Installation](setup/index.md) notes, including:
-    - [Pre-requisites / Preliminary software](setup/preliminaries.md) to install
-* How to [contribute](contributing/index.md) to the development of this project. In particular, we detail:
-     - the steps to follow to [setup this repository](contributing/setup.md)
-     - information as regard the [semantic versioning](contributing/versioning.md) of this project
-     - Apart form the directory layout, we will cover various configuration aspects (mainly the [git-flow](https://github.com/nvie/gitflow) workflow)
+* The general [organization and directory layout](layout.md)
+* Complete [Installation and Setup notes](setup.md) for this repository
+<% if File.exists?(File.join(config[:rootdir], 'Vagrantfile')) %>
+* Overview of the [Vagrant](https://www.vagrantup.com/) configuration proposed
+<% end %>
+* (...)
+* [Contributing notes](contributing/index.md) and [semantic versioning](contributing/versioning.md) information of this project

data/templates/mkdocs/docs/contributing/setup.md.erb

@@ -1,4 +1,4 @@
-There is a number of pre-requisite programs / framework you shall install to be able to correctly contribute to this project.
+There is a number of pre-requisite programs / framework you shall install to be able to correctly contribute to this project -- see [../setup.md](../setup.md) for detailed instructions.
 
 <% if config[:gitflow] %>
 __Git Branching Model__
@@ -15,7 +15,7 @@ Thus you are more than encouraged to install the [git-flow](https://github.com/n
 
 __Repository Setup__
 
-As mentioned in the [installation notes](../setup/install.md), to make your local copy of the repository ready to use the [git-flow](https://github.com/nvie/gitflow) workflow
+As mentioned in the [installation notes](../setup.md), to make your local copy of the repository ready to use the [git-flow](https://github.com/nvie/gitflow) workflow, run:
 
 <% if config[:make] %>
     $> make setup
@@ -23,4 +23,4 @@ As mentioned in the [installation notes](../setup/install.md), to make your loca
     $> rake setup
 <% end %>
 
-This will also initiate the [Git submodules of this repository](.gitmodules) for this repository.
+Semantic versioning informations happening upon the release operations are detailed in [`versioning.md`](versioning.md).

data/templates/mkdocs/docs/layout.md.erb

@@ -1,10 +1,9 @@
 
-This repository is organized as follows:
+This repository is organized as follows (use `tree -L 2` to complete):
 
 ~~~bash
 .
-├── LICENSE.txt     # Licence of this project
-<% unless options[:rake] %>
+<% if options[:rake] %>
 ├── Rakefile        # Ruby Rake configuration
 <% else %>
 ├── Makefile        # GNU Make configuration
@@ -13,5 +12,27 @@ This repository is organized as follows:
 ├── VERSION         # /!\ DO NOT EDIT. Current repository version
 ├── docs/           # [MkDocs](mkdocs.org) main directory
 ├── mkdocs.yml      # [MkDocs](mkdocs.org) configuration
-└── src/            # Source Code
+<% if File.exists?(File.join(config[:rootdir], '.ruby-version')) %>
+├── .ruby-{version,gemset}  # [RVM](https://rvm.io/) (Ruby Version Manager) configuration
+<% end %>
+<% if File.exists?(File.join(config[:rootdir], 'Gemfile')) %>
+├── Gemfile[.lock]   # [Bundler](https://bundler.io/) configuration
+<% end %>
+<% if File.exists?(File.join(config[:rootdir], '.envrc')) %>
+├── .envrc           # Local direnv configuration -- see https://direnv.net/
+│                    # Assumes you have installed in ~/.config/direnv/direnvrc
+│                    # the version proposed on
+│                    #    https://raw.githubusercontent.com/Falkor/dotfiles/master/direnv/direnvrc
+<% end %>
+<% if File.exists?(File.join(config[:rootdir], '.python-version')) %>
+├── .python-{version,virtualenv}  # Pyenv/Virtualenv configuration
+<% end %>
+<% if File.exists?(File.join(config[:rootdir], 'Vagrantfile')) %>
+├── Vagrantfile     # Vagrant configuration file - see https://www.vagrantup.com/
+└── vagrant/        # Complementary Vagrant configuration
+    ├── config.yaml         # custom config
+    ├── config.yaml.sample
+    ├── puppet/             # puppet provisionning
+    └── scripts/            # scripts (bootstrap etc.) for vagrant VM provisioning
+<% end %>
 ~~~

data/templates/mkdocs/docs/setup.md.erb

@@ -0,0 +1,315 @@
+# Repository Setup and Preliminaries
+
+This projects relies on several components you need to have installed on your system.
+
+* [Git](https://git-scm.com/)
+* __On Mac OS__: [Homebrew](http://brew.sh/) (The missing package manager for macOS)
+
+The below instructions will help you to configure your local copy of this repository and eventually install software dependencies required for this project.
+
+_Note_: in the following instructions, terminal commands are prefixed by a virtual prompt `$>`which obviously **does not** belong to the command.
+
+-----------
+
+<% unless config[:forge].empty? %>
+This repository is hosted on [<%= FalkorLib::Config::Bootstrap::DEFAULTS[:forge][ config[:forge].to_sym ][:name] %>](<%= config[:project_page] %>).
+<% if (config[:forge] == :gitlab) %>
+Git interactions with this repository (push, pull etc.) are performed over SSH using the port 8022
+<% end %>
+To clone this repository, proceed as follows (adapt accordingly):
+
+```bash
+$> mkdir -p ~/<%= config[:rootdir].gsub(ENV['HOME'] + '/', '').gsub(File.basename(config[:rootdir]), '') %>
+$> cd ~/<%= config[:rootdir].gsub(ENV['HOME'] + '/', '').gsub(File.basename(config[:rootdir]), '') %>
+$> git clone <%= config[:origin] %> <%= File.basename(config[:rootdir]) %>
+$> cd <%= File.basename(config[:rootdir]) %>
+# /!\ IMPORTANT: run 'make setup' only **AFTER** Pre-requisites sofftware are installed
+```
+<% end %>
+To setup you local copy of this repository (**after** pre-requisites are satisfied), simply run:
+
+```bash
+<% if config[:rake] %>
+$> rake setup    # Under Mac OS / Linux
+<% else %>
+$> make setup    # Under Mac OS / Linux
+<% end %>
+```
+
+This will initiate the Git submodules of this repository (see `.gitmodules`) and setup the [git flow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) layout for this repository. Later on, you can update your local branches by running:
+
+<% if config[:rake] %>
+     $> rake up
+<% else %>
+     $> make up
+<% end %>
+
+If upon pulling the repository, you end in a state where another collaborator have upgraded the Git submodules for this repository, you'll end in a dirty state (as reported by modifications within the `.submodules/` directory). In that case, just after the pull, you **have to run** `<%= config[:rake] ? 'r' : 'm' %>ake up` to ensure consistency with regards the Git submodules:
+
+Finally, you can upgrade the Git submodules to the latest version by running:
+
+<% if config[:rake] %>
+    $> rake git:submodules:upgrade
+<% else %>
+    $> make upgrade
+<% end %>
+
+
+## Pre-requisites Software
+
+Install the following software, depending on your running platform:
+
+| Platform | Software                                              | Description                           | Usage                   |
+|----------|-------------------------------------------------------|---------------------------------------|-------------------------|
+| Mac OS   | [Homebrew](http://brew.sh/)                           | The missing package manager for macOS | `brew install ...`      |
+| Mac OS   | [Brew Cask Plugin](https://caskroom.github.io)        | Mac OS Apps install made easy         | `brew cask install ...` |
+| Mac OS   | [iTerm2](https://www.iterm2.com/)                     | _(optional)_ enhanced Terminal        |                         |
+| Windows  | [Git for Windows](https://git-for-windows.github.io/) | I'm sure you guessed                  |                         |
+| Windows  | [SourceTree](https://www.sourcetreeapp.com/)          | _(optional)_ enhanced git GUI         |                         |
+| Windows  | [Virtual Box](https://www.virtualbox.org/)            | Free hypervisor provider for Vagrant  |                         |
+| Windows  | [Vagrant](https://www.vagrantup.com/downloads.html)   | Reproducible environments made easy.  |                         |
+
+Follow the below **custom** instructions depending on your running platform and Operating System.
+
+#### Mac OS X
+
+Once you have [Homebrew](http://brew.sh/) installed:
+
+```bash
+$> brew install git-core git-flow    # (newer) Git stuff
+$> brew install mkdocs               # (optional) install mkdocs
+$> brew install pyenv pyenv-virtualenv direnv # see https://varrette.gforge.uni.lu/tutorials/pyenv.html
+$> brew tap caskroom/cask            # install brew cask  -- see https://caskroom.github.io/
+$> brew cask install virtualbox      # install virtualbox -- see https://www.virtualbox.org/
+$> brew cask install vagrant         # install Vagrant    -- see https://www.vagrantup.com/downloads.html
+$> brew cask install vagrant-manager # see http://vagrantmanager.com/
+$> brew cask install docker          # install Docker -- https://docs.docker.com/engine/installation/mac/
+```
+
+_Note_: later on, you might wish to use the following shell function to update the software installed using [Homebrew](http://brew.sh/).
+
+```bash
+bup () {
+	echo "Updating your [Homebrew] system"
+	brew update
+	brew upgrade
+	brew cu
+	brew cleanup
+	brew cask cleanup
+}
+```
+
+#### Linux
+
+
+```bash
+# Below instructions for Debian/Ubuntu
+# Adapt the package names (and package manager) in case you are using another Linux distribution.
+$> sudo apt-get update
+$> sudo apt-get install git git-flow build-essential
+$> sudo apt-get install rubygems virtualbox vagrant virtualbox-dkms
+```
+
+#### Windows
+
+On Windows (10, 7/8 should also be OK) you should download and install the following tools:
+
+* [MobaXterm](http://mobaxterm.mobatek.net). You can also check out the [MobaXterm demo](http://mobaxterm.mobatek.net/demo.html) which shows an overview of its features.
+    - See also [official ULHPC SSH access instructions](https://hpc.uni.lu/users/docs/access/access_windows.html)
+
+* [VirtualBox](https://www.virtualbox.org/wiki/Downloads), download the latest [VirtualBox 'Windows hosts' installer](https://www.virtualbox.org/wiki/Downloads)  and [VirtualBox Extension Pack](https://www.virtualbox.org/wiki/Downloads) .
+    - First, install VirtualBox with the default settings. Note that a warning will be issued that your network connections will be temporarily impacted, you should continue.
+    - Then, run the downloaded extension pack (.vbox-extpack file), it will open within the VirtualBox Manager and you should let it install normally.
+
+* [Vagrant](https://www.vagrantup.com/downloads.html), download the latest [Windows (64 bit) Vagrant installer](https://www.vagrantup.com/downloads.html)
+    - Proceed with the installation, no changes are required to the default setup.
+
+* [Git](https://git-scm.com/downloads), download the latest [Git installer](https://git-scm.com/download/win)
+
+The Git installation requires a few changes to the defaults, make sure the following are selected in the installer:
+
+   - Select Components: _Use a TrueType font in all console windows)_
+   - Adjusting your PATH environment: _Use Git and optional Unix tools from the Windows Command Prompt_
+   - Configuring the line ending conversions: _Checkout Windows-style, commit Unix-style line endings)_
+   - Configuring the terminal emulator to use with Git Bash: _Use MinTTY (the default terminal of MSYS2)_
+   - Configuring extra options: _Enable symbolic links_
+
+Please note that to clone a Git repository which contains symbolic links (symlinks), you **must start a shell** (Microsoft PowerShell in this example, but a Command Prompt - cmd.exe - or Git Bash shell should work out fine) **with elevated (Administrator) privileges**. This is required in order for git to be able to create symlinks on Windows:
+
+* Start Powershell:
+    1. In the Windows Start menu, type PowerShell
+    2. Normally PowerShell will appear as the first option on the top as **Best match**
+    3. Right click on it and select "Run as administrator"
+
+See also the instructions and screenshots provided on this [tutorial](http://rr-tutorials.readthedocs.io/en/latest/setup/#windows).
+
+<% if File.exists?(File.join(config[:rootdir], 'Vagrantfile')) %>
+## Vagrant
+
+This repository comes with a `Vagrantfile` at the root of the repository which, together with the associated configuration (under `vagrant/`), pilot the provisioning of Virtual Machine(s) using [Vagrant](http://www.vagrantup.com/).
+
+[Vagrant](http://vagrantup.com/) uses [Oracle's VirtualBox](http://www.virtualbox.org/)
+to build configurable, lightweight, and portable virtual machines dynamically.
+
+* [Reference installation notes](http://docs.vagrantup.com/v2/installation/) -- assuming you have installed [Oracle's VirtualBox](http://www.virtualbox.org/)
+* [installation notes on Mac OS](http://sourabhbajaj.com/mac-setup/Vagrant/README.html) using [Homebrew](http://brew.sh/) and [Cask](http://sourabhbajaj.com/mac-setup/Homebrew/Cask.html)
+
+Once installed, check the list of VMs ready to be deployed using
+
+```bash
+$> vagrant status
+# Follow instructions to (eventually) install the missing plugings
+$> vagrant plugin install
+$> vagrant plugin install vagrant-hosts
+$> vagrant plugin install vagrant-vbguest
+$> vagrant plugin install vagrant-cachier
+$> vagrant plugin install terminal-table deep_merge
+$> vagrant status
+Current machine states:
+
+[...]
+
+The environment has not yet been created. Run `vagrant up` to
+create the environment. If a machine is not created, only the
+default provider will be shown. So if a provider is not listed,
+then the machine is not created for that environment.
+```
+
+See [`vagrant.md`](vagrant.md) for further details.
+<% end %>
+
+<% if File.exists?(File.join(config[:rootdir], '.ruby-version')) %>
+## Ruby setup with RVM
+
+In order to have a consistent Ruby environment among the collaborators of this project, [Bundler](http://bundler.io/) is used in complement to [RVM](https://rvm.io/).
+
+* Configuration of [Bundler](http://bundler.io/) is made via the [`Gemfile[.lock]` files](http://bundler.io/gemfile.html).
+* [RVM](https://rvm.io/) gives you compartmentalized independent ruby setups. This means that ruby, gems and irb are all separate and self-contained - from the system, and from each other projects.  Sandboxing with [RVM](https://rvm.io/) is straight-forward via the [notion of gemsets](https://rvm.io/gemsets) and is managed via the `.ruby-{version,gemset}` files.
+    - [RVM installation](https://rvm.io/rvm/install)
+
+Once RVM is installed, proceed as follows:
+
+```bash
+rvm list   # SHow currently installed version
+rvm list know # Show known configuration
+rvm install $(head .ruby-version)
+# Activate the gemset environment by reentering into the directory
+cd ..
+cd -
+rvm current  #check current ruby environment -- should match $(head .ruby-version)@head .ruby-gemset)
+```
+<% end %>
+<% if File.exists?(File.join(config[:rootdir], 'Gemfile')) %>
+Assuming your Ruby environment is correctly setup (again, use `rvm current` to check it), you can install the package dependencies detailed in the [`Gemfile`](Gemfile) through  [Bundler](http://bundler.io/) as follows:
+
+```bash
+gem install bundler
+bundle
+```
+
+<% end %>
+<% if File.exists?(File.join(config[:rootdir], 'Rakefile')) %>
+The various operations that can be conducted from this repository are piloted from a [`Rakefile`](https://github.com/ruby/rake) and assumes you have a running [Ruby](https://www.ruby-lang.org/en/) installation
+
+If things are fine, you should  be able to access the list of available tasks by running:
+
+       $> rake -T
+
+You probably want to activate the bash-completion for rake tasks, such as the one provided [here](https://github.com/ai/rake-completion).
+
+<% end %>
+<% if File.exists?(File.join(config[:rootdir], '.envrc')) %>
+## Python Virtualenv / Pyenv and Direnv
+
+In order to have a consistent Python environment among the collaborators of this project, the use of [`virtualenv`](https://pypi.org/project/virtualenv/) (a tool to create isolated virtual Python environments) is strongly encouraged.
+Based on the guidelines of [this blog post](https://varrette.gforge.uni.lu/tutorials/pyenv.html), this project relies on two additional tools facilitating the setup of the python environment expected within this project:
+
+* [`pyenv`](https://github.com/pyenv/pyenv)
+* [`pyenv-virtualenv`](https://github.com/pyenv/pyenv-virtualenv)
+    - see [Note on virtualenv and venv](https://github.com/pyenv/pyenv-virtualenv#virtualenv-and-venv):
+    `pyenv-virtualenv` uses `python -m venv` if it is available (CPython 3.3 and newer) and the `virtualenv` command is not available.
+* [Direnv](https://direnv.net/) allowing to automatically activate/deactivate the project virtualenv when entering/leaving the directory hosting your local copy of this repository.
+    - [direnv](https://direnv.net/) has a standard library of functions / layout (see [direnv-stdlib](https://github.com/direnv/direnv/blob/master/stdlib.sh) or the associated  [man page](https://github.com/direnv/direnv/blob/master/man/direnv-stdlib.1.md)), which you can override  with your own set of function though [`~/.config/direnv/direnvrc`](https://github.com/Falkor/dotfiles/blob/master/direnv/direnvrc).
+    - Below instructions will make you install [this version](https://github.com/Falkor/dotfiles/blob/master/direnv/direnvrc)
+
+Installation  instructions -- see also [this blog post](https://varrette.gforge.uni.lu/tutorials/pyenv.html)
+
+```bash
+### Mac OS
+$> brew install pyenv pyenv-virtualenv direnv
+### Linux
+curl -L https://raw.githubusercontent.com/pyenv/pyenv-installer/master/bin/pyenv-installer | bash
+$> git clone https://github.com/pyenv/pyenv-virtualenv.git $(pyenv root)/plugins/pyenv-virtualenv
+$> { apt-get | yum } install direnv    # direnv install
+```
+
+You then need adapt your environment _i.e._ `~/.{profile | bash* | zsh* etc.}` to support [pyenv shims](https://github.com/yyuu/pyenv#understanding-shims), [virtualenv](http://docs.python-guide.org/en/latest/dev/virtualenv
+s/) and [direnv](https://direnv.net/). Ex:
+
+```bash
+# To add in your favorite shell configuration (.bashrc, .zshrc etc.)
+#
+# - pyenv: https://github.com/pyenv/pyenv
+# - pyenv-virtualenv: https://github.com/pyenv/pyenv-virtualenv
+if [ -n "$(which pyenv)" ]; then
+  eval "$(pyenv init -)"
+  eval "$(pyenv virtualenv-init -)"
+  export PYENV_VIRTUALENV_DISABLE_PROMPT=1
+fi
+#
+# - direnv: https://direnv.net/
+if [ -n "$(which direnv)" ]; then
+  eval "$(direnv hook $(basename $SHELL))"
+  # export DIRENV_WARN_TIMEOUT=100s
+fi
+```
+
+If you're using [oh-my-zsh](http://ohmyz.sh/), you probably want to enable the [pyenv plugin](https://github.com/Falkor/dotfiles/blob/master/oh-my-zsh/.zshrc#L73)
+
+Finally, to setup direnv, simply run:
+
+```bash
+make setup-direnv
+```
+
+Running `direnv allow` (this will have to be done only once), you should automatically enable the virtualenv `<%= config[:name].downcase %>` based on the python version specified in `.python-version`. You'll eventually need to install the appropripriate Python version with `pyenv`:
+
+```bash
+pyenv versions   # Plural: show all versions
+pyenv install $(head .python-version)
+# Activate the virtualenv by reentering into the directory
+cd ..
+cd -
+```
+<% end %>
+<% if File.exists?(File.join(config[:rootdir], 'requirements.txt')) %>
+From that point, you should install the required packages using:
+
+    pip install -r requirements.txt
+
+Alternatively, you can use `make setup-python`
+
+<% end %>
+
+## Post-Installations checks
+
+(Eventually) Make yourself known to Git
+
+```bash
+$> git config –-global user.name  "Firstname LastName"              # Adapt accordingly
+$> git config –-global user.email "Firstname.LastName@domain.org"   # Adapt with your mail
+# Eventually, if you have a GPG key, use the public key to sign your commits/tags
+$> git config --global user.helper osxkeychain       # Only on Mac OS
+$> git config --global user.signingkey <fingerprint> # Ex: git config --global user.signingkey 5D08BCDD4F156AD7
+# you can get your key fingerprint (prefixed by 0x) with 'gpg -K --fingerprint | grep sec'
+```
+
+Now you can complete the setup of your copy of this repository by running
+
+```bash
+<% if config[:rake] %>
+$> rake setup    # Under Mac OS / Linux
+<% else %>
+$> make setup    # Under Mac OS / Linux
+<% end %>
+```

data/templates/mkdocs/docs/vagrant.md.erb

@@ -0,0 +1,85 @@
+## Reproducible VM deployment with Vagrant
+
+This repository comes with a `Vagrantfile` at the root of the repository which, together with the associated configuration (under `vagrant/`), pilots the provisioning of Virtual Machine(s) using [Vagrant](http://www.vagrantup.com/).
+
+[Vagrant](http://vagrantup.com/) uses [Oracle's VirtualBox](http://www.virtualbox.org/)
+to build configurable, lightweight, and portable virtual machines dynamically.
+
+* [Reference installation notes](http://docs.vagrantup.com/v2/installation/) -- assuming you have installed [Oracle's VirtualBox](http://www.virtualbox.org/)
+* [installation notes on Mac OS](http://sourabhbajaj.com/mac-setup/Vagrant/README.html) using [Homebrew](http://brew.sh/) and [Cask](http://sourabhbajaj.com/mac-setup/Homebrew/Cask.html)
+
+#### Plugins installation
+
+Once installed, check the list of VMs ready to be deployed using
+
+```bash
+$> vagrant status
+# Follow instructions to (eventually) install the missing plugings
+$> vagrant plugin install
+$> vagrant plugin install vagrant-hosts
+$> vagrant plugin install vagrant-vbguest
+$> vagrant plugin install vagrant-cachier
+$> vagrant plugin install terminal-table deep_merge
+$> vagrant status
+Current machine states:
+
+[...]
+
+The environment has not yet been created. Run `vagrant up` to
+create the environment. If a machine is not created, only the
+default provider will be shown. So if a provider is not listed,
+then the machine is not created for that environment.
+```
+
+#### Vagrant VM(s) deployment
+
+By default, the following boxes will be deployed upon `vagrant up`:
+
+* `default`: default VM
+
+To initiate the deployment:
+
+```bash
+$> vagrant status
+$> vagrant up
+[...]
++--------------|-------------------------|---------|----------|------------|----------------|------------+
+|                                     Virtual environment deployed on Vagrant                            |
++--------------|-------------------------|---------|----------|------------|----------------|------------+
+| Name         | Hostname                | OS      | vCPU/RAM | Role       | Description    | IP         |
++--------------|-------------------------|---------|----------|------------|----------------|------------+
+| <hostname>   | <hostname>.vagrant.dev  | centos7 | 2/1024   | default    | <description>  | 10.10.1.2  |
+| [...]        |                         |         |          |            |                |            |
++--------------|-------------------------|---------|----------|------------|----------------|------------+
+- Virtual Vagrant infrastructure successfully deployed!
+```
+
+You can ssh into any of the deployed machine afterwards:
+
+```bash
+$> vagrant ssh [<name>]
+```
+
+#### Vagrant boxes provisionning
+
+When you run `vagrant up <name>` to boot the VM, the following default provisioning are applied (shell scripts are located in `vagrant/scripts/`):
+
+| Script           | Type   | Description                           |
+|------------------|--------|---------------------------------------|
+| `bootstrap.sh`   | shell  | Install puppet and defaults packages  |
+
+In addition, a [Puppet](https://puppet.com/)-based provisionning in configured, operated by calling `puppet apply` (i.e. without a Puppet Master). To make the best use of it:
+
+1. associate a `role` name to each of your VM (default role: `default`)
+     - you can use the `:role: <name>` YAML entry in `vagrant/config.yaml` or add `:role => '<name>'` in the appropriate `:vms` hash table entry within the root `Vagrantfile`
+     - use the `:puppet_modules` entry to list the [puppet modules](https://forge.puppet.com/) required for this role
+2. create a new [hiera](https://puppet.com/docs/puppet/latest/hiera_intro.html) YAML configuration under `vagrant/puppet/hieradata/<name>.yaml`.
+     - list the profiles you want to see applied under the `profiles:` key, and append the puppet classes parameters you want to set using [hiera](https://puppet.com/docs/puppet/latest/hiera_automatic.html#class_parameters)
+3. (eventually) create the [puppet manifest(s)](https://puppet.com/docs/puppet/latest/puppet_language.html) for each declared profile under `vagrant/puppet/site/profiles/manifests/`
+     - Ex: `profile::pxe::server` is defined in `vagrant/puppet/site/profiles/manifests/pxe/server.pp`
+
+That should be sufficient. You can test on demand the application of puppet provisionning using
+
+```
+vagrant provision --provision-with puppet
+```