Re: [foreman-dev] setting up rex w/ katello dev forklift

2017-01-11 Thread Tom McKay
I see ssh now after a fresh forklift dev. I will post custom playbooks used
for feedback.

On Tue, Jan 10, 2017 at 3:45 PM, Tom McKay  wrote:

>
>
> yum install tfm-rubygem-foreman_remote_execution
> rubygem-smart_proxy_remote_execution_ssh
> added to katello-devel-answers.yaml
> still no rex options
>
>
> On Tue, Jan 10, 2017 at 3:03 PM, Stephen Benjamin 
> wrote:
>
>>
>>
>> - Original Message -
>> > From: "Tom McKay" 
>> > To: foreman-dev@googlegroups.com
>> > Sent: Tuesday, January 10, 2017 1:59:00 PM
>> > Subject: Re: [foreman-dev] setting up rex w/ katello dev forklift
>> >
>> > Yes, I have the rex gem as noted in original post. The missing steps are
>> > how to configure the smart proxy to have rex available.
>> >
>>
>> Can you try this:
>>
>>   echo 'foreman_proxy::plugin::remote_execution::ssh: false' >>
>> /etc/foreman-installer/scenarios.d/katello-devel-answers.yaml
>>
>>
>> And see if that's enough to get the options?
>>
>>
>> Once you do that you should be able to run:
>>
>>   foreman-installer --enable-foreman-proxy-plugin-remote-execution-ssh
>>
>>
>>
>>
>> > On Tue, Jan 10, 2017 at 1:42 PM, Stephen Benjamin 
>> > wrote:
>> >
>> > >
>> > >
>> > > - Original Message -
>> > > > From: "Ewoud Kohl van Wijngaarden" 
>> > > > To: foreman-dev@googlegroups.com
>> > > > Sent: Tuesday, January 10, 2017 12:14:18 PM
>> > > > Subject: Re: [foreman-dev] setting up rex w/ katello dev forklift
>> > > >
>> > > > On Tue, Jan 10, 2017 at 11:50:04AM -0500, Tom McKay wrote:
>> > > > > I'm trying to figure out the steps to get rex working with a dev
>> > > forklift.
>> > > > > Here's what I have so far...
>> > > > >
>> > > > > vagrant up devbox
>> > > > > sshfs mount in git checkout, which includes rex plugin
>> > > > > rake katello:reset
>> > > > > hammer csv smart-proxies to add back smart proxy on 9090
>> > > > > rake db:seed
>> > > > > rake db:migrate
>> > > > > yum install rubygem-smart_proxy_remote_execution_ssh
>> > > > > mkdir ~foreman-proxy/.ssh chown foreman-proxy ~foreman-proxy/.ssh
>> sudo
>> > > -u
>> > > > > foreman-proxy ssh-keygen -f ~foreman-proxy/.ssh/id_rsa_for
>> eman_proxy
>> > > -N ''
>> > > > > systemctl restart foreman-proxy.service
>> > > > >
>> > > > > I was hoping that the foreman-installer would have the necessary
>> flags
>> > > to
>> > > > > just make it work but I see no remote-execution flags at all in
>> > > > > foreman-installer --help
>> > > > >
>> > > > > Does anyone have a forklift playbook that wires all this up
>> correctly?
>> > > >
>> > > > Looks like the katello scenario does expose it:
>> > > >
>> > > > https://github.com/Katello/katello-installer/blob/
>> > > 9d08de2589d7a3c01f9965fa0aaf5f86be992b9b/config/katello-answ
>> ers.yaml#L68
>> > > >
>> > > > But katello-devel doesn't:
>> > > >
>> > > > https://github.com/Katello/katello-installer/blob/
>> > > 9d08de2589d7a3c01f9965fa0aaf5f86be992b9b/config/katello-deve
>> l-answers.yaml
>> > > >
>> > > > For for me worked was:
>> > > >
>> > > > echo '  foreman::plugin::remote_execution: false' >>
>> > > > /etc/foreman-installer/scenarios.d/katello-devel-answers.yaml
>> > > >
>> > > > Then the option should become visible, but maybe the options aren't
>> in
>> > > > the parser cache because I don't see those.
>> > > >
>> > >
>> > > I answered already on IRC, but this isn't going to work.  If you have
>> a dev
>> > > environment, it's the same process to install any Foreman plugin,
>> check out
>> > > the source and add it to your bundler.d.
>> > >
>> > >http://projects.theforeman.org/projects/foreman/wiki/How_
>> > > to_Create_a_Plugin#Installing-the-plugin
>> > >
>> > > The installer can automate some of this for the

Re: [foreman-dev] setting up rex w/ katello dev forklift

2017-01-10 Thread Tom McKay
yum install tfm-rubygem-foreman_remote_execution
rubygem-smart_proxy_remote_execution_ssh
added to katello-devel-answers.yaml
still no rex options


On Tue, Jan 10, 2017 at 3:03 PM, Stephen Benjamin 
wrote:

>
>
> - Original Message -
> > From: "Tom McKay" 
> > To: foreman-dev@googlegroups.com
> > Sent: Tuesday, January 10, 2017 1:59:00 PM
> > Subject: Re: [foreman-dev] setting up rex w/ katello dev forklift
> >
> > Yes, I have the rex gem as noted in original post. The missing steps are
> > how to configure the smart proxy to have rex available.
> >
>
> Can you try this:
>
>   echo 'foreman_proxy::plugin::remote_execution::ssh: false' >>
> /etc/foreman-installer/scenarios.d/katello-devel-answers.yaml
>
>
> And see if that's enough to get the options?
>
>
> Once you do that you should be able to run:
>
>   foreman-installer --enable-foreman-proxy-plugin-remote-execution-ssh
>
>
>
>
> > On Tue, Jan 10, 2017 at 1:42 PM, Stephen Benjamin 
> > wrote:
> >
> > >
> > >
> > > - Original Message -----
> > > > From: "Ewoud Kohl van Wijngaarden" 
> > > > To: foreman-dev@googlegroups.com
> > > > Sent: Tuesday, January 10, 2017 12:14:18 PM
> > > > Subject: Re: [foreman-dev] setting up rex w/ katello dev forklift
> > > >
> > > > On Tue, Jan 10, 2017 at 11:50:04AM -0500, Tom McKay wrote:
> > > > > I'm trying to figure out the steps to get rex working with a dev
> > > forklift.
> > > > > Here's what I have so far...
> > > > >
> > > > > vagrant up devbox
> > > > > sshfs mount in git checkout, which includes rex plugin
> > > > > rake katello:reset
> > > > > hammer csv smart-proxies to add back smart proxy on 9090
> > > > > rake db:seed
> > > > > rake db:migrate
> > > > > yum install rubygem-smart_proxy_remote_execution_ssh
> > > > > mkdir ~foreman-proxy/.ssh chown foreman-proxy ~foreman-proxy/.ssh
> sudo
> > > -u
> > > > > foreman-proxy ssh-keygen -f ~foreman-proxy/.ssh/id_rsa_
> foreman_proxy
> > > -N ''
> > > > > systemctl restart foreman-proxy.service
> > > > >
> > > > > I was hoping that the foreman-installer would have the necessary
> flags
> > > to
> > > > > just make it work but I see no remote-execution flags at all in
> > > > > foreman-installer --help
> > > > >
> > > > > Does anyone have a forklift playbook that wires all this up
> correctly?
> > > >
> > > > Looks like the katello scenario does expose it:
> > > >
> > > > https://github.com/Katello/katello-installer/blob/
> > > 9d08de2589d7a3c01f9965fa0aaf5f86be992b9b/config/katello-
> answers.yaml#L68
> > > >
> > > > But katello-devel doesn't:
> > > >
> > > > https://github.com/Katello/katello-installer/blob/
> > > 9d08de2589d7a3c01f9965fa0aaf5f86be992b9b/config/katello-
> devel-answers.yaml
> > > >
> > > > For for me worked was:
> > > >
> > > > echo '  foreman::plugin::remote_execution: false' >>
> > > > /etc/foreman-installer/scenarios.d/katello-devel-answers.yaml
> > > >
> > > > Then the option should become visible, but maybe the options aren't
> in
> > > > the parser cache because I don't see those.
> > > >
> > >
> > > I answered already on IRC, but this isn't going to work.  If you have
> a dev
> > > environment, it's the same process to install any Foreman plugin,
> check out
> > > the source and add it to your bundler.d.
> > >
> > >http://projects.theforeman.org/projects/foreman/wiki/How_
> > > to_Create_a_Plugin#Installing-the-plugin
> > >
> > > The installer can automate some of this for the dev environment but
> > > I haven't tried this feature.  Look for "extra-plugins" in the help:
> > >
> > >   https://github.com/Katello/puppet-katello_devel/blob/
> > > master/manifests/init.pp#L65
> > >
> > >
> > >
> > >
> > >
> > >
> > > - Stephen
> > >
> > > --
> > > 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.
> >
>
> --
> 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.


Re: [foreman-dev] setting up rex w/ katello dev forklift

2017-01-10 Thread Stephen Benjamin


- Original Message -
> From: "Tom McKay" 
> To: foreman-dev@googlegroups.com
> Sent: Tuesday, January 10, 2017 1:59:00 PM
> Subject: Re: [foreman-dev] setting up rex w/ katello dev forklift
> 
> Yes, I have the rex gem as noted in original post. The missing steps are
> how to configure the smart proxy to have rex available.
>

Can you try this:

  echo 'foreman_proxy::plugin::remote_execution::ssh: false' >> 
/etc/foreman-installer/scenarios.d/katello-devel-answers.yaml


And see if that's enough to get the options?


Once you do that you should be able to run:

  foreman-installer --enable-foreman-proxy-plugin-remote-execution-ssh




> On Tue, Jan 10, 2017 at 1:42 PM, Stephen Benjamin 
> wrote:
> 
> >
> >
> > - Original Message -
> > > From: "Ewoud Kohl van Wijngaarden" 
> > > To: foreman-dev@googlegroups.com
> > > Sent: Tuesday, January 10, 2017 12:14:18 PM
> > > Subject: Re: [foreman-dev] setting up rex w/ katello dev forklift
> > >
> > > On Tue, Jan 10, 2017 at 11:50:04AM -0500, Tom McKay wrote:
> > > > I'm trying to figure out the steps to get rex working with a dev
> > forklift.
> > > > Here's what I have so far...
> > > >
> > > > vagrant up devbox
> > > > sshfs mount in git checkout, which includes rex plugin
> > > > rake katello:reset
> > > > hammer csv smart-proxies to add back smart proxy on 9090
> > > > rake db:seed
> > > > rake db:migrate
> > > > yum install rubygem-smart_proxy_remote_execution_ssh
> > > > mkdir ~foreman-proxy/.ssh chown foreman-proxy ~foreman-proxy/.ssh sudo
> > -u
> > > > foreman-proxy ssh-keygen -f ~foreman-proxy/.ssh/id_rsa_foreman_proxy
> > -N ''
> > > > systemctl restart foreman-proxy.service
> > > >
> > > > I was hoping that the foreman-installer would have the necessary flags
> > to
> > > > just make it work but I see no remote-execution flags at all in
> > > > foreman-installer --help
> > > >
> > > > Does anyone have a forklift playbook that wires all this up correctly?
> > >
> > > Looks like the katello scenario does expose it:
> > >
> > > https://github.com/Katello/katello-installer/blob/
> > 9d08de2589d7a3c01f9965fa0aaf5f86be992b9b/config/katello-answers.yaml#L68
> > >
> > > But katello-devel doesn't:
> > >
> > > https://github.com/Katello/katello-installer/blob/
> > 9d08de2589d7a3c01f9965fa0aaf5f86be992b9b/config/katello-devel-answers.yaml
> > >
> > > For for me worked was:
> > >
> > > echo '  foreman::plugin::remote_execution: false' >>
> > > /etc/foreman-installer/scenarios.d/katello-devel-answers.yaml
> > >
> > > Then the option should become visible, but maybe the options aren't in
> > > the parser cache because I don't see those.
> > >
> >
> > I answered already on IRC, but this isn't going to work.  If you have a dev
> > environment, it's the same process to install any Foreman plugin, check out
> > the source and add it to your bundler.d.
> >
> >http://projects.theforeman.org/projects/foreman/wiki/How_
> > to_Create_a_Plugin#Installing-the-plugin
> >
> > The installer can automate some of this for the dev environment but
> > I haven't tried this feature.  Look for "extra-plugins" in the help:
> >
> >   https://github.com/Katello/puppet-katello_devel/blob/
> > master/manifests/init.pp#L65
> >
> >
> >
> >
> >
> >
> > - Stephen
> >
> > --
> > 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.
> 

-- 
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.


Re: [foreman-dev] setting up rex w/ katello dev forklift

2017-01-10 Thread Tom McKay
Yes, I have the rex gem as noted in original post. The missing steps are
how to configure the smart proxy to have rex available.

On Tue, Jan 10, 2017 at 1:42 PM, Stephen Benjamin 
wrote:

>
>
> - Original Message -
> > From: "Ewoud Kohl van Wijngaarden" 
> > To: foreman-dev@googlegroups.com
> > Sent: Tuesday, January 10, 2017 12:14:18 PM
> > Subject: Re: [foreman-dev] setting up rex w/ katello dev forklift
> >
> > On Tue, Jan 10, 2017 at 11:50:04AM -0500, Tom McKay wrote:
> > > I'm trying to figure out the steps to get rex working with a dev
> forklift.
> > > Here's what I have so far...
> > >
> > > vagrant up devbox
> > > sshfs mount in git checkout, which includes rex plugin
> > > rake katello:reset
> > > hammer csv smart-proxies to add back smart proxy on 9090
> > > rake db:seed
> > > rake db:migrate
> > > yum install rubygem-smart_proxy_remote_execution_ssh
> > > mkdir ~foreman-proxy/.ssh chown foreman-proxy ~foreman-proxy/.ssh sudo
> -u
> > > foreman-proxy ssh-keygen -f ~foreman-proxy/.ssh/id_rsa_foreman_proxy
> -N ''
> > > systemctl restart foreman-proxy.service
> > >
> > > I was hoping that the foreman-installer would have the necessary flags
> to
> > > just make it work but I see no remote-execution flags at all in
> > > foreman-installer --help
> > >
> > > Does anyone have a forklift playbook that wires all this up correctly?
> >
> > Looks like the katello scenario does expose it:
> >
> > https://github.com/Katello/katello-installer/blob/
> 9d08de2589d7a3c01f9965fa0aaf5f86be992b9b/config/katello-answers.yaml#L68
> >
> > But katello-devel doesn't:
> >
> > https://github.com/Katello/katello-installer/blob/
> 9d08de2589d7a3c01f9965fa0aaf5f86be992b9b/config/katello-devel-answers.yaml
> >
> > For for me worked was:
> >
> > echo '  foreman::plugin::remote_execution: false' >>
> > /etc/foreman-installer/scenarios.d/katello-devel-answers.yaml
> >
> > Then the option should become visible, but maybe the options aren't in
> > the parser cache because I don't see those.
> >
>
> I answered already on IRC, but this isn't going to work.  If you have a dev
> environment, it's the same process to install any Foreman plugin, check out
> the source and add it to your bundler.d.
>
>http://projects.theforeman.org/projects/foreman/wiki/How_
> to_Create_a_Plugin#Installing-the-plugin
>
> The installer can automate some of this for the dev environment but
> I haven't tried this feature.  Look for "extra-plugins" in the help:
>
>   https://github.com/Katello/puppet-katello_devel/blob/
> master/manifests/init.pp#L65
>
>
>
>
>
>
> - Stephen
>
> --
> 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.


Re: [foreman-dev] setting up rex w/ katello dev forklift

2017-01-10 Thread Stephen Benjamin


- Original Message -
> From: "Ewoud Kohl van Wijngaarden" 
> To: foreman-dev@googlegroups.com
> Sent: Tuesday, January 10, 2017 12:14:18 PM
> Subject: Re: [foreman-dev] setting up rex w/ katello dev forklift
> 
> On Tue, Jan 10, 2017 at 11:50:04AM -0500, Tom McKay wrote:
> > I'm trying to figure out the steps to get rex working with a dev forklift.
> > Here's what I have so far...
> > 
> > vagrant up devbox
> > sshfs mount in git checkout, which includes rex plugin
> > rake katello:reset
> > hammer csv smart-proxies to add back smart proxy on 9090
> > rake db:seed
> > rake db:migrate
> > yum install rubygem-smart_proxy_remote_execution_ssh
> > mkdir ~foreman-proxy/.ssh chown foreman-proxy ~foreman-proxy/.ssh sudo -u
> > foreman-proxy ssh-keygen -f ~foreman-proxy/.ssh/id_rsa_foreman_proxy -N ''
> > systemctl restart foreman-proxy.service
> > 
> > I was hoping that the foreman-installer would have the necessary flags to
> > just make it work but I see no remote-execution flags at all in
> > foreman-installer --help
> > 
> > Does anyone have a forklift playbook that wires all this up correctly?
> 
> Looks like the katello scenario does expose it:
> 
> https://github.com/Katello/katello-installer/blob/9d08de2589d7a3c01f9965fa0aaf5f86be992b9b/config/katello-answers.yaml#L68
> 
> But katello-devel doesn't:
> 
> https://github.com/Katello/katello-installer/blob/9d08de2589d7a3c01f9965fa0aaf5f86be992b9b/config/katello-devel-answers.yaml
> 
> For for me worked was:
> 
> echo '  foreman::plugin::remote_execution: false' >>
> /etc/foreman-installer/scenarios.d/katello-devel-answers.yaml
> 
> Then the option should become visible, but maybe the options aren't in
> the parser cache because I don't see those.
> 

I answered already on IRC, but this isn't going to work.  If you have a dev
environment, it's the same process to install any Foreman plugin, check out
the source and add it to your bundler.d.

   
http://projects.theforeman.org/projects/foreman/wiki/How_to_Create_a_Plugin#Installing-the-plugin

The installer can automate some of this for the dev environment but
I haven't tried this feature.  Look for "extra-plugins" in the help:

  
https://github.com/Katello/puppet-katello_devel/blob/master/manifests/init.pp#L65






- Stephen

-- 
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.


Re: [foreman-dev] setting up rex w/ katello dev forklift

2017-01-10 Thread Ewoud Kohl van Wijngaarden
On Tue, Jan 10, 2017 at 11:50:04AM -0500, Tom McKay wrote:
> I'm trying to figure out the steps to get rex working with a dev forklift.
> Here's what I have so far...
> 
> vagrant up devbox
> sshfs mount in git checkout, which includes rex plugin
> rake katello:reset
> hammer csv smart-proxies to add back smart proxy on 9090
> rake db:seed
> rake db:migrate
> yum install rubygem-smart_proxy_remote_execution_ssh
> mkdir ~foreman-proxy/.ssh chown foreman-proxy ~foreman-proxy/.ssh sudo -u
> foreman-proxy ssh-keygen -f ~foreman-proxy/.ssh/id_rsa_foreman_proxy -N ''
> systemctl restart foreman-proxy.service
> 
> I was hoping that the foreman-installer would have the necessary flags to
> just make it work but I see no remote-execution flags at all in
> foreman-installer --help
> 
> Does anyone have a forklift playbook that wires all this up correctly?

Looks like the katello scenario does expose it:

https://github.com/Katello/katello-installer/blob/9d08de2589d7a3c01f9965fa0aaf5f86be992b9b/config/katello-answers.yaml#L68

But katello-devel doesn't:

https://github.com/Katello/katello-installer/blob/9d08de2589d7a3c01f9965fa0aaf5f86be992b9b/config/katello-devel-answers.yaml

For for me worked was:

echo '  foreman::plugin::remote_execution: false' >> 
/etc/foreman-installer/scenarios.d/katello-devel-answers.yaml

Then the option should become visible, but maybe the options aren't in
the parser cache because I don't see those.

-- 
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.


[foreman-dev] setting up rex w/ katello dev forklift

2017-01-10 Thread Tom McKay
I'm trying to figure out the steps to get rex working with a dev forklift.
Here's what I have so far...

vagrant up devbox
sshfs mount in git checkout, which includes rex plugin
rake katello:reset
hammer csv smart-proxies to add back smart proxy on 9090
rake db:seed
rake db:migrate
yum install rubygem-smart_proxy_remote_execution_ssh
mkdir ~foreman-proxy/.ssh chown foreman-proxy ~foreman-proxy/.ssh sudo -u
foreman-proxy ssh-keygen -f ~foreman-proxy/.ssh/id_rsa_foreman_proxy -N ''
systemctl restart foreman-proxy.service

I was hoping that the foreman-installer would have the necessary flags to
just make it work but I see no remote-execution flags at all in
foreman-installer --help

Does anyone have a forklift playbook that wires all this up correctly?

-- 
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.