Jira (PUP-4766) Puppet packages should stick to FHS for file locations
Title: Message Title Scott Garman updated an issue Puppet / PUP-4766 Puppet packages should stick to FHS for file locations Change By: Scott Garman Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4766) Puppet packages should stick to FHS for file locations
Title: Message Title Scott Garman commented on PUP-4766 Re: Puppet packages should stick to FHS for file locations This ticket hasn't had any activity in some time (almost two years), and I can't see us going through the pain of further file location changes without a significant level of demand from our users, so I'm going to close this ticket as won't fix. We do appreciate the feedback but in the grand scheme of things we have to prioritize our efforts on other tickets. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4766) Puppet packages should stick to FHS for file locations
Title: Message Title Chris Spence commented on PUP-4766 Re: Puppet packages should stick to FHS for file locations Well, yes - FHS is a Linux thing, and I agree with you about e.g. /etc/opt being a bit unpleasant. I have seen lots of other well behaved bits of software e.g. gitlab put their variable data in /var/opt and whilst the '/opt/' part of that path might be a bit sub-optimal, the leading '/var' is in line with my expectations. From memory, I think the original reason for /var/opt was to allow PE and Puppet open source to live on the same system to provide a migration path from POSS to PE. It seems that coexistence isn't possible any more by design (at least on EL - I haven't checked other platforms). That said, the fact that it's not possible for different flavours of Puppet to coexist shouldn't make the software behave in a way contrary to established system management practices by default. Harmony is OK. Not slapping cruft all across the filesystem is good, although from a system management standpoint, I personally view slapping variable data in /opt/something/somewhereelse/cache is a species of slathering - and incidentally to a location that doesn't exist on Windows. I'm not suggesting that the tool should not provide a consistent implementation, merely a consistency that conforms more in line with how the world manages systems. I still think that most unix/linuxes recommend /var as the place to put variable data. Even, and though I stand to be corrected, I'm pretty sure that this is true even on AIX. Systemd harmony with FHS is another conversation entirely, though I think I'm right in saying systemd hasn't thrown away /var yet (though when it does, I look forward to our systemd overlords storing variable data in a shared nosql database hosted somewhere in Slough (on AIX)). 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 un
Jira (PUP-4766) Puppet packages should stick to FHS for file locations
Title: Message Title Michael Stahnke commented on PUP-4766 Re: Puppet packages should stick to FHS for file locations We chose not to follow FHS as it didn't serve for the experience many of customers and users wanted. For instance FHS says that config files should be in /etc/opt. I have not ever talked to anybody who liked that, and I've asked dozens of people about it. We had stuff in /var/opt in our PE layouts and most people didn't like it. They wanted our software to be more self-contained and less slathered throughout the filesystem. The basic use-case was "can I tar up /opt/puppetlabs and /etc/puppetlabs and migrate to a new system?" I realize it's not something everybody likes. There are trade-offs to be made. We've opted for consistency cross platform over correctness per platform. (FHS doesn't apply the same way on AIX for example). (Side note: FHS also is a little odd in that it still doens't really map with systemd /run /media etc , even in version 3 which launched less than a month ago.) 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-4766) Puppet packages should stick to FHS for file locations
Title: Message Title Chris Spence created an issue Puppet / PUP-4766 Puppet packages should stick to FHS for file locations Issue Type: Bug Assignee: Unassigned Created: 2015/06/19 2:59 AM Priority: Normal Reporter: Chris Spence Following the discussion at https://groups.google.com/forum/?fromgroups=#!topic/puppet-dev/AH8yuIGtPg8 setting default file locations for e.g. vardir to locations that don't adhere to the FHS makes Puppet more tricky to implement and maintain. The major current example of this is setting the vardir to /opt/puppetlabs/puppet/cache by default when it should be /var/opt/puppetlabs according to the FHS Add Comment This message was sent by Atlassian JIRA (v6.3.15
