Hot answers tagged

1

Unless things have changed in the past year, from my experience Foreman does not create environments. It just tells that host to use an existing environment (rather than the default). So the environment has to exist first before you can use it in Foreman.


1

The classical way to configure the environment is this: #Environments [development] modulepath =/etc/puppet/development/modules manifest = /etc/puppet/development/manifest/site.pp manifestdir = /etc/puppet/development/manifest [testing] modulepath =/etc/puppet/testing/modules manifest = /etc/puppet/testing/manifest/site.pp ...


1

As per the comments: The agent asked for the environment qa, whereas you showed site.pp of the environment production. So, better double check the environments on both sides, master and agent. :)


1

This configuration works for me as a r10k.yaml (using r10k 2.3.0): --- :cachedir: /var/cache/r10k :sources: :local: remote: file:///opt/repos/r10k basedir: /etc/puppet/environments The repository does not need to be a bare repository.


1

Configuring and running services under Mesos can be a complex operation or an easy one, and you should first define a schema of services you want to run under it, depending on your needs and goals, to get the soultion you want. I run a setup of >70 machines and a variety of different services under HAProxy for dynamic load balancing with Mesos-DNS and ...



Only top voted, non community-wiki answers of a minimum length are eligible