[foreman-dev] Re: Nominating Timo Goebel for theforeman/foreman commit access
+1 On Thursday, June 2, 2016 at 7:47:09 AM UTC-7, Daniel Lobato wrote: > > Hi devs, > > I'd like to nominate Timo Goebel (timogoebel on Github & IRC) for commit > access to theforeman/foreman repo. > > He's been contributing to the puppet modules, community-templates, > bootdisk > and Foreman for some time, particularly on the VMWare/vsphere side of > things. > He's been running Foreman on production for years already and gave > local talks about it.( > www.meetup.com/AWS-Meetup-Karlsruhe/events/229036956/) > > Most importantly and the reason why I thought of him as a person that > could become a committer is his involvement on ipv6 support lately, > where he's been submitting consistently good code. > > I think he understands very well the problem domain, and he will be > committed to maintain and improve the code quality of the project, as > well as providing good feedback from a production installations. > > Some examples of his contributions: > > https://github.com/theforeman/foreman/pull/3420 > https://github.com/theforeman/foreman/pull/3424 > https://github.com/theforeman/foreman/pull/3498 > https://github.com/theforeman/foreman/pull/3499 > > https://github.com/theforeman/foreman/commit/5131edbfab258c0862c987f238049ee81a1cd13f > > > https://github.com/theforeman/foreman/commit/8ca6c6bbc5242c29a8039d1e6a1d09d1a454164c > > > https://github.com/theforeman/foreman/commit/2328beb569d3f0e51043202d3a00a3b30879d244 > > https://github.com/theforeman/puppet-puppet/pull/389 > https://github.com/theforeman/foreman_bootdisk/pull/19 > > Lastly I'd encourage him to start reviewing already! > > Objections or comments in private are welcome, but public replies to this > thread are preferred :) > > Best, > > -- > Daniel Lobato Garcia > > @dLobatog > blog.daniellobato.me > daniellobato.me > > GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 > Keybase: https://keybase.io/elobato > -- 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] Re: Nominating Timo Goebel for theforeman/foreman commit access
Reminder - 2 days left if you have any objections or comments! On 06/02, Daniel Lobato Garcia wrote: > Hi devs, > > I'd like to nominate Timo Goebel (timogoebel on Github & IRC) for commit > access to theforeman/foreman repo. > > He's been contributing to the puppet modules, community-templates, bootdisk > and Foreman for some time, particularly on the VMWare/vsphere side of things. > He's been running Foreman on production for years already and gave > local talks about it.(www.meetup.com/AWS-Meetup-Karlsruhe/events/229036956/) > > Most importantly and the reason why I thought of him as a person that > could become a committer is his involvement on ipv6 support lately, > where he's been submitting consistently good code. > > I think he understands very well the problem domain, and he will be > committed to maintain and improve the code quality of the project, as > well as providing good feedback from a production installations. > > Some examples of his contributions: > > https://github.com/theforeman/foreman/pull/3420 > https://github.com/theforeman/foreman/pull/3424 > https://github.com/theforeman/foreman/pull/3498 > https://github.com/theforeman/foreman/pull/3499 > https://github.com/theforeman/foreman/commit/5131edbfab258c0862c987f238049ee81a1cd13f > https://github.com/theforeman/foreman/commit/8ca6c6bbc5242c29a8039d1e6a1d09d1a454164c > https://github.com/theforeman/foreman/commit/2328beb569d3f0e51043202d3a00a3b30879d244 > https://github.com/theforeman/puppet-puppet/pull/389 > https://github.com/theforeman/foreman_bootdisk/pull/19 > > Lastly I'd encourage him to start reviewing already! > > Objections or comments in private are welcome, but public replies to this > thread are preferred :) > > Best, > > -- > Daniel Lobato Garcia > > @dLobatog > blog.daniellobato.me > daniellobato.me > > GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 > Keybase: https://keybase.io/elobato -- Daniel Lobato Garcia @dLobatog blog.daniellobato.me daniellobato.me GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 Keybase: https://keybase.io/elobato -- 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. signature.asc Description: PGP signature
Re: [foreman-dev] smart-proxy rake test fails for me
On 06/07, paul kelly wrote: > Hi Folks, Hi! > I am attempting to run the smart-proxy tests and am getting some errors. > I suspect a mismatched gem somewhere. Could someone confirm that this > selection of gems is correct for running under ruby-2.0.0-p353? > Alternatively could I get a copy of this information from the Jenkins CI > environment? You can see what gems are installed here: http://ci.theforeman.org/job/test_proxy_develop_pr_core/804/puppet=4.3.0,ruby=2.0.0/consoleFull Anyway, what errors are you seeing when you run tests? Have you tried 'bundle exec rake test' (that uses gems in the smart-proxy bundle)? -- Daniel Lobato Garcia @dLobatog blog.daniellobato.me daniellobato.me GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 Keybase: https://keybase.io/elobato -- 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. signature.asc Description: PGP signature
Re: [foreman-dev] smart-proxy rake test fails for me
Nice!! -- 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] smart-proxy rake test fails for me
On 07/06/16 14:11, paul kelly wrote: > Hi Folks, > I am attempting to run the smart-proxy tests and am getting some > errors. I suspect a mismatched gem somewhere. Could someone confirm that > this selection of gems is correct for running under ruby-2.0.0-p353? > Alternatively could I get a copy of this information from the Jenkins CI > environment? http://ci.theforeman.org/job/test_proxy_develop/ is the test job, linked from the README if you need it in future. http://ci.theforeman.org/job/test_proxy_develop/puppet=3.8.0,ruby=2.0.0/lastSuccessfulBuild/console is the last run for Ruby 2.0.0, scroll most of the way down past the RVM setup to find the gem list. -- Dominic Cleal domi...@cleal.org -- 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] smart-proxy rake test fails for me
Hi Folks, I am attempting to run the smart-proxy tests and am getting some errors. I suspect a mismatched gem somewhere. Could someone confirm that this selection of gems is correct for running under ruby-2.0.0-p353? Alternatively could I get a copy of this information from the Jenkins CI environment? pkelly@vihla676(theforeman-develop): bundle list Gems included by the bundle: * addressable (2.3.8) * ast (2.2.0) * builder (3.2.2) * bundler (1.9.6) * ci_reporter (1.9.3) * coderay (1.1.1) * crack (0.4.3) * facter (2.4.6) * ffi (1.9.10) * gssapi (1.2.0) * hashdiff (0.3.0) * hiera (1.3.4) * json (1.8.3) * json_pure (1.8.3) * metaclass (0.0.4) * method_source (0.8.2) * mocha (0.13.3) * parser (2.3.1.2) * powerpack (0.1.1) * pry (0.10.3) * puppet (3.7.5) * rack (1.5.5) * rack-protection (1.5.3) * rack-test (0.6.3) * rainbow (2.1.0) * rake (10.4.2) * rake-compiler (0.9.9) * rdoc (4.2.0) * rkerberos (0.1.3) * rubocop (0.38.0) * rubocop-checkstyle_formatter (0.2.0) * ruby-augeas (0.5.0) * ruby-libvirt (0.6.0) * ruby-progressbar (1.8.1) * rubyipmi (0.10.0) * safe_yaml (1.0.4) * sinatra (1.4.7) * single_test (0.6.0) * slop (3.6.0) * smart_proxy (1.13.0.develop) * test-unit (2.0.0.0) * tilt (1.4.1) * unicode-display_width (1.0.5) * webmock (2.1.0) Thanks In Advance , Paul -- 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] Re: Foreman Community Demo Items - Thu 09 Jun
On 7 June 2016 at 13:29, Lukas Zapletal wrote: > > 2 days to go, still no presenters - I see 153 closed bugs and 23 closed > > features in the last 3 weeks, surely someone has something to say? :) > > I can hardly say what I was eating for lunch yesterday. Can't you just > drop the search query link to the list every month please? :-) > You mean the [2] link in the original post? :) -- 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] Drop support for Ruby 1.9.2 in smart proxy
Hi, On Tue, Jun 07, 2016 at 01:20:10PM +0100, Dominic Cleal wrote: > I'd like to drop support for testing Ruby 1.9.2 in the smart proxy, Please do. :) > We used to have some platforms (such as Debian Squeeze, IIRC) that > shipped 1.9.2 but we no longer support them. AFAICT, even on Debian/squeeze, Ruby 1.8 was the default. So in the vast majority of these setups, 1.9.2 was never used. -- Michael Moll -- 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] Re: Foreman Community Demo Items - Thu 09 Jun
> 2 days to go, still no presenters - I see 153 closed bugs and 23 closed > features in the last 3 weeks, surely someone has something to say? :) I can hardly say what I was eating for lunch yesterday. Can't you just drop the search query link to the list every month please? :-) -- Later, Lukas #lzap Zapletal -- 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] how to determine power on/off of discovered host from API?
Hey, > PUT api/v2/discovered_hosts/:id/refresh_facts yeah this or GET /features works as well. > Any other "ping status" API call? Nope, all other ports except 8443 and 8448 (http) are firewalled. Proper shutdown should delete discovered host (file RFE for this please), good idea. But hard power off we can't detect easily of course. -- Later, Lukas #lzap Zapletal -- 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] Drop support for Ruby 1.9.2 in smart proxy
I'd like to drop support for testing Ruby 1.9.2 in the smart proxy, primarily because we're getting intermittent segfaults on it during tests. We used to have some platforms (such as Debian Squeeze, IIRC) that shipped 1.9.2 but we no longer support them. Puppet also didn't support it officially as 1.9.3 contained lots of fixes. 1.8.7 support would remain, so we'd have 1.8.7, 1.9.3, 2.0.0 and up. Any objections? -- Dominic Cleal domi...@cleal.org -- 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] Re: [foreman-users] Strawpoll - Switching the community demo to a monthly timeframe
Cycling around to this now that it's had a while to run - it seems 88% (ok, sample size of just 17 replies :P) are in favour of monthly. There are a few other considerations, so I'll get thinking about that and make a decision in the near future. On 23 May 2016 at 11:43, Daniel Lobato Garcia wrote: > That's kind of a big problem for me - frequent reminders on IRC > to put things in the current sprint info page > > http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information > page would help :) If that's helpful, then I'll see what I can do. Perhaps nudnik should respond to GitHub notifications :P -- 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] Re: Foreman Community Demo Items - Thu 09 Jun
2 days to go, still no presenters - I see 153 closed bugs and 23 closed features in the last 3 weeks, surely someone has something to say? :) -- 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] how to determine power on/off of discovered host from API?
What if a discovered host is powered off after it was discovered and registered in Foreman. One way seems to be to: PUT api/v2/discovered_hosts/:id/refresh_facts and if a 500 error is returned, then we know it's powered off. Any other "ping status" API call? Thanks, Joseph -- 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.
