Jira (PUP-4444) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Jeremy Barlow commented on PUP- Re: Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter Peter Huene and Kylo Ginsberg, elaborating on the discussion we had about the HttpClient “hook” approach that I’d mentioned we followed in Puppet Server in order to register an alternative http_client with core Ruby Puppet when running under Puppet Server. I think this is what Christopher Price had been alluding to in a prior comment in this thread: The “hook” was added to the Puppet::Network::HttpPool module in core Ruby Puppet. See: https://github.com/puppetlabs/puppet/blob/4.0.0/lib/puppet/network/http_pool.rb#L14-L21 When running under MRI Ruby by default, an Puppet::Network::HTTP::Connection instance would be used for HTTP client calls. Puppet Server, during its initialization, would register an alternative http_client: https://github.com/puppetlabs/puppet-server/blob/master/src/ruby/puppet-server-lib/puppet/server/config.rb#L27 Like I mentioned, even if it were viable, I’m not sure if this is the best approach for the hook being done for CFacter support. I believe the approach that Peter Huene has started pursuing could allow for CFacter to be accessed from Ruby Facter when running under JRuby without a special assist from Puppet Server. This could be advantageous for other potential reuses of CFacter from Ruby in the future where Puppet Server wouldn't be in the stack. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-4444) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title
Peter Huene commented on PUP-
Re: Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
$ jirb
2.0.0-p598 :001 > com.puppetlabs.Facter.getFact('os')
{
architecture => "x86_64",
family => "Darwin",
hardware => "x86_64",
macosx => {
build => "14D136",
product => "Mac OS X",
version => {
full => "10.10.3",
Jira (PUP-4444) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Peter Huene commented on PUP- Re: Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter Yeah, I don't think removing Facter interactions on the master is the answer. I'm looking into building an optional JNI interface into libfacter that we can make use of from JRuby. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4444) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Josh Cooper commented on PUP- Re: Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter Puppet will require (in the ruby sense) providers on the master to determine the default provider for a type. Any code that is outside of a class or instance method, will be executed on the master. For example, lib/puppet/provider/host/parsed.rb invokes Facter as soon as the file is required: case Facter.value(:osfamily) when "Solaris"; hosts = "/etc/inet/hosts" I believe any confining of providers will also be evaluated to determine suitability (during compilation). Also, this is why windows providers are guarded by the Puppet.features.microsoft_windows? feature flag, because we don't want to try to require windows gems on the master. So I think we'll find that there are many cases where Facter is executed on the master in both core puppet code and custom type & providers. Fortunately, the API is relatively "small" as we're just looking up fact values. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4444) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Peter Huene commented on PUP- Re: Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter Here's a list of facts Puppet looks for when just starting up a master: hostname (settings and catalog indirector) kernel (many different places, including provider resolution for types due to settings catalog) domain (settings, catalog indirector, CA) operatingsystem (groupadd provider due to settings catalog) That's just from starting up a default configured master. I'm going to look into JNI as a possible solution. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4444) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet / PUP- Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4444) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP- Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter Change By: Kylo Ginsberg Sprint: Client 2015- 05 04 - 13 29 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4444) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP- Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter Change By: Kylo Ginsberg Story Points: 3 Issue Type: Bug Task Summary: Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
