Jira (PUP-5076) Non-component resources need to have defined behavior
Title: Message Title Luke Kanies commented on PUP-5076 Re: Non-component resources need to have defined behavior Henrik Lindberg We will almost definitely need to differentiate resource types - those that have to run on a local host, and those that contact remote hosts. We'll continue to fail if host-local resources are included in the catalog – just like we should fail if, for instance, Cisco resources are attempted to be used on Solaris machines. You might even find that the 'confine' mechanism works just fine to support this. It'll end up being pretty complicated, probably on multiple dimensions. In the short term (i.e., Ankeny) we just need consistent behavior. In the long term, though, it needs to align with the thread in my keynote, which is that the orchestrator becomes the integration point for all agentless work. Does that make sense? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4969) Puppet should support an arrow syntax for specifying containment edges
Title: Message Title Luke Kanies created an issue Puppet / PUP-4969 Puppet should support an arrow syntax for specifying containment edges Issue Type: Bug Assignee: Unassigned Created: 2015/07/31 3:14 AM Priority: Normal Reporter: Luke Kanies We currently have an arrow syntax for specifying dependency edges (Res[foo] - Res[bar]), and a function for making containment edges, but not a syntax for making containment edges. The function only works to add a specified resource to the current container (e.g., to specify that a resource is contained by a class), which works fine to remove the need for the 'anchor' pattern, but it doesn't work to specify containment outside of a container. This would be useful for things that behave like containers in real life but aren't containers in Puppet's language, like virtual machines. The arrow that seems obvious to me is '', because (AFAIK) it's not used and it has the right implication, but I'm open to other ideas. I'm assuming this is quite simple to implement, given we've got equivalent syntactical structures already, and equivalent semantics, so while this isn't necessarily super-high priority, I'd like to see it done. Add Comment
Jira (PDB-1786) Spike - Exported Resources for HA
Title: Message Title Luke Kanies commented on PDB-1786 Re: Spike - Exported Resources for HA It's also worth noting that we're relying on exported resources for the app mgmt work, and we're hoping to change some aspects of the behavior to better fit that use case. As you work on this, make sure you talk to Ryan Coleman. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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-3807) 'puppet config print' should sort the output
Title: Message Title Luke Kanies created an issue Puppet / PUP-3807 'puppet config print' should sort the output Issue Type: Bug Assignee: Unassigned Created: 2015/01/04 10:54 PM Priority: Normal Reporter: Luke Kanies It's pretty simple, and the output with all options is basically unreadable otherwise. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1027) PuppetDB should ship with a simpler query system that directly integrates with Puppet's SSL
Title: Message Title
Luke Kanies created an issue
PuppetDB / PDB-1027
PuppetDB should ship with a simpler query system that directly integrates with Puppet's SSL
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2014/11/13 11:22 AM
Priority:
Normal
Reporter:
Luke Kanies
This is what I wrote to make PuppetDB querying easier:
#!/bin/bash
ca_crt=$(puppet config print cacert) cert=$(puppet config print hostcert) key=$(puppet config print hostprivkey)
file=$1
curl -sk -X GET --cacert $ca_crt --cert $cert --key $key -H 'Accept: application/json' --data-urlencode query@$ {file}
https://localhost:8081/v3/resources
Much simpler than trying to handle it all manually. It could easily be extended to support different commands (e.g., pull a host's entire catalog or facts) and flags (e.g., certname).
Add Comment
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Luke Kanies commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' Eric Sorenson Does this show up anywhere in our plans? Seems like there's a lot of interest. For those who are watching, do you have a clear idea of how you want this to work? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3636) Converting from config environments should be less confusing
Title: Message Title Luke Kanies created an issue Puppet / PUP-3636 Converting from config environments should be less confusing Issue Type: Bug Assignee: Eric Sorenson Created: 2014/11/06 8:20 PM Priority: Normal Reporter: Luke Kanies Trying to follow the path of deprecation warnings from a puppet.conf that specifies modulepath and manifest to one that uses directory environments is quite confusing. The link given by the warning: http://links.puppetlabs.com/env-settings-deprecations points to the old configuration instead of a page about how to convert. Yes, that page has deprecation warnings, but this doesn't make sense. The link should point to the new configuration, with some migration information. Then, when you follow the link to the new page, it doesn't talk about the actual parameters you have to convert. The page is here: https://docs.puppetlabs.com/puppet/latest/reference/environments.html And there's no mention at all of 'manifest' or 'modulepath' on this page. These deprecation warnings need a clear path of migration - not a link to more detail on the deprecation, but a link to detail on how to make the warning go away. If I'm using 'manifest' and 'modulepath' to override these values right now (which I am, in my home directory, when running Puppet as myself on my laptop), how do I convert to directory environments? Note that I'm not actually using environments at all, I just want a custom value for these variables. How do I make these warnings go away? Where is that clearly documented?
Jira (PUP-3272) Remove support for yaml on the network
Title: Message Title
Luke Kanies commented on an issue
Re: Remove support for yaml on the network
Ah, I didn't realize the agent didn't send yaml any more - thanks for the update on that, Andy Parker.
Add Comment
Puppet / PUP-3272
Remove support for yaml on the network
YAML on the network is either dangerous or slow. It is dangerous without safe_yaml and slow with it. We've had it deprecated for a while now. Puppet 4 is the time to completely remove it. We can remove: * vendored safe_yaml * serializing and deserializing yaml * special parsing for query parameters that start with {{\-\-\-}} * more?
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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-3272) Remove support for yaml on the network
Title: Message Title
Luke Kanies commented on an issue
Re: Remove support for yaml on the network
It's worth pointing out here that the only core call that Puppet makes that still uses yaml is the one that sends the report back to the master. Just coincidentally, that also happens to be one of the slowest calls in the system. So this wouldn't just be a big security win, it would be a really big performance win.
Add Comment
Puppet / PUP-3272
Remove support for yaml on the network
YAML on the network is either dangerous or slow. It is dangerous without safe_yaml and slow with it. We've had it deprecated for a while now. Puppet 4 is the time to completely remove it. We can remove: * vendored safe_yaml * serializing and deserializing yaml * special parsing for query parameters that start with {{\-\-\-}} * more?
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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.
Jira (PUP-532) (#22719) Allow exec to runas different user on windows
Title: Message Title Luke Kanies commented on an issue Re: (#22719) Allow exec to runas different user on windows John Cooper To what extent is this a priority for Windows users? Seems like this is a pretty big difference in functionality across the platforms. Add Comment Puppet / PUP-532 (#22719) Allow exec to runas different user on windows The `exec` type has a `user` parameter that allows the exec to be performed as a different user. On Windows, this functionality is not supported, because unlike *nix, we can't switch users without the password. To support this feature, we would need to add a `password` parameter to the `exec` type, and modify the SUIDManager to support switching users ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-521) allow classes to be treated differently by documentation and classification tools
Title: Message Title
Luke Kanies commented on an issue
Re: allow classes to be treated differently by documentation and classification tools
I was expecting to just add the keyword to the class declaration. E.g.:
private class foobar { ... }
Rather than:
class foobar { ... }
private foobar
Add Comment
Puppet / PUP-521
allow classes to be treated differently by documentation and classification tools
Modern module writing patterns call for classes to be broken down to components that either provide user-facing interfaces or manage discrete pieces of functionality for the larger module. On an individual module level, this might lead to one or two classes that an author intends for others to use while the remaining four or five are just back-end cla...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (PUP-1534) Puppet classes should be able to declare that they are internal
Title: Message Title Luke Kanies created an issue Puppet / PUP-1534 Puppet classes should be able to declare that they are internal Issue Type: Story Assignee: Eric Sorenson Created: 28/Jan/14 11:21 PM Priority: Normal Reporter: Luke Kanies Many classes in Puppet are not meant to be declared directly by a node, and are instead meant only to be used internally. In these cases, the Puppet developer should be able to state that a class is internal, thus preventing that class from showing up in class lists, e.g., in the Console or the API. The primary user benefit of this is that it makes it easy for users configuring classes to focus on the list of classes you might directly associate with a host, rather than having all classes visible, whether they're for external use or not. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-536) Create endpoint for enumerating environments
Title: Message Title Luke Kanies commented on an issue Re: Create endpoint for enumerating environments Ok, thanks Aaron Armstrong was discussing the building of an environment service that the node classifier could talk to as a source of truth, and it sounds like this won't quite be that (because it would need to talk to each master). I just wanted to clarify. Add Comment Puppet / PUP-536 Create endpoint for enumerating environments Much of the Node Classifier and Continuous Delivery work is predicated on improved support for environments, and one significant gap is the absence of a way to enumerate the environments known to a puppet master. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-536) Create endpoint for enumerating environments
Title: Message Title Luke Kanies commented on an issue Re: Create endpoint for enumerating environments Will this be the single source of truth for environments, or meant more as a means of knowing what a given master sees? It seems difficult to make it a single source of truth, given that any master is likely to have a different list. Could/would we promote this to a separate service, like the node classifier? Add Comment Puppet / PUP-536 Create endpoint for enumerating environments Much of the Node Classifier and Continuous Delivery work is predicated on improved support for environments, and one significant gap is the absence of a way to enumerate the environments known to a puppet master. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
