Jira (PUP-4073) rundir and logdir are no longer relative to vardir
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4073 rundir and logdir are no longer relative to vardir Change By: Steve Barlow Scope Change Reason: AIO Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4073) rundir and logdir are no longer relative to vardir
Title: Message Title Christopher Price commented on PUP-4073 Re: rundir and logdir are no longer relative to vardir OMG, run_mode. Josh Cooper Jeff McCune I looked at the commit and I understand the issue now, and I guess I'm OK with the proposed path for now, but it's disconcerting. Basically, the problem we have today is that the implementation of 'run_mode' is tightly coupled with the user account, and that's just totally, totally backwards for Puppet Server... because we will never be running as root, but we always want the root-user version of the paths. If we stick with the current direction of things, it will mean that we need to duplicate every run_mode-related setting in puppetserver.conf, and pass them all in to the ruby code when we boot up. Before, that list was limited to one or two settings (confdir/vardir), and now it looks like we're talking about increasing that to 4. The user will have to potentially be aware of this and may need to modify these settings in two places. We are also at risk of the 'puppet master --configprint' command line tool returning invalid results for these settings. I've suffered through the pain associated with that part of the code base enough to know how tricky it is to deal with, so if this is the path of least resistance and everyone thinks it's the only timely way to get things finished up, I won't argue too much. But it feels pretty ugly and risky. I wonder if there's some other way that we could handle this such that the decision about the run_mode (during early boot up of the process) wouldn't be so tightly coupled to the UID of the process? Like, what if we tweaked things so that the only two args that Puppet Server passed into the ruby code were '- confdir' and some new flag like ' run-mode'. Then we could tweak Puppet so that in the spot where it determines the default run mode, it'd notice that cli flag and override the normal behavior? Skip the user check and put us into 'master' run_mode right away? This would be an improvement on the current releases in that we wouldn't even need to pass ' vardir' any longer, in addition to avoiding the need to add ' logdir' and ' -rundir' on top of everything else. It'd also allow us to get rid of some hacky code in Puppet Server where we have to force the run mode to 'master' after the settings have already all been loaded with 'agent/user' run_mode, as it works today. Thoughts? Add Comment
Jira (PUP-4073) rundir and logdir are no longer relative to vardir
Title: Message Title Jeff McCune commented on PUP-4073 Re: rundir and logdir are no longer relative to vardir Thanks Josh Cooper. Christopher Price, what do you think? It appears that it would be more costly to resolve this in the puppet side and instead we should solve it in puppet-server, matching up logdir and rundir both in production and in our unit tests rather than relying on them following vardir. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4073) rundir and logdir are no longer relative to vardir
Title: Message Title Jeff McCune updated an issue Puppet / PUP-4073 rundir and logdir are no longer relative to vardir Change By: Jeff McCune Summary: Childdirectoriesdon'tfollowparentdirectories rundirandlogdirarenolongerrelativetovardir Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4073) rundir and logdir are no longer relative to vardir
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-4073 rundir and logdir are no longer relative to vardir Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4073) rundir and logdir are no longer relative to vardir
Title: Message Title Matthaus Owens commented on PUP-4073 Re: rundir and logdir are no longer relative to vardir Jeremy Barlow I had a similar thought not too long ago. If which_dir had 3 cases instead of 2, it could meet puppetserver's needs. The 3 cases I can think of are: running as root running as puppet user in master runmode (everything else) running as non-root user Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4073) rundir and logdir are no longer relative to vardir
Title: Message Title Jeremy Barlow commented on PUP-4073 Re: rundir and logdir are no longer relative to vardir +1 to coming up with some alternative means of instructing core Ruby Puppet code to use the root-compatible paths when running under Puppet Server instead of perpetuating the duplicated settings across puppetserver.conf and puppet.conf. Would be great, in the process, to eliminate the need for Puppet Server `master-var-dir` configuration . Could this come down to somehow changing the logic in run_mode.rb's which_dir - https://github.com/puppetlabs/puppet/blob/e155144211688f883dd770f07b676311e9b421c1/lib/puppet/util/run_mode.rb#L52 - to force the root settings to be used even if Puppet.features.root? is false, maybe through reading back on some flag that only Puppet Server would set. I presume we don't want to have Puppet Server somehow configure `Puppet.feature.root?` to true because of other runtime uses of that feature flag that Puppet Server running under the puppet user would violate. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
