----- Original Message -----
> From: "lakier" <stanislaw.jak...@gmail.com>
> To: "foreman-dev" <foreman-dev@googlegroups.com>
> Cc: step...@redhat.com
> Sent: Monday, September 19, 2016 4:11:15 PM
> Subject: Re: [foreman-dev] smart-proxy plugin installation failure
> 
> As I mentioned in first post, I've refreshed this...

It wasn't clear to me that you did that after starting the smart proxy
after step 6 in your summary.

Does it show up in the output of the features API call 
(https://localhost:8443/features)?

Did you run db:seed as well on the foreman? This is what creates the 
Salt feature in the database.




> On Monday, September 19, 2016 at 7:54:25 PM UTC+2, stephen wrote:
> >
> > You would need to refresh the features from the Infrastructure/Proxies
> > page on the Foreman server.
> >
> >
> > ----- Original Message -----
> > > From: "lakier" <stanisla...@gmail.com <javascript:>>
> > > To: "foreman-dev" <forem...@googlegroups.com <javascript:>>
> > > Cc: dom...@cleal.org <javascript:>
> > > Sent: Monday, September 19, 2016 1:19:13 PM
> > > Subject: Re: [foreman-dev] smart-proxy plugin installation failure
> > > 
> > > Thank you for your reply.
> > > I've followed these steps once again, still no change...
> > > 
> > > I see in smart-proxy (debug) log:
> > > Successfully initialized 'salt'
> > > But on the foreman gui still no 'salt' feature after smart-proxy
> > refresh.
> > > Moreover proxy.log doesn't contain any other useful information...
> > > I'm using 'foreman_salt' foreman plugin via source install:
> > > /usr/share/foreman/bundler.d/Gemfile.local.rb (using 6.0.0 branch, my
> > > foreman is 1.12), which seems to install just fine.
> > > 
> > > To sum up steps:
> > > 1. sudo foreman-installer \
> > >    --no-enable-foreman-proxy \
> > >    --no-enable-puppet \
> > >    --puppet-server=false \
> > >    --foreman-user-groups=EMPTY_ARRAY \
> > >    --foreman-server-ssl-ca=$CA_CERT \
> > >    --foreman-server-ssl-chain=$CA_CERT \
> > >    --foreman-server-ssl-cert=$FOREMAN_CERT \
> > >    --foreman-server-ssl-key=$FOREMAN_KEY \
> > >    --foreman-server-ssl-crl=$FOREMAN_CRL \
> > >    --foreman-client-ssl-ca=$CA_CERT \
> > >    --foreman-client-ssl-cert=$FOREMAN_CERT \
> > >    --foreman-client-ssl-key=$FOREMAN_KEY \
> > >    --foreman-websockets-ssl-cert=$FOREMAN_CERT \
> > >    --foreman-websockets-ssl-key=$FOREMAN_KEY \
> > >    --puppet-ssldir=$CERT_BASEDIR \
> > >    --foreman-puppet-ssldir=$CERT_BASEDIR
> > > 
> > > (it seems to install smart-proxy - I can see it in *ps aux, *I'm killing
> > > this process)
> > > 
> > > 2. installing foreman_salt using aforementioned method, running
> > db:migrate.
>
> > > 3. Cloning my fork of smart-proxy-salt and smart-proxy
> > > 4. gem build *.gemspec; sudo gem install *.gem
> > > 5. changing settings in smart-proxy/settings.d (generic and salt ones,
> > > :enabled is set to https), running *bundle install* (I see
> > smart_proxy_salt)
> > > 6. run smart-proxy/bin/smart-proxy
> > > 
> > > Outcome:
> > > smart-proxy doesn't show salt feature, absolutely nothing in logs...
> > > 
> > > On Monday, September 19, 2016 at 8:55:54 AM UTC+2, Dominic Cleal wrote:
> > > > 
> > > > On 18/09/16 22:03, lakier wrote:
> > > > > Hi,
> > > > > 
> > > > > I was willing to install my version of salt-smart-proxy plugin.
> > > > > And basically the question is:
> > > > > *How to do this? ELI5*
> > > > > *
> > > > > *
> > > > > I've
> > > > > read
> > > > 
> > http://projects.theforeman.org/projects/foreman/wiki/How_to_Install_a_Smart-Proxy_Plugin
> > > > > so spare me that (I suggest making it clear that package
> > installation is
> > > > > fundamentally different that source install).
> > > > > After some time I've discovered that gem installing my
> > smart_proxy_salt
> > > > > doesn't do anything.
> > > > 
> > > > The gem has to be installed, but you also need a bundler.d/ entry to
> > > > load it (e.g.
> > > > 
> > > > 
> > https://github.com/theforeman/smart_proxy_salt/blob/master/bundler.d/salt.rb)
> >
> > > > 
> > > > and a configuration file in settings.d/ to activate it.
> > > > 
> > > > > Cloning smart-proxy repo, adding gem 'smart_proxy_salt' to
> > > > > Gemfile.local.rb, adding settings files to /config/ dir and doing
> > > > > /bundle install /doesn't setup salt at all (refreshing smart-proxy
> > in
> > > > > foreman gui doesn't show salt /feature/)
> > > > 
> > > > "bundle install" doesn't list smart_proxy_salt? If so, check that the
> > > > entry in your Gemfile.local.rb is correct and that it's at
> > > > bundler.d/Gemfile.local.rb.
> > > > 
> > > > Check the smart proxy log file, particularly on debug mode rather than
> > > > using the list of enabled features in Foreman. The logs will show if
> > any
> > > > modules are failing to load, or being loaded but are disabled, plus
> > > > using Foreman requires you to have an equivalent Foreman plugin
> > > > installed that can recognise the smart proxy feature.
> > > > 
> > > > > Where for the God's sake you actually PLUG your plugin to
> > smart-proxy ?
> > > > > Where is it configured?
> > > > 
> > > > Adding the plugin gem to the Gemfile loads the code and registers the
> > > > plugin at startup.
> > > > 
> > > > > Who calls lib/proxy/plugin_initializer.rb resolve_providers method?
> > > > 
> > > > This is an internal smart proxy function, called at startup.
> > > > 
> > > > > Is it possible to write plugins in different than ruby language?
> > > > 
> > > > No.
> > > > 
> > > > > Is it possible to call other languages from within ruby ?
> > > > 
> > > > Probably - like most languages, Ruby has many methods to run other
> > > > executables and could call other APIs.
> > > > 
> > > > --
> > > > Dominic Cleal
> > > > dom...@cleal.org <javascript:>
> > > > 
> > > 
> > > --
> > > You received this message because you are subscribed to the Google
> > Groups
> > > "foreman-dev" group.
> > > To unsubscribe from this group and stop receiving emails from it, send
> > an
> > > email to foreman-dev...@googlegroups.com <javascript:>.
> > > For more options, visit https://groups.google.com/d/optout.
> > > 
> >
> 
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to