...
Before You Start
The primary purpose of the 6.4.0 release is to make SIMP compatible with R10K. This meant a major change to the installation
...
in a skeleton directory under /usr/share/simp. The purpose of this is so that no operational files are changed during installtioninstallation
of the RPMs. All this will be done by commands specifically run by the user.
...
This will create the Puppet environment called "production" under /etc/puppetlabs/code/environments and copy the SIMP hiera data hiera archies hierarchies from
the skeleton. It will also create the Secondary Environment (/var/simp/environments) and the Writeable Environment. See SIMP 6.4.0 ISO workflow for
...
There are 2 parts, Puppetfile, which is a shell that you should use to add any of you your own repositories. This shell includes the other file generated, Puppetfile.simp, which points
...
If you have modules in git repos, they can be added here in the Puppetfile and they will be deployed into the environment when r10k is run.
...
simp puppetfile generate --skeleton > " /etc/puppetlabs/code/environments/production//Puppetfile"
# To generate the simp Puppetfile.simp file:
simp puppetfile generate > " /etc/puppetlabs/code/environments/production/Puppetfile.simp
...
Deploy Modules into the Environment
R10K is used to deploy deploy the modules into the environment.
...
At this point you are ready to run simp config and bootstrap. In the future running the configuration will take care of creating and an environment
for you. Since this is not completely developed, that was done previously with the /usr/local/sbin/simpenv script. So you need to tell simp
...
or you can copy the data over if your environment will be short lived and you are not worried about changes in the original envirnmentenvironment.
Run /usr/local/sbin/simpenv --help for more information on creating a new environment.
...
simp puppetfile generate > " /etc/puppetlabs/code/environments/production/Puppetfile.simp
...