Re: [Puppet Users] Facts of other nodes
Hi Ohad, > if you are interested in using foreman, see > http://blog.theforeman.org/2012/01/getting-foreman-search-results-into.html > I currently do not use foreman, but this is good incentive to look into it. Thank you very much. Joe -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Facts of other nodes
Hi John, You can use other nodes' exported resources, if there are any, but you > cannot use other nodes' facts. Multiple nodes can use the same data, > however, by obtaining them from the same source, be it global > variables, class variables, or external data (e.g. extdata or hiera). > Understood. > I don't quite follow that. "References"? Do you mean that class > some::app::db relies on a template that interpolates the value of the > db_host parameter? > Yes. > On the contrary, in your example you will have that problem all the > time. It doesn't matter what classes have been applied to other > nodes. Only classes applied to the same node are accessible to each > other. For your example to work, therefore, classes 'my_mysql_server' > and 'some::app::db' would need to be applied to the same node, and > each would see the other in the form they were applied to that node. > In that case you don't need to rely on information about other nodes, > so the question is moot. > OK, I understand now. Thank you. > Hard coding it is the quick and dirty way. It's not necessarily > wrong, but it will make your manifests more difficult to maintain as > they grow in number and complexity. > > You can instead use an external node classifier to declare your > classes and their parameters. That does require you to write or > obtain an ENC, set it up for your configuration, etc. Foreman is one > possibility there, and the Puppet Dashboard provides another. > > If you're not already using an ENC, however, then I would recommend > putting the DB server name into an external data store and reading it > into your manifest via a Puppet function. The built-in extlookup() > function provides an approach of this sort. Hiera provides a more > flexible approach of the same kind, and it will be a built-in starting > with the next major version of Puppet (Telly). > Thank you for the options - it's appreciated. Joe -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Facts of other nodes
Hi Dan, You may want to have a look at this function: > > https://github.com/puppetlabs/puppetlabs-nodesearch > > it doest map exactly to your use case, but the implementation of it is > close to what the implementation for your solution may look like. > This definitely looks useful. Thank you! > Its worth noting that once the next generation of storeconfigs comes out > (which is REALLY soon), it will have better APIs to support these kinds of > functions and I intend to write puppet functions that support these kinds > of use cases. > Good to know - thanks! Joe -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Intermittent freeze on select when running standalone
> > And why I cannot find anyone else with the same issue. > This sounds very similar, if not the same issue, that I have run into many times before. It happens during a simple "puppet apply". I always run apply with --verbose, and since there is no output at all, I figure the command has just hung. Similarly, running strace on the process results in an infinite output of select. ctrl-c does not kill the process - I have to kill the PID from another terminal. I cannot reproduce this issue at will -- it seems to happen randomly. Thanks, Joe -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Intermittent freeze on select when running standalone
Hi David, On Sun, Jul 29, 2012 at 4:28 PM, david c wrote: > So it looks (without an in depth comparison) to be this bug in the bug > tracking tool. > http://projects.puppetlabs.com/issues/13038 > Indeed this is it. Thank you for the link. > So maybe this is already solved. Just need to wait* for the 2.7.12 or > later version of pupet to make it to the debian packages for Ubuntu then > I should be able to test. > It's very disappointing / frustrating that Ubuntu LTS stocks 2.7.11 by default. :/ Thanks, Joe -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Intermittent freeze on select when running standalone
Hi Christopher, > I didn't have any difficulty replacing the version in Ubuntu 10.04 with > the version in Debian Squeeze. (Albeit that I rebuilt the package from the > source deb.) It helped me get "puppet kick" going everywhere. Right. I did not mean that it's difficult to replace the stock package. I'm more frustrated at the extra step needed to upgrade the stock package given that 12.04 is the latest version of Ubuntu + it's an LTS release. This means that administrators will either have a special step to upgrade the stock version of puppet (and then maintain that non-stock version from there on out) or will have to put up with the bug mentioned in this thread as well as miss out on built-in puppet module support. All of which would not be necessary if 12.04 just shipped with 2.7.12+. The comment was more whining on my part. Thanks, Joe -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] duplicate resources across defined types
Hello, I am hoping that someone might be able to shed some light on the best way to solve an issue. https://github.com/puppetlabs/puppetlabs-apache/commit/c2c75a62b7dafced8a6120a14bacfc8be7539282<https://github.com/puppetlabs/puppetlabs-apache/commit/c2c75a62b7dafced8a6120a14bacfc8be7539282#commitcomment-1654941> This commit introduced functionality into the vhost type to ensure that the $docroot and $logroot exist. This is smart as Apache will throw a warning if $docroot does not exist and error out if $logroot does not exist. I believe the original intention of the author was to make the names of these resources unique so that multiple vhosts can share the same docroot and logroot (line 71-80). However, the path of the resources is not unique across vhosts that use the same $docroot and $logroot and therefore puppet will error out. The first thing that came to my mind was to make the resources virtual and then just realize a single directory. Unless something special needs done, marking the two file resources as virtual (@file) still does not work. The other option that has been discussed is to use a conditional if block: https://github.com/puppetlabs/puppetlabs-apache/pull/37/files Here, on all but one of the vhost entries, you mark ensure_dirs as false and Puppet will not enforce the existence of the two directories. This works, but it comes off as a workaround more than a proper solution. Any ideas? Thanks, Joe -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] duplicate resources across defined types
Hi Dan, This is actually a pretty common modeling problem in Puppet. > I figured it had to be common as this type of configuration can exist in a lot of other system administration areas. > I just wrote a function called ensure_resource that is intended to solve > this problem. > > https://github.com/bodepd/puppet-ensure_resource > > The function allows you to ensure that a resource should exist in the > catalog. > > If the exact resource already exists in the catalog (meaning that it has > the exact type, title, and specified parameters), it will not create the > resource. Otherwise it will create the resource which could result in a > duplicate resource definition if the resource already existed but had > non-matching parameters. > > I would really like to see this incorporated into the apache module. > I agree. > thoughts? > The only thing I am curious about now is the difference between this and a virtual resource? Maybe I was under the wrong impression about virtual resources... I thought that they did this same thing. Thank you for your help and work with this! Joe -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] duplicate resources across defined types
Hi Dan, > virtual resources are definitely intended to solve the same problem, but > they would not work for this use case b/c multiple declarations of the same > virtual resource still result in the duplicate definition failures. > > virtual resources can also be problematic b/c collecting resources also > realizes them as a side effect. > I see. Thank you. I incorporated the ensure_resource function into the vhost type: https://github.com/jtopjian/puppetlabs-apache/tree/jtopjian-ensure_resource It seems to pass the test manifest that I threw at it, but it is giving these warnings: /usr/lib/ruby/1.8/puppet/parser/functions/create_resources.rb:1: warning: multiple values for a block parameter (2 for 1) from /usr/lib/ruby/1.8/puppet/parser/scope.rb:464 /usr/lib/ruby/1.8/puppet/parser/functions/create_resources.rb:1: warning: multiple values for a block parameter (2 for 1) from /etc/puppet/modules/ensure_resource/lib/puppet/parser/functions/ensure_resource.rb:24 /usr/lib/ruby/1.8/puppet/parser/functions/create_resources.rb:1: warning: multiple values for a block parameter (2 for 1) from /etc/puppet/modules/ensure_resource/lib/puppet/parser/functions/ensure_resource.rb:24 Thanks, Joe -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] duplicate resources across defined types
> > I made a few inline comments > Thank you. > should be fixed in master. > Yup, looks good. I will open a pull request for this. -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How to set DNS on Ubuntu 12.04 clients?
> > That is a very attractive solution fore sure! > > Should I just ignore that it depends on the "ubuntu-minimal" package? > ouch. Since /etc/resolv.conf is a symlink to resolvconf's resolv.conf, you can break the symlink, turn resolv.conf into a normal static file and then use the puppet module. I am not 100% confident of this solution, though, since I'm not sure if resolvconf will recreate the symlink at some point -- I haven't used this solution enough to confirm that. Thanks, Joe -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Big data is coming to Canada. Join the welcome wagon. *Cyber Summit 2012* October 1-3, Banff www.cybera.ca/summit2012 Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How to set DNS on Ubuntu 12.04 clients?
> > if /etc/resolv.conf is a puppet maintained file, even if resolvconf > package is updated, it will be replaced by the puppet asserted file anyway. > Very true, but I would hate to have two services fighting with each other in that way. -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Big data is coming to Canada. Join the welcome wagon. *Cyber Summit 2012* October 1-3, Banff www.cybera.ca/summit2012 Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Can puppet add repositories to nodes?
Hi Sandra, The Puppet Apt module should be of some use: http://puppetlabs.com/blog/module-of-the-week-puppetlabs-apt-pull-apt-strings-with-puppet/ Thanks, Joe On Mon, Sep 17, 2012 at 7:51 AM, Sandra Schlichting < littlesandr...@gmail.com> wrote: > Hi all, > > I would like to add two repositories to Ubuntu nodes > > apt-add-repository "deb http://archive.canonical.com/ $(lsb_release -sc) > partner" > > deb http://dl.google.com/linux/chrome/deb/ stable main > > > and then import the key > > > apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 16126D3A3E5C1192 > > > Can this be done in a clever way with puppet? > > > Hugs, > > Sandra > > > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/lkxkivCib8YJ. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Big data is coming to Canada. Join the welcome wagon. *Cyber Summit 2012* October 1-3, Banff www.cybera.ca/summit2012 Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] pocco - a puppet manifest documentation experiment
Hi Nan, Like everyone else, I think this is great. > Run pocco against a modules directory: > > pocco /etc/puppet/modules/ > Just a quick comment: Isn't pocco the name of the Python *occo? ( http://fitzgen.github.com/pocco/) should the name be changed to differentiate? Joe -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How to group hosts?
Hello,
I do this using facter-dot-d.
For my environment, I group by physical location, so I have a text file
"/etc/facter/facts.d/location.txt" with contents of:
location=foobar
Then "facter -p location" will output the location of the node.
Then throughout my manifests, I use the meta-parameter "tag" to tag various
resources by location:
tag => $::location
You can also use hiera in this way by having one of your hiera hierarchies
be %{location}.
Note that "location" is just arbitrary - you can use something like "role"
instead:
/etc/facter/facts.d/role.txt:
role=storage_nodes
Hope that helps,
Joe
On Thu, Dec 6, 2012 at 10:27 AM, Jakov Sosic wrote:
> Hi.
>
> I'm currently using hiera in a very rudimentary way, using only perhost
> and common.
>
> Now, I'm trying to group my hosts a little bit, so for example web
> servers could have their own yaml with data. Problem is I don't have an
> idea how to group hosts? How can I say to puppet that for example hosts:
>
> storage01
> storage02
> storage03
> storage04
>
> belong to group storage_nodes, and
>
> web01
> web02
>
> belong to group web_nodes?
>
>
> How do you do that?
>
>
> Thank you
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
Joe Topjian
Systems Administrator
Cybera Inc.
www.cybera.ca
Cybera is a not-for-profit organization that works to spur and support
innovation, for the economic benefit of Alberta, through the use
of cyberinfrastructure.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How to group hosts?
On Tue, Dec 11, 2012 at 6:52 PM, Jakov Sosic wrote: > On 12/09/2012 04:39 PM, Stefan Goethals wrote: > >> Serving facts to nodes via puppet... >> That means you already know those facts in puppet so you don't need to >> serve them to the nodes anymore :-) >> > > Yeah kinda beats the purpose of facter LOL :) But that's why I'm asking > this thread in the first place... So, how do you distribute your custom > facts like node role or servertype? Fill em up manually, enter them at > provisioning, etc? I agree that it can sound redundant in most cases, but there are a few cases when it makes sense. I think the main one is when the built-in set of facts is not enough to properly categorize your nodes. In this case, you're correct -- add the facts at the time of provisioning. Then they will be available for the first Puppet run. Thanks, Joe > > > > -- > Jakov Sosic > www.srce.unizg.hr > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@** > googlegroups.com . > For more options, visit this group at http://groups.google.com/** > group/puppet-users?hl=en<http://groups.google.com/group/puppet-users?hl=en> > . > > -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] avoiding duplicate package definitions with stdlib's "ensure_packages"
Wow - I never knew about ensure_packages. I'm not sure if I overlooked it or if it's relatively new, but either way, I agree that it should be more widely used. I run into the same issue that you described when using third-party modules. I try to avoid this in my own modules by only managing packages that are core to the module and expect the user to manage secondary packages on their own. Unfortunately this method imposes more responsibility onto the user. ensure_packages might be a good solution to this. On Tue, May 21, 2013 at 11:27 AM, Jonathan Proulx wrote: > One of the most frustrating things about puppet is duplicate definitions > of packages, > > The "ensure_packages" function from stdlib seems very much like the > correct way to handle this: > > newfunction(:ensure_packages, :type => :statement, :doc => <<-EOS > Takes a list of packages and only installs them if they don't already > exist. > EOS > ) do |arguments| > > Why isn't this a core feature? Or better why aren't resources that are > identical merged? Clearly there is a conflict if they are defined with > different parameter (ensure => installed -vs ensure => latest for example) > but if they are really identical where is the conflict? > > My current situation is that we define parted and xfsprogs in our local > site configs and the enovance ceph modules also do so. Both of these seem > reasonable to me as we need them to make all our systems go and the ceph > module needs them to set up the object storage volumes (which is it's > primary function) and can't assume everyone uses parted and xfs. > > The two prevailing opinions in my web readings seem to be to use Virtual > resources which is fine for local modules but not so good for sharing and > the purist opinion that if there is a conflict the conflicting parts should > be split out into an independent module, which is fine for large functional > chunks like httpd but ridiculous for single utilities that require no > configuration. > > Yet there is little discussion of ensure_packages as an alternative. Is > this for cause or just because it is not well known? > > -Jon > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Joe Topjian Systems Architect Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Parsing issues in 3.5
Hello, I keep running into several parsing issues in 3.5 that don't exist in Puppet 3.4. I saw the thread about issues with the future parser and defined types: https://groups.google.com/forum/#!topic/puppet-users/HOVnQ1EXwjY I'm using the future parser, but I'm seeing issues in other manifests besides defined types. Two examples are: https://github.com/saz/puppet-rsyslog/issues/74 https://github.com/arioch/puppet-redis/blob/master/manifests/init.pp For the Redis example, I had to add redis:: to each of the include statements and Class resources. I understand why those changes needed made, but I don't understand what caused them to appear in 3.5.x when everything works fine in 3.4. I read that Puppet 3.6 fixes some issues with the future parser. Are the issues I'm seeing known and fixed? Thanks, Joe -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/94532ad1-75c3-48c3-92a9-0bcd583e1133%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Parsing issues in 3.5
Hi Henrik, On Saturday, May 10, 2014 2:56:19 PM UTC-4, Henrik Lindberg wrote: In 3.5 the new evaluator was added and it is on by default when using > --parser future. If you want to turn it off you can use --evaluator > current in addition to --parser future) > > If it works under --evaluator current but not under --evaluator future, > we like to hear about it, please file a ticket in that case. > I apologize for the late reply! Thank you for your reply and information. I'm away from the office this week, but will try this out as soon as I have a chance. Thanks again, Joe -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0bfa296d-54f8-49cf-b9e5-5a585909bd22%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Parsing issues in 3.5
Hi Henrik, In 3.5 the new evaluator was added and it is on by default when using > --parser future. If you want to turn it off you can use --evaluator > current in addition to --parser future) > > If it works under --evaluator current but not under --evaluator future, > we like to hear about it, please file a ticket in that case. > Again, sorry for the late reply, but I wanted to confirm that setting evaluator to current did resolve the issue. I'll file a ticket now. Thanks, Joe -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7012cca2-c637-4be8-983a-dd9a0fc38297%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
