Foreman settings

Support
1

I am using the version I got from github which declares it to be 0.3 in FOREMAN_ROOT/VERSION

I noticed that in this version, there is a 'Foreman Settings' option in 'Settings Menu' of the web app that didn't appear in the 0.3 tarball so I definitely gather that the one I got from github is newer.

Anyway, I gather that this populated from FOREMAN_ROOT/config/settings.yaml (at least as much as it could and filled the rest with defaults) and now, there's really no reason to manually maintain config/settings.yaml any longer but rather I should just maintain these settings in the web app. Is that correct?

··· -- Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white@ttiltd.com 1.800.869.6908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ www.ttiassessments.com

Need help communicating between generations at work to achieve your desired success? Let us help!

2

> I am using the version I got from github which declares it to be 0.3 in FOREMAN_ROOT/VERSION
>
> I noticed that in this version, there is a 'Foreman Settings' option in 'Settings Menu' of the web app that didn't appear in the 0.3 tarball so I definitely gather that the one I got from github is newer.
>
> Anyway, I gather that this populated from FOREMAN_ROOT/config/settings.yaml (at least as much as it could and filled the rest with defaults) and now, there's really no reason to manually maintain config/settings.yaml any longer but rather I should just maintain these settings in the web app. Is that correct?

Yep, you are correct, this is one of the features of the upcoming 0.4 release.

see Foreman configuration - Foreman
for more information.

Ohad

··· On Tue, Aug 9, 2011 at 6:03 PM, Craig White wrote:

–
Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white@ttiltd.com
1.800.869.6908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ www.ttiassessments.com

Need help communicating between generations at work to achieve your desired success? Let us help!

–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en.

3

>> I am using the version I got from github which declares it to be 0.3 in FOREMAN_ROOT/VERSION
>>
>> I noticed that in this version, there is a 'Foreman Settings' option in 'Settings Menu' of the web app that didn't appear in the 0.3 tarball so I definitely gather that the one I got from github is newer.
>>
>> Anyway, I gather that this populated from FOREMAN_ROOT/config/settings.yaml (at least as much as it could and filled the rest with defaults) and now, there's really no reason to manually maintain config/settings.yaml any longer but rather I should just maintain these settings in the web app. Is that correct?
>
> Yep, you are correct, this is one of the features of the upcoming 0.4 release.
>
> see Foreman configuration - Foreman
> for more information.

··· On Aug 9, 2011, at 8:09 AM, Ohad Levy wrote: > On Tue, Aug 9, 2011 at 6:03 PM, Craig White wrote: ---- ahh - new documentation since I checked - thanks. Are you going to put :require_ssl in the web app or will that remain the exclusive domain of config/settings.yaml ?

Craig

4

>
>
>>> I am using the version I got from github which declares it to be 0.3 in FOREMAN_ROOT/VERSION
>>>
>>> I noticed that in this version, there is a 'Foreman Settings' option in 'Settings Menu' of the web app that didn't appear in the 0.3 tarball so I definitely gather that the one I got from github is newer.
>>>
>>> Anyway, I gather that this populated from FOREMAN_ROOT/config/settings.yaml (at least as much as it could and filled the rest with defaults) and now, there's really no reason to manually maintain config/settings.yaml any longer but rather I should just maintain these settings in the web app. Is that correct?
>>
>> Yep, you are correct, this is one of the features of the upcoming 0.4 release.
>>
>> see Foreman configuration - Foreman
>> for more information.
> ----
> ahh - new documentation since I checked - thanks. Are you going to put :require_ssl in the web app or will that remain the exclusive domain of config/settings.yaml ?

SSL, Login, unattended and puppet.conf path are the only 4 settings
(for the moment) that needs to be in the setting.yaml file.

Ohad

··· On Tue, Aug 9, 2011 at 6:29 PM, Craig White wrote: > On Aug 9, 2011, at 8:09 AM, Ohad Levy wrote: >> On Tue, Aug 9, 2011 at 6:03 PM, Craig White wrote: > > Craig > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To post to this group, send email to foreman-users@googlegroups.com. > To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en. > >
5

Thanks for this thread guys. I just updated to the nightly not too
long ago and started running into issues. Didn't realize that
settings had moved! This got me in the right direction and back up
and running.

Regards,
Jake

··· On Aug 9, 10:09 am, Ohad Levy wrote: > On Tue, Aug 9, 2011 at 6:03 PM, Craig White wrote: > > I am using the version I got from github which declares it to be 0.3 in FOREMAN_ROOT/VERSION > > > I noticed that in this version, there is a 'Foreman Settings' option in 'Settings Menu' of the web app that didn't appear in the 0.3 tarball so I definitely gather that the one I got from github is newer. > > > Anyway, I gather that this populated from FOREMAN_ROOT/config/settings.yaml (at least as much as it could and filled the rest with defaults) and now, there's really no reason to manually maintain config/settings.yaml any longer but rather I should just maintain these settings in the web app. Is that correct? > > Yep, you are correct, this is one of the features of the upcoming 0.4 release. > > seehttp://theforeman.org/projects/foreman/wiki/Foreman_configuration > for more information. > > Ohad > > > > > > > > > > > -- > > Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.wh...@ttiltd.com > > 1.800.869.6908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~www.ttiassessments.com > > > Need help communicating between generations at work to achieve your desired success? Let us help! > > > -- > > You received this message because you are subscribed to the Google Groups "Foreman users" group. > > To post to this group, send email to foreman-users@googlegroups.com. > > To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/foreman-users?hl=en.
6

Using the nightly from Sept 7th, I've noticed some settings aren't
being respected, either in settings.yaml or in the new Foreman
Settings. The first is "Puppet Run". While I'm in the process of
setting it up, I have it set to False in the web interface however the
button is still enabled. The other option I can't seem to disable is
the Unattended feature. Right now I'm still testing that ability in
my environment and have it set to false in settings.yaml, but the
button "Build" is enabled.

This is my current settings.yaml,

··· On Aug 9, 12:52 pm, Ohad Levy wrote: > On Tue, Aug 9, 2011 at 6:29 PM, Craig White wrote: > > > On Aug 9, 2011, at 8:09 AM, Ohad Levy wrote: > > >> On Tue, Aug 9, 2011 at 6:03 PM, Craig White wrote: > >>> I am using the version I got from github which declares it to be 0.3 in FOREMAN_ROOT/VERSION > > >>> I noticed that in this version, there is a 'Foreman Settings' option in 'Settings Menu' of the web app that didn't appear in the 0.3 tarball so I definitely gather that the one I got from github is newer. > > >>> Anyway, I gather that this populated from FOREMAN_ROOT/config/settings.yaml(at least as much as it could and filled the rest with defaults) and now, there's really no reason to manually maintain config/settings.yamlany longer but rather I should just maintain these settings in the web app. Is that correct? > > >> Yep, you are correct, this is one of the features of the upcoming 0.4 release. > > >> seehttp://theforeman.org/projects/foreman/wiki/Foreman_configuration > >> for more information. > > ---- > > ahh - new documentation since I checked - thanks. Are you going to put :require_ssl in the web app or will that remain the exclusive domain of config/settings.yaml? > > SSL, Login, unattended and puppet.conf path are the only 4 settings > (for the moment) that needs to be in the setting.yaml file. > > Ohad > > > > > > > > > > > Craig > > > -- > > You received this message because you are subscribed to the Google Groups "Foreman users" group. > > To post to this group, send email to foreman-users@googlegroups.com. > > To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/foreman-users?hl=en.

:modulepath: /etc/puppet/modules/
#:tftppath: tftp/
#:rrd_report_url: report/
:require_ssl: true
#:ldap: true
:login: false
#your default puppet server - can be overridden in the host level
#if none specified, plain “puppet” will be used.
:puppet_server:
:unattended: false
#use the following setting to override the default 30 minutes puppet
run interval - value must be in minutes
#:puppet_interval: 60
#:document_root: /var/www

Thanks

  • Trey
7

while I did a really quick test and was unable to reproduce, its
probably a bug, would you mind creating a new issue?

thanks

··· On Fri, Sep 9, 2011 at 5:47 PM, treydock wrote: > > > On Aug 9, 12:52 pm, Ohad Levy wrote: >> On Tue, Aug 9, 2011 at 6:29 PM, Craig White wrote: >> >> > On Aug 9, 2011, at 8:09 AM, Ohad Levy wrote: >> >> >> On Tue, Aug 9, 2011 at 6:03 PM, Craig White wrote: >> >>> I am using the version I got from github which declares it to be 0.3 in FOREMAN_ROOT/VERSION >> >> >>> I noticed that in this version, there is a 'Foreman Settings' option in 'Settings Menu' of the web app that didn't appear in the 0.3 tarball so I definitely gather that the one I got from github is newer. >> >> >>> Anyway, I gather that this populated from FOREMAN_ROOT/config/settings.yaml(at least as much as it could and filled the rest with defaults) and now, there's really no reason to manually maintain config/settings.yamlany longer but rather I should just maintain these settings in the web app. Is that correct? >> >> >> Yep, you are correct, this is one of the features of the upcoming 0.4 release. >> >> >> seehttp://theforeman.org/projects/foreman/wiki/Foreman_configuration >> >> for more information. >> > ---- >> > ahh - new documentation since I checked - thanks. Are you going to put :require_ssl in the web app or will that remain the exclusive domain of config/settings.yaml? >> >> SSL, Login, unattended and puppet.conf path are the only 4 settings >> (for the moment) that needs to be in the setting.yaml file. >> >> Ohad >> >> >> >> >> >> >> >> >> >> > Craig >> >> > -- >> > You received this message because you are subscribed to the Google Groups "Foreman users" group. >> > To post to this group, send email to foreman-users@googlegroups.com. >> > To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. >> > For more options, visit this group athttp://groups.google.com/group/foreman-users?hl=en. > > Using the nightly from Sept 7th, I've noticed some settings aren't > being respected, either in settings.yaml or in the new Foreman > Settings. The first is "Puppet Run". While I'm in the process of > setting it up, I have it set to False in the web interface however the > button is still enabled. The other option I can't seem to disable is > the Unattended feature. Right now I'm still testing that ability in > my environment and have it set to false in settings.yaml, but the > button "Build" is enabled. > > This is my current settings.yaml, > > --- > :modulepath: /etc/puppet/modules/ > #:tftppath: tftp/ > #:rrd_report_url: report/ > :require_ssl: true > #:ldap: true > :login: false > #your default puppet server - can be overridden in the host level > #if none specified, plain "puppet" will be used. > :puppet_server: > :unattended: false > #use the following setting to override the default 30 minutes puppet > run interval - value must be in minutes > #:puppet_interval: 60 > #:document_root: /var/www > > Thanks > - Trey > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To post to this group, send email to foreman-users@googlegroups.com. > To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/foreman-users?hl=en. > >
8

New issue created, Bug #1167: Foreman settings ignored in web interface - Foreman

··· On Sep 10, 3:12 pm, Ohad Levy wrote: > On Fri, Sep 9, 2011 at 5:47 PM, treydock wrote: > > > On Aug 9, 12:52 pm, Ohad Levy wrote: > >> On Tue, Aug 9, 2011 at 6:29 PM, Craig White wrote: > > >> > On Aug 9, 2011, at 8:09 AM, Ohad Levy wrote: > > >> >> On Tue, Aug 9, 2011 at 6:03 PM, Craig White wrote: > >> >>> I am using the version I got from github which declares it to be 0.3 in FOREMAN_ROOT/VERSION > > >> >>> I noticed that in this version, there is a 'Foreman Settings' option in 'Settings Menu' of the web app that didn't appear in the 0.3 tarball so I definitely gather that the one I got from github is newer. > > >> >>> Anyway, I gather that this populated from FOREMAN_ROOT/config/settings.yaml(at least as much as it could and filled the rest with defaults) and now, there's really no reason to manually maintain config/settings.yamlany longer but rather I should just maintain these settings in the web app. Is that correct? > > >> >> Yep, you are correct, this is one of the features of the upcoming 0.4 release. > > >> >> seehttp://theforeman.org/projects/foreman/wiki/Foreman_configuration > >> >> for more information. > >> > ---- > >> > ahh - new documentation since I checked - thanks. Are you going to put :require_ssl in the web app or will that remain the exclusive domain of config/settings.yaml? > > >> SSL, Login, unattended and puppet.conf path are the only 4 settings > >> (for the moment) that needs to be in the setting.yaml file. > > >> Ohad > > >> > Craig > > >> > -- > >> > You received this message because you are subscribed to the Google Groups "Foreman users" group. > >> > To post to this group, send email to foreman-users@googlegroups.com. > >> > To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. > >> > For more options, visit this group athttp://groups.google.com/group/foreman-users?hl=en. > > > Using the nightly from Sept 7th, I've noticed some settings aren't > > being respected, either in settings.yaml or in the new Foreman > > Settings. The first is "Puppet Run". While I'm in the process of > > setting it up, I have it set to False in the web interface however the > > button is still enabled. The other option I can't seem to disable is > > the Unattended feature. Right now I'm still testing that ability in > > my environment and have it set to false in settings.yaml, but the > > button "Build" is enabled. > > > This is my current settings.yaml, > > > --- > > :modulepath: /etc/puppet/modules/ > > #:tftppath: tftp/ > > #:rrd_report_url: report/ > > :require_ssl: true > > #:ldap: true > > :login: false > > #your default puppet server - can be overridden in the host level > > #if none specified, plain "puppet" will be used. > > :puppet_server: > > :unattended: false > > #use the following setting to override the default 30 minutes puppet > > run interval - value must be in minutes > > #:puppet_interval: 60 > > #:document_root: /var/www > > > Thanks > > - Trey > > > -- > > You received this message because you are subscribed to the Google Groups "Foreman users" group. > > To post to this group, send email to foreman-users@googlegroups.com. > > To unsubscribe from this group, send email to foreman-users+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/foreman-users?hl=en. > > while I did a really quick test and was unable to reproduce, its > probably a bug, would you mind creating a new issue? > > thanks