I can manually alter files in
/etc/foreman-proxy/settings/{puppet|puppetCA} after foreman-installer to
reach the goal, but that will increase manual work for each Foreman
Upgrade; so what I did was:
foreman-installer -v
–enable-puppet
–foreman-proxy-puppetca=true
–foreman-proxy-puppetrun=false
–puppet-server=true --puppet-server-ca=true
…
Note: I tried many options, and find that only
'–foreman-proxy-puppetrun=false' will disable proxying puppet master,
although the option comments pointing to different things I am not certain,
In fact, I assume that some option like
'–foreman-proxy-puppetmaster=false', or ' --foreman-proxy-puppet=false',
but those doesn't exist.
(The above config option '–puppet-server=true' will let puppet master
running on a member node, though I would like Foreman proxy only proxy
puppet CA, while let puppet master alone. )
Any one can help confirm whether the above options combination is correct,
or there are better alternatives? Thanks.
You found the correct option, it's --foreman-proxy-puppetrun in 1.11 or
older. The parameter was renamed to --foreman-proxy-puppet in 1.12 as it
was misleading.
···
On 25/06/16 10:20, Thomas Cheng wrote:
>
> I can manually alter files in
> /etc/foreman-proxy/settings/{puppet|puppetCA} after foreman-installer to
> reach the goal, but that will increase manual work for each Foreman
> Upgrade; so what I did was:
>
> foreman-installer -v \
> --enable-puppet \
> --foreman-proxy-puppetca=true \
> --foreman-proxy-puppetrun=false \
> --puppet-server=true --puppet-server-ca=true \
> ...
>
> Note: I tried many options, and find that only
> '--foreman-proxy-puppetrun=false' will disable proxying puppet master,
> although the option comments pointing to different things I am not
> certain, In fact, I assume that some option like
> '--foreman-proxy-puppetmaster=false', or '
> --foreman-proxy-puppet=false', but those doesn't exist.
–
Dominic Cleal
dominic@cleal.org
>
> >
> > I can manually alter files in
> > /etc/foreman-proxy/settings/{puppet|puppetCA} after foreman-installer to
> > reach the goal, but that will increase manual work for each Foreman
> > Upgrade; so what I did was:
> >
> > foreman-installer -v \
> > --enable-puppet \
> > --foreman-proxy-puppetca=true \
> > --foreman-proxy-puppetrun=false \
> > --puppet-server=true --puppet-server-ca=true \
> > …
> >
> > Note: I tried many options, and find that only
> > '–foreman-proxy-puppetrun=false' will disable proxying puppet master,
> > although the option comments pointing to different things I am not
> > certain, In fact, I assume that some option like
> > '–foreman-proxy-puppetmaster=false', or '
> > --foreman-proxy-puppet=false', but those doesn't exist.
>
> You found the correct option, it's --foreman-proxy-puppetrun in 1.11 or
> older. The parameter was renamed to --foreman-proxy-puppet in 1.12 as it
> was misleading.
>
> Cool! Thanks for confirmation. now I'm feeling much relaxed. phew…
> –
> Dominic Cleal
> dom...@cleal.org <javascript:>
>
···
On Monday, June 27, 2016 at 12:38:19 AM UTC-7, Dominic Cleal wrote:
> On 25/06/16 10:20, Thomas Cheng wrote: