Version 37 (Romain Vrignaud, 11/17/2011 09:58 am)
h1. I'm not using Storeconfigs, how can I still use Foreman?
See [[Puppet Facts]]
h1. I'm using Storeconfigs, how can I populate various settings in Foreman that are required for hands free (unattended) installations?
See [[Puppet Facts]]
h1. I don't want to use Foreman for unattended installations can I disable it?
see [[Unattended_installations#How to desactivate unattended installation ?]]
yes, edit config/settings.yaml and add this line:
and restart your foreman instance.
This will will not ask you to enter additional information (e.g. mac address etc)
h1. How can I migrate from an other External Node Classifier to Foreman ?
see [[External Nodes#Import-your-external-node-setup-from-an-older-external-node-setup]]
h1. How do I configure my database ?
see [[Database configuration]]
h1. What about other operating systems?
Foreman currently supports RedHat/Fedora, Debian/Ubuntu and Solaris Jumpstart
it has been successfully tested on CentOS 3,4,5 Fedora 10-11, Ubuntu 9.04 and Solaris 8-10 on Sparc.
If you have any other operating system you would like to see added to Foreman, please contact us and we would be happy to add it.
for Jumpstart support, as Solaris doesn't support nativity accessing the profile data dynamically, its required to create some workarounds
example for those are found at the *extras/jumpstart* directory.
You may find the dynamic profile and dynamic finish at the following URL's:
It is also required to add vendor options to your dhcp server if you plan to boot from network on the sparc platform.
h1. Will Foreman manage non OpenSource services (e.g. DNS/DHCP etc) ?
Yes! we understand that many enterprises relay on non opensource infrastrucutre as well. We support MS DNS and DHCP services
If you have any additional requirements, please enter a feature request.
h1. How do I fix this error: "Unable to find directory $confdir/environments/$environment/modules in environment master" ?
If you've followed http://docs.puppetlabs.com/guides/environment.html#configuring-environments-on-the-puppet-master to
create a multi-environment puppet configuration, you're initial rake may look something like this:
rake puppet:import:puppet_classes RAILS_ENV=production
Evaluating possible changes to your installation
Problems were detected during the evaluation phase
Unable to find directory $confdir/environments/$environment/modules in environment master
Please fix these issues and try again
This is because Foreman does not currently evaluate $confdir. There is a feature request open on this issue. In the
meantime, hard code your $confdir in your puppet.conf.
h1. How do I fix the puppet class import problem with multiple puppet environment ?
If Foreman don't seems to be aware of all your environment and is able to import only your "production" environment (see http://theforeman.org/issues/1159),
try to add ":puppetconfdir: /etc/puppet/puppet.conf" in your settings.yaml.
h1. Whats planned for the next major release?
See the "roadmap":http://theforeman.org/projects/foreman/roadmap
If you want additional features, please open a new feature request "here":http://theforeman.org/projects/foreman/issues/new !