> I could use some help trying to get foreman-proxy working.
> I've got a puppet-3.0.1-1 running on a CentOS 6.3 server. I used Mark
> Stanislavï¿½s excellent post to get puppet running
> # rpm -qa | grep puppet
> I'm using passengerï¿½
> # rpm -qa | grep passenger
> Iï¿½ve installed foreman from rpm as well
> # rpm -qa | grep foreman
> Here are my gems:
> My problem is foreman-proxy doesnï¿½t seem to actually do anything. It
> wonï¿½t even write to the log file specified in settings.yml. If I put a
> typo in settings.yml, foreman-proxy complained when I restarted, so I
> know the file is being read. I put a large number of warning statements
> in my code to figure out what was going on.
> Now when I run foreman-proxy, at least it creates the log file specified
> in settings.yml. It still wonï¿½t do anything else meaningful ï¿½ Iï¿½m
> trying to get DHCP working first.
It doesn't do anything by itself - it'll just listen on port 8443 until
instructed to do something. How are you trying to use it?
Typically you'd start up the proxy, then go into the Foreman UI, More,
Smart Proxies and then add it by URL. You should then see a number of
features listed, such as Puppet, PuppetCA, DHCP, depending on what's
configured in the proxy's settings.yml.
You can also query it directly yourself, e.g.
curl -H "Accept: application/json" http://localhost:8443/features
Once you've added the proxy to Foreman's UI, you can select it in your
configuration to handle certain tasks. e.g. under Domains, you could
select the proxy for DNS if it provides the DNS feature and manages that
domain. For DHCP, you'd be able to select it under the Subnet if it
supported the DHCP feature.
> I donï¿½t know ruby so I have no idea whatï¿½s going on.
> Related dumb question - does foreman-proxy need to be run as passenger?
> If so, how do I do this? I see a config.ru, but I donï¿½t see any
> example configurations for /etc/httpd/conf.d
That's not necessary, but some people might decide to deploy it that way
if they're comfortable with Rack applications. Most users should deploy
it as a standalone service using the package, which runs a WEBrick
daemon with no httpd or passenger required.
We use passenger for the Foreman UI itself, as it scales better,
Apache's mod_ssl works better etc.
> Iï¿½ve tried running the foreman installer on this server, it didnï¿½t seem
> to do anything.
> The server is a VM with a snapshot so I can easily back out changes like
> Iï¿½ve tried various versions of foreman and the proxy, nothing has helped.
The installer should just set up the package and configuration
(settings.yml) if you apply the foreman_proxy class, then you're able to
use the proxy from Foreman.
···On 08/02/13 00:26, John Smith wrote:
Red Hat Engineering