[Puppet Users] Re: Restore Storconfig Data
gem versions activerecord 3.1.1 rails 3.0.1 On Oct 21, 9:33 am, sysborg dimecybo...@gmail.com wrote: master log == err: Could not call: TypeError: unknown buffer_type: 241744256: SELECT `hosts`.* FROM `hosts` WHERE `hosts`.`name` = 'testdb' LIMIT 1 === Agent log === [root@testdb ~]$ puppetd --test err: Could not retrieve catalog: TypeError: unknown buffer_type: 241744256: SELECT `hosts`.* FROM `hosts` WHERE `hosts`.`name` = 'testdb' LIMIT 1 warning: Not using cache on failed catalog == On Oct 21, 9:24 am, Scott Smith sc...@ohlol.net wrote: Run puppet. On Thu, Oct 20, 2011 at 8:57 PM, dime cyborgian dimecybo...@gmail.comwrote: I Get the initial table structure. But the tables are not populated with the data such as hosts, resources... etc. On Thu, Oct 20, 2011 at 5:30 PM, Bernd Adamowicz bernd.adamow...@esailors.de wrote: If you really dropped the database you have to recreate it before the first Puppet run: 05 mysql create database puppet; 06 Query OK, 1 row affected (0.00 sec) 07 08 mysql grant all privileges on puppet.* to puppet@localhostidentified by 'xxx'; 09 Query OK, 0 rows affected (0.00 sec) The initial table structure will then be done by Puppet. Bernd -Ursprüngliche Nachricht- Von: puppet-users@googlegroups.com [mailto:puppet- us...@googlegroups.com] Im Auftrag von sysborg Gesendet: Donnerstag, 20. Oktober 2011 13:19 An: Puppet Users Betreff: [Puppet Users] Restore Storconfig Data Hi, I did a drop database puppet which is used for storing puppet storconfigs. Now I get the following error. === err: Could not retrieve catalog: TypeError: unknown buffer_type: 498322352: SELECT `hosts`.* FROM `hosts` WHERE `hosts`.`name` = 'testdb' LIMIT 1 === Is there a way to repopulate the data. I tried reinstalling, removing /var/lib/puppet. None worked. -- 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. -- 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. -- 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. -- 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] Puppet remote resource
Hi,
No, puppet is about setting desired state of your nodes rather than current
state. That is:
'the service be started on this node'.
'this directory should not exist'.
It's not really about 'that other nodes service should be up, but if it's not
there right now, don't do this either'.
Now if you want something to take action based on a current state, like stop a
service based on some other service, you could look at MCollective or
eventhandlers in something like Nagios.
Cheers,
Den
On 21/10/2011, at 16:01, Benyi Wang bewang.t...@gmail.com wrote:
Is there a puppet module supporting remote resource? For example,
service { my_service:
ensure = stopped
require = RemoteService[remote_service]
}
If a service on a remote host is done, then stop my_service on this host.
--
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.
--
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] Publicly accessible server?
2011/10/21 Brian Gallew g...@gallew.org In theory, as long as you are NOT auto-signing certificate requests, this is exactly what the puppet server was designed for. However, you should note that the server is likely to suffer lots of random probing and may be susceptible to performance problems. [...] Set up a firewall and restrict the IPs that can access Puppet. Regards, Thomas -- Linux ... enjoy the ride! -- 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] Re: Restore Storconfig Data
puppet version 2.7.3 Change the activerecord and rails versions as per doc. rails 2.2.2 activerecord 2.3.5 Now I get the following error === err: Could not retrieve catalog from remote server: Error 400 on SERVER: NULL pointer given == The database contains the following information for host. === | id | name | ip | environment | last_compile | last_freshcheck | last_report | updated_at | source_file_id | created_at | +++--+-+-- +-+-+-+ +-+ | 1 | testdb | NULL | NULL| NULL | NULL| NULL| 2011-10-21 02:34:15 | NULL | 2011-10-21 02:34:15 | On Oct 21, 11:15 am, sysborg dimecybo...@gmail.com wrote: gem versions activerecord 3.1.1 rails 3.0.1 On Oct 21, 9:33 am, sysborg dimecybo...@gmail.com wrote: master log == err: Could not call: TypeError: unknown buffer_type: 241744256: SELECT `hosts`.* FROM `hosts` WHERE `hosts`.`name` = 'testdb' LIMIT 1 === Agent log === [root@testdb ~]$ puppetd --test err: Could not retrieve catalog: TypeError: unknown buffer_type: 241744256: SELECT `hosts`.* FROM `hosts` WHERE `hosts`.`name` = 'testdb' LIMIT 1 warning: Not using cache on failed catalog == On Oct 21, 9:24 am, Scott Smith sc...@ohlol.net wrote: Run puppet. On Thu, Oct 20, 2011 at 8:57 PM, dime cyborgian dimecybo...@gmail.comwrote: I Get the initial table structure. But the tables are not populated with the data such as hosts, resources... etc. On Thu, Oct 20, 2011 at 5:30 PM, Bernd Adamowicz bernd.adamow...@esailors.de wrote: If you really dropped the database you have to recreate it before the first Puppet run: 05 mysql create database puppet; 06 Query OK, 1 row affected (0.00 sec) 07 08 mysql grant all privileges on puppet.* to puppet@localhostidentified by 'xxx'; 09 Query OK, 0 rows affected (0.00 sec) The initial table structure will then be done by Puppet. Bernd -Ursprüngliche Nachricht- Von: puppet-users@googlegroups.com [mailto:puppet- us...@googlegroups.com] Im Auftrag von sysborg Gesendet: Donnerstag, 20. Oktober 2011 13:19 An: Puppet Users Betreff: [Puppet Users] Restore Storconfig Data Hi, I did a drop database puppet which is used for storing puppet storconfigs. Now I get the following error. === err: Could not retrieve catalog: TypeError: unknown buffer_type: 498322352: SELECT `hosts`.* FROM `hosts` WHERE `hosts`.`name` = 'testdb' LIMIT 1 === Is there a way to repopulate the data. I tried reinstalling, removing /var/lib/puppet. None worked. -- 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. -- 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. -- 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. -- 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] LSB facts
Hi All, In the example42 modules, I noticed the following is done: # Calculate OS version (without using lsb facts) $ossplit=split($operatingsystemrelease, '[.]') $osver=$ossplit[0] I've been using $lsbmajdistrelease in all my configs. Is there any particular reason why I might want to use the above instead? (apart from the dependency on redhat-lsb, which is always installed) Regards, Gonzalo -- 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] Re: Restore Storconfig Data
Fixed by uninstalling mysql gem and installing ruby-mysql using yum. On Oct 21, 12:37 pm, sysborg dimecybo...@gmail.com wrote: puppet version 2.7.3 Change the activerecord and rails versions as per doc. rails 2.2.2 activerecord 2.3.5 Now I get the following error === err: Could not retrieve catalog from remote server: Error 400 on SERVER: NULL pointer given == The database contains the following information for host. === | id | name | ip | environment | last_compile | last_freshcheck | last_report | updated_at | source_file_id | created_at | +++--+-+-- +-+-+-+ +-+ | 1 | testdb | NULL | NULL | NULL | NULL | NULL | 2011-10-21 02:34:15 | NULL | 2011-10-21 02:34:15 | On Oct 21, 11:15 am, sysborg dimecybo...@gmail.com wrote: gem versions activerecord 3.1.1 rails 3.0.1 On Oct 21, 9:33 am, sysborg dimecybo...@gmail.com wrote: master log == err: Could not call: TypeError: unknown buffer_type: 241744256: SELECT `hosts`.* FROM `hosts` WHERE `hosts`.`name` = 'testdb' LIMIT 1 === Agent log === [root@testdb ~]$ puppetd --test err: Could not retrieve catalog: TypeError: unknown buffer_type: 241744256: SELECT `hosts`.* FROM `hosts` WHERE `hosts`.`name` = 'testdb' LIMIT 1 warning: Not using cache on failed catalog == On Oct 21, 9:24 am, Scott Smith sc...@ohlol.net wrote: Run puppet. On Thu, Oct 20, 2011 at 8:57 PM, dime cyborgian dimecybo...@gmail.comwrote: I Get the initial table structure. But the tables are not populated with the data such as hosts, resources... etc. On Thu, Oct 20, 2011 at 5:30 PM, Bernd Adamowicz bernd.adamow...@esailors.de wrote: If you really dropped the database you have to recreate it before the first Puppet run: 05 mysql create database puppet; 06 Query OK, 1 row affected (0.00 sec) 07 08 mysql grant all privileges on puppet.* to puppet@localhostidentified by 'xxx'; 09 Query OK, 0 rows affected (0.00 sec) The initial table structure will then be done by Puppet. Bernd -Ursprüngliche Nachricht- Von: puppet-users@googlegroups.com [mailto:puppet- us...@googlegroups.com] Im Auftrag von sysborg Gesendet: Donnerstag, 20. Oktober 2011 13:19 An: Puppet Users Betreff: [Puppet Users] Restore Storconfig Data Hi, I did a drop database puppet which is used for storing puppet storconfigs. Now I get the following error. === err: Could not retrieve catalog: TypeError: unknown buffer_type: 498322352: SELECT `hosts`.* FROM `hosts` WHERE `hosts`.`name` = 'testdb' LIMIT 1 === Is there a way to repopulate the data. I tried reinstalling, removing /var/lib/puppet. None worked. -- 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. -- 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. -- 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. -- 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] Re: extlookup()
On Oct 20, 10:18 am, ollies...@googlemail.com
paul.seym...@barcap.com wrote:
Taking a brief look at extlookup()
We have a module to setup resolv.conf based on location so we have a %
{domain}.csv file
Can you post your $extlookup_datadir and $extlookup_precedence values?
more /etc/puppetlabs/puppet/envs/legacy/extdata/ldt.csv
domainname,my.domain.com
resolvers,10.10.10.10 10.10.10.11
searchpath,sub.my.domain.com sub2.my.domain.com
class resolver::setup {
$searchpath = extlookup(searchpath)
$resolvers = extlookup(resolvers)
$resolvdomainname = extlookup(domainname)
}
This looks correct.
Each value is getting set with the “domainname” value.
What happens if you change the order of the values in the csv file?
This is with Puppet v2.6.9
Am I doing something wrong here ?
Thanks
Paul
--
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] Re: 2.7.2 or higher repository for Ubuntu 10.04
@Scoot: I'm assuming you mean this: https://github.com/jordansissel/fpm Looks interesting, thanks. @Dan: I have a manifest for puppet client to update itself through apt. I was hoping to keep that configuration as it works very well for me. On Oct 21, 12:25 am, Scott Smith sc...@ohlol.net wrote: Use fpm. On Thu, Oct 20, 2011 at 1:53 PM, Dan Sheffner dsheff...@gmail.com wrote: *ruby 1.9.2 not puppet 1.9.2 On Thu, Oct 20, 2011 at 3:51 PM, Dan Sheffner dsheff...@gmail.com wrote: I'm compiling from source w/ rvm, and puppet 1.9.2, then installing puppet through gems. I might be able to publish my python script that does this. On Thu, Oct 20, 2011 at 3:01 PM, Evan Stachowiak evan.stachow...@gmail.com wrote: Is there a best practice or repository I can pull from to install =2.7.2 on ubuntu 10.04? I'm currently using backports and the latest available version is 2.7.1, which is below the requirements for cloud provisioner. Or should I just go ahead and compile from source? -- 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. -- 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. -- 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] Re: Announce: Puppet Dashboard 1.2.2 Available
My apologies, I didn't completely investigate the problem before complaining. My reposync cron job is not pulling down dashboard 1.2.2 to my local mirror from the EL6 x86_64 directory. After looking, I found that while the file is present on your web server, reposync is ignoring it because your repo metadata is out of date. I verified that 1.2.2 is missing from the primary.xml file, but you can tell just from the timestamps - the RPM is from 10/10 10:53, whereas the metadata is from 10/10 10:19. It would be helpful if you would automate a createrepo job to either run periodically or as part of your release process. Thanks. On Oct 20, 5:06 pm, Michael Stahnke stah...@puppetlabs.com wrote: On Thu, Oct 20, 2011 at 9:46 AM, Steve Snodgrass phe...@gmail.com wrote: Is this going to make it into the yum repo? Thanks. What is this in this context? Dashboard 1.2.2 is available in the yum repo for EL6. On Oct 10, 2:33 pm, Michael Stahnke stah...@puppetlabs.com wrote: This is a maintenance release of Puppet Dashboard 1.2.2. This release is available for download at:http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball. RPMs are also available on yum.puppetlabs.com. See the Verifying Puppet Download section at:http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.2.2http://projects.puppetlabs.com/projects/dashboard Documentation is available at:http://docs.puppetlabs.com/dashboard/index.html # Highlights for this release ## (#9940) dashboard-workers can be managed as service The stop command in the puppet-dashboard-workers init script would fail when run using a puppet service resource. This had something to do with the way sudo works on EL. Removing the sudo from the stop function allows the service to be managed by puppet reliably. And because it is stopping the process, and not creating the process, it doesn't matter whether it runs as root or puppet-dashboard. ## (#9429) Prevent editing node name The uneditable node name was displayed in a text input control, which was less than ideal for a number of reasons. Now it's plain text. ## (#9429) makes node name field readonly during edit action The readonly attribute of the node name text field is set via the @readonly_name instance variable. When nil, the node name can be edited. This commit prevents the node name from being edited, though it can be set normally during node creation. ## (#9429) adds attr_readonly to name in the node model Changes to the name attribute of nodes are ignored, via the attr_readonly attribute in the model. In the view, readonly input controls are assigned a #EEE background. spec tests updated with readonly changes. ## (#9282) Change user in database.yml.example to dashboard Previously, our database.yml.example file suggested handing the keys to the root MySQL user to Dashboard, which is a poor security practice. This commit changes the default user suggestion to dashboard, which is the default MySQL user used in Puppet Enterprise. ## (#9262) causes the contents of .section divs to scroll when overflowing This is a short-term solution to a larger problem. Dashboard is split into two columns, the sidebar (20% of window width), and the main content pane (80% of window width). The problem is when dealing with large strings of non-breaking text (e.g. file paths), the containing element runs off the screen unless accomodations are made (e.g. overflow: auto;). The better--long term--fix is to replace the 20%/80% column layout with one that allows the main content pane variable width. Thus, the entire window scrolls horizonally when elements overflow instead of requiring short-term fixes for each offending element. ## (#9215) Add a Rake task that removes nodes v1.2.2 === 484b323 Change node:delete to node:del for consistency 56b141c (#9215) Rename node:del to node:delete 20cf5fe (#9954) Add a rake task to add classes to a nodegroup d9eca18 (#9954) Add a rake task to list nodeclasses e75b51d (#9953) Add a rake task for listing nodegroups 14b93a2 Maint: adding VERSION_LINK to .gitignore 8725921 (#9940) dashboard-workers can be managed as service ce3868f (#9429) Prevent editing node name edbb48e (#9429) makes node name field readonly during edit action 14bc1e5 (#9429) adds attr_readonly to name in the node model a344e82 (#9366) removes conditional on .git for APP_VERSION_LINK 9ed1c19 (#9366) allows a custom version link to be specified 39a07de (#9773) Report content hidden 233fbf0 (#9756/Maint) Fix plugin loading. 54146c6 (#9756/Maint) Better guards around installed_plugins.
[Puppet Users] not finding function parsejson
I am getting the following error:
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: Could not autoload parsejson: no such file to load -- json at /
etc/puppetlabs/puppet/modules/ntp/manifests/init.pp:2 on node
whatever
The file is on the puppet master server:
% locate parsejson.rb
/etc/puppetlabs/puppet/modules/puppetlabs-stdlib/lib/puppet/parser/
functions/parsejson.rb
/var/opt/lib/pe-puppet/lib/puppet/parser/functions/parsejson.rb
Here is the begining of the class
class ntp(
$ntp_server = parsejson(convjson($::ntp_server))
){
But the agent is not seeing it. Any ideas?
--
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] Projects using Puppet for research on models evolution
Hi everyone, I am Federico Tomassetti, a PhD student in Software Engineering. I am interested in DSLs and I would like to study how models realized through textual DSLs evolve over time. I have heard from Henrik Lindberg about this project and I come to ask some help: I would need to access the history of some projects containing Puppet scripts. Can you suggest me some public projects or gave access to some of your projects using Puppet? Also short-lived projects with a bunch of revisions would be very useful. What I would do is download all the revisions available of a given script and compare them to reconstruct their evolution. That alone would be great but it would be perfect if I can also read the comments on the SVN/Git/etc to find commit related to bugfixing, in this way I could mark those transition differently in my analysis. Thank you for any help you can provide, Federico P.S. I am sorry if you have already read this message on the mailing-list, I was adviced that here more users could be found -- 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] LSB facts
On Fri, Oct 21, 2011 at 2:35 AM, Gonzalo Servat gser...@gmail.com wrote: Hi All, In the example42 modules, I noticed the following is done: # Calculate OS version (without using lsb facts) $ossplit=split($operatingsystemrelease, '[.]') $osver=$ossplit[0] I've been using $lsbmajdistrelease in all my configs. Is there any particular reason why I might want to use the above instead? (apart from the dependency on redhat-lsb, which is always installed) Minimal installs may not have the required lsb packages. I believe they pull in a huge amount of dependencies, like X libs, cups, etc etc on a bunch of platforms, so some people don't have them available. -- Nigel Kersten Product Manager, Puppet Labs -- 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] Puppet remote resource
On Thu, Oct 20, 2011 at 11:23 PM, Denmat tu2bg...@gmail.com wrote:
Hi,
No, puppet is about setting desired state of your nodes rather than current
state. That is:
'the service be started on this node'.
'this directory should not exist'.
If the nodes work independently, it is always true.
It's not really about 'that other nodes service should be up, but if it's
not there right now, don't do this either'.
I don't agree with this because some times different nodes of a cluster may
need to work together, such as Hadoop cluster. A Hadoop cluster has
namenode, jobtracker, datanodes and tasktrackers. If you want to bring the
whole cluster down, you need to turn off the services running on different
nodes in the order.
Hadoop provides a script to stop all services on different nodes using ssh,
but it is sequential, especially for a large cluster which has thousands
datanodes. But if puppet can provides remote resource I asked, puppet can
easily coordinate the start and stop of the whole cluster.
Now if you want something to take action based on a current state, like stop
a service based on some other service, you could look at MCollective or
eventhandlers in something like Nagios.
Cheers,
Den
On 21/10/2011, at 16:01, Benyi Wang bewang.t...@gmail.com wrote:
Is there a puppet module supporting remote resource? For example,
service { my_service:
ensure = stopped
require = RemoteService[remote_service]
}
If a service on a remote host is done, then stop my_service on this host.
--
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.
--
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.
--
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] Module Dependency with a service
If tomcat::enable is in a separate file you'll want to 'include' it in
tomcat::server to ensure it's in scope.
On Thu, Oct 20, 2011 at 4:27 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
Thanks, tried that. I moved the tomcat service out of tomcat::server
into tomcat::enable, but...
I had this in my tomcat::server class:
File {
require = Package['apache-tomcat6'],
before = Service['tomcat']
}
which now doesn't work, because it can't find the tomcat service. I tried
this:
File {
require = Package['apache-tomcat6'],
before = Class['tomcat::enable'] #Service['tomcat']
}
but puppet complains Could not find dependent Class[Tomcat::Enable].
Any ideas?
Doug.
On Thu, Oct 20, 2011 at 2:46 PM, Aaron Grewell aaron.grew...@gmail.com
wrote:
I suspect you may want a separate class, something like tomcat::enable
to handle the service independently.
On Thu, Oct 20, 2011 at 1:55 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
All,
I have a tomcat module, and another module, containing a tomcat
application called OpenAM. In the OpenAM module, I 'require' the
tomcat module, which ensures that all the tomcat bits are in place
before trying to install the OpenAM bits.
That works great except the tomcat bits includes the tomcat
service. I want the OpenAM module to require the tomcat module, but I
don't want the tomcat service to start until the OpenAM module is
complete.
What's the best practice way to arrange this?
Doug.
--
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.
--
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.
--
Regards,
Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garst...@gmail.com
Cell: +1-805-340-5627
--
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.
--
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] MySQL server has gone away
On Wed, Oct 19, 2011 at 01:58:40AM -0700, Alexey Wasilyev wrote: CentOS 5.7 on puppet master, Centos 5.7 or 6.0 on clients. puppet 2.7.5 Storeconfig enabled. activerecord-2.3.5 Time to time i got MySQL server has gone away. How can i fix it? Are you using tagmail reports? You may want to have a look at these two: http://projects.puppetlabs.com/issues/3581 http://projects.puppetlabs.com/issues/4694 -Stefan pgpUHOJ5ddaWu.pgp Description: PGP signature
Re: [Puppet Users] Puppet remote resource
MCollective seems what I want. Thanks a lot.
On Fri, Oct 21, 2011 at 9:43 AM, Benyi Wang bewang.t...@gmail.com wrote:
On Thu, Oct 20, 2011 at 11:23 PM, Denmat tu2bg...@gmail.com wrote:
Hi,
No, puppet is about setting desired state of your nodes rather than
current state. That is:
'the service be started on this node'.
'this directory should not exist'.
If the nodes work independently, it is always true.
It's not really about 'that other nodes service should be up, but if
it's not there right now, don't do this either'.
I don't agree with this because some times different nodes of a cluster
may need to work together, such as Hadoop cluster. A Hadoop cluster has
namenode, jobtracker, datanodes and tasktrackers. If you want to bring the
whole cluster down, you need to turn off the services running on different
nodes in the order.
Hadoop provides a script to stop all services on different nodes using ssh,
but it is sequential, especially for a large cluster which has thousands
datanodes. But if puppet can provides remote resource I asked, puppet can
easily coordinate the start and stop of the whole cluster.
Now if you want something to take action based on a current state, like
stop a service based on some other service, you could look at MCollective or
eventhandlers in something like Nagios.
Cheers,
Den
On 21/10/2011, at 16:01, Benyi Wang bewang.t...@gmail.com wrote:
Is there a puppet module supporting remote resource? For example,
service { my_service:
ensure = stopped
require = RemoteService[remote_service]
}
If a service on a remote host is done, then stop my_service on this
host.
--
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.
--
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.
--
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] Concatfile part fails functionally
Hi, Does anyone know which concatfilepart recipe is the code here - https://github.com/luxflux/puppet-openvpn using? I tried to use https://github.com/camptocamp/puppet-common/blob/master/manifests/definitions/concatfilepart.pp , but it fails functionally. Looks like there are lot of forks on concatfile part. If anyone knows, please point me in the right direction. Thank you, -- Srikrishna Das (krish at irc.freenode.net) -- 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] Re: Passing a variable to exec?
Thanks, that was it exactly. This works:
$addtodumplv = ((( $needump_kbsize - $pridumplv_kbsize ) /
( $pridumplv_ppsize * 1024 )) + 1 )
exec { /opt/freeware/bin/echo \extendlv $pridumplv $addtodumplv
\: }
--
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] Module Dependency with a service
Isn't the net result of including something the same as it's really
there already? If so, the final result is the same... the service
resource ends up in the tomcat::server class no?
Doug.
On Fri, Oct 21, 2011 at 10:25 AM, Aaron Grewell aaron.grew...@gmail.com wrote:
If tomcat::enable is in a separate file you'll want to 'include' it in
tomcat::server to ensure it's in scope.
On Thu, Oct 20, 2011 at 4:27 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
Thanks, tried that. I moved the tomcat service out of tomcat::server
into tomcat::enable, but...
I had this in my tomcat::server class:
File {
require = Package['apache-tomcat6'],
before = Service['tomcat']
}
which now doesn't work, because it can't find the tomcat service. I tried
this:
File {
require = Package['apache-tomcat6'],
before = Class['tomcat::enable'] #Service['tomcat']
}
but puppet complains Could not find dependent Class[Tomcat::Enable].
Any ideas?
Doug.
On Thu, Oct 20, 2011 at 2:46 PM, Aaron Grewell aaron.grew...@gmail.com
wrote:
I suspect you may want a separate class, something like tomcat::enable
to handle the service independently.
On Thu, Oct 20, 2011 at 1:55 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
All,
I have a tomcat module, and another module, containing a tomcat
application called OpenAM. In the OpenAM module, I 'require' the
tomcat module, which ensures that all the tomcat bits are in place
before trying to install the OpenAM bits.
That works great except the tomcat bits includes the tomcat
service. I want the OpenAM module to require the tomcat module, but I
don't want the tomcat service to start until the OpenAM module is
complete.
What's the best practice way to arrange this?
Doug.
--
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.
--
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.
--
Regards,
Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garst...@gmail.com
Cell: +1-805-340-5627
--
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.
--
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.
--
Regards,
Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garst...@gmail.com
Cell: +1-805-340-5627
--
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] Module Dependency with a service
True. But your 'before' already creates that dependency. Instead try
using 'require' in tomcat::enable. tomcat::enable should depend upon
tomcat::server but not vice-versa in order to make this work.
On Fri, Oct 21, 2011 at 1:50 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
Isn't the net result of including something the same as it's really
there already? If so, the final result is the same... the service
resource ends up in the tomcat::server class no?
Doug.
On Fri, Oct 21, 2011 at 10:25 AM, Aaron Grewell aaron.grew...@gmail.com
wrote:
If tomcat::enable is in a separate file you'll want to 'include' it in
tomcat::server to ensure it's in scope.
On Thu, Oct 20, 2011 at 4:27 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
Thanks, tried that. I moved the tomcat service out of tomcat::server
into tomcat::enable, but...
I had this in my tomcat::server class:
File {
require = Package['apache-tomcat6'],
before = Service['tomcat']
}
which now doesn't work, because it can't find the tomcat service. I tried
this:
File {
require = Package['apache-tomcat6'],
before = Class['tomcat::enable'] #Service['tomcat']
}
but puppet complains Could not find dependent Class[Tomcat::Enable].
Any ideas?
Doug.
On Thu, Oct 20, 2011 at 2:46 PM, Aaron Grewell aaron.grew...@gmail.com
wrote:
I suspect you may want a separate class, something like tomcat::enable
to handle the service independently.
On Thu, Oct 20, 2011 at 1:55 PM, Douglas Garstang
doug.garst...@gmail.com wrote:
All,
I have a tomcat module, and another module, containing a tomcat
application called OpenAM. In the OpenAM module, I 'require' the
tomcat module, which ensures that all the tomcat bits are in place
before trying to install the OpenAM bits.
That works great except the tomcat bits includes the tomcat
service. I want the OpenAM module to require the tomcat module, but I
don't want the tomcat service to start until the OpenAM module is
complete.
What's the best practice way to arrange this?
Doug.
--
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.
--
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.
--
Regards,
Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garst...@gmail.com
Cell: +1-805-340-5627
--
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.
--
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.
--
Regards,
Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garst...@gmail.com
Cell: +1-805-340-5627
--
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.
--
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: Announce: Puppet Dashboard 1.2.2 Available
On Fri, Oct 21, 2011 at 7:10 AM, Steve Snodgrass phe...@gmail.com wrote: My apologies, I didn't completely investigate the problem before complaining. My reposync cron job is not pulling down dashboard 1.2.2 to my local mirror from the EL6 x86_64 directory. After looking, I found that while the file is present on your web server, reposync is ignoring it because your repo metadata is out of date. I verified that 1.2.2 is missing from the primary.xml file, but you can tell just from the timestamps - the RPM is from 10/10 10:53, whereas the metadata is from 10/10 10:19. It would be helpful if you would automate a createrepo job to either run periodically or as part of your release process. Thanks. I think we updated the repodata today. Agreed, though, repodata should be updated when new packages arrive ;) On Oct 20, 5:06 pm, Michael Stahnke stah...@puppetlabs.com wrote: On Thu, Oct 20, 2011 at 9:46 AM, Steve Snodgrass phe...@gmail.com wrote: Is this going to make it into the yum repo? Thanks. What is this in this context? Dashboard 1.2.2 is available in the yum repo for EL6. On Oct 10, 2:33 pm, Michael Stahnke stah...@puppetlabs.com wrote: This is a maintenance release of Puppet Dashboard 1.2.2. This release is available for download at:http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball. RPMs are also available on yum.puppetlabs.com. See the Verifying Puppet Download section at:http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.2.2http://projects.puppetlabs.com/projects/dashboard Documentation is available at:http://docs.puppetlabs.com/dashboard/index.html # Highlights for this release ## (#9940) dashboard-workers can be managed as service The stop command in the puppet-dashboard-workers init script would fail when run using a puppet service resource. This had something to do with the way sudo works on EL. Removing the sudo from the stop function allows the service to be managed by puppet reliably. And because it is stopping the process, and not creating the process, it doesn't matter whether it runs as root or puppet-dashboard. ## (#9429) Prevent editing node name The uneditable node name was displayed in a text input control, which was less than ideal for a number of reasons. Now it's plain text. ## (#9429) makes node name field readonly during edit action The readonly attribute of the node name text field is set via the @readonly_name instance variable. When nil, the node name can be edited. This commit prevents the node name from being edited, though it can be set normally during node creation. ## (#9429) adds attr_readonly to name in the node model Changes to the name attribute of nodes are ignored, via the attr_readonly attribute in the model. In the view, readonly input controls are assigned a #EEE background. spec tests updated with readonly changes. ## (#9282) Change user in database.yml.example to dashboard Previously, our database.yml.example file suggested handing the keys to the root MySQL user to Dashboard, which is a poor security practice. This commit changes the default user suggestion to dashboard, which is the default MySQL user used in Puppet Enterprise. ## (#9262) causes the contents of .section divs to scroll when overflowing This is a short-term solution to a larger problem. Dashboard is split into two columns, the sidebar (20% of window width), and the main content pane (80% of window width). The problem is when dealing with large strings of non-breaking text (e.g. file paths), the containing element runs off the screen unless accomodations are made (e.g. overflow: auto;). The better--long term--fix is to replace the 20%/80% column layout with one that allows the main content pane variable width. Thus, the entire window scrolls horizonally when elements overflow instead of requiring short-term fixes for each offending element. ## (#9215) Add a Rake task that removes nodes v1.2.2 === 484b323 Change node:delete to node:del for consistency 56b141c (#9215) Rename node:del to node:delete 20cf5fe (#9954) Add a rake task to add classes to a nodegroup d9eca18 (#9954) Add a rake task to list nodeclasses e75b51d (#9953) Add a rake task for listing nodegroups 14b93a2 Maint: adding VERSION_LINK to .gitignore 8725921 (#9940) dashboard-workers can be managed as service ce3868f (#9429) Prevent editing node name edbb48e (#9429) makes node name field readonly during edit action 14bc1e5 (#9429) adds attr_readonly to name in the node model a344e82 (#9366) removes conditional on .git for APP_VERSION_LINK 9ed1c19
Re: [Puppet Users] Re: Announce: Puppet Dashboard 1.2.2 Available
On Sat, Oct 22, 2011 at 4:18 AM, Michael Stahnke stah...@puppetlabs.com wrote: On Fri, Oct 21, 2011 at 7:10 AM, Steve Snodgrass phe...@gmail.com wrote: My apologies, I didn't completely investigate the problem before complaining. My reposync cron job is not pulling down dashboard 1.2.2 to my local mirror from the EL6 x86_64 directory. After looking, I found that while the file is present on your web server, reposync is ignoring it because your repo metadata is out of date. I verified that 1.2.2 is missing from the primary.xml file, but you can tell just from the timestamps - the RPM is from 10/10 10:53, whereas the metadata is from 10/10 10:19. It would be helpful if you would automate a createrepo job to either run periodically or as part of your release process. Thanks. I think we updated the repodata today. Agreed, though, repodata should be updated when new packages arrive ;) One can use mtime checksum on the directory to trigger createrepo ;) Ohad On Oct 20, 5:06 pm, Michael Stahnke stah...@puppetlabs.com wrote: On Thu, Oct 20, 2011 at 9:46 AM, Steve Snodgrass phe...@gmail.com wrote: Is this going to make it into the yum repo? Thanks. What is this in this context? Dashboard 1.2.2 is available in the yum repo for EL6. On Oct 10, 2:33 pm, Michael Stahnke stah...@puppetlabs.com wrote: This is a maintenance release of Puppet Dashboard 1.2.2. This release is available for download at:http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball. RPMs are also available on yum.puppetlabs.com. See the Verifying Puppet Download section at:http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet Please report feedback via the Puppet Labs Redmine site, using an affected version of 1.2.2http://projects.puppetlabs.com/projects/dashboard Documentation is available at:http://docs.puppetlabs.com/dashboard/index.html # Highlights for this release ## (#9940) dashboard-workers can be managed as service The stop command in the puppet-dashboard-workers init script would fail when run using a puppet service resource. This had something to do with the way sudo works on EL. Removing the sudo from the stop function allows the service to be managed by puppet reliably. And because it is stopping the process, and not creating the process, it doesn't matter whether it runs as root or puppet-dashboard. ## (#9429) Prevent editing node name The uneditable node name was displayed in a text input control, which was less than ideal for a number of reasons. Now it's plain text. ## (#9429) makes node name field readonly during edit action The readonly attribute of the node name text field is set via the @readonly_name instance variable. When nil, the node name can be edited. This commit prevents the node name from being edited, though it can be set normally during node creation. ## (#9429) adds attr_readonly to name in the node model Changes to the name attribute of nodes are ignored, via the attr_readonly attribute in the model. In the view, readonly input controls are assigned a #EEE background. spec tests updated with readonly changes. ## (#9282) Change user in database.yml.example to dashboard Previously, our database.yml.example file suggested handing the keys to the root MySQL user to Dashboard, which is a poor security practice. This commit changes the default user suggestion to dashboard, which is the default MySQL user used in Puppet Enterprise. ## (#9262) causes the contents of .section divs to scroll when overflowing This is a short-term solution to a larger problem. Dashboard is split into two columns, the sidebar (20% of window width), and the main content pane (80% of window width). The problem is when dealing with large strings of non-breaking text (e.g. file paths), the containing element runs off the screen unless accomodations are made (e.g. overflow: auto;). The better--long term--fix is to replace the 20%/80% column layout with one that allows the main content pane variable width. Thus, the entire window scrolls horizonally when elements overflow instead of requiring short-term fixes for each offending element. ## (#9215) Add a Rake task that removes nodes v1.2.2 === 484b323 Change node:delete to node:del for consistency 56b141c (#9215) Rename node:del to node:delete 20cf5fe (#9954) Add a rake task to add classes to a nodegroup d9eca18 (#9954) Add a rake task to list nodeclasses e75b51d (#9953) Add a rake task for listing nodegroups 14b93a2 Maint: adding VERSION_LINK to .gitignore 8725921 (#9940) dashboard-workers can be managed as service ce3868f (#9429) Prevent editing node name edbb48e (#9429) makes node name field readonly
[Puppet Users] Re: Puppet 2.7 allows dash in variable names: bug or feature?
We have interpolations like $name-tomcat all over our manifests.
It's possible to adjust them all to ${name}-tomcat but it's not
going to be fun :)
On Oct 6, 1:19 am, Evgeny eokole...@gmail.com wrote:
perhaps you should enclose the variables in quotes to something like
this:
http://${yumserver}/repos/vmware-${esxversion-rhel6-64};
On Oct 5, 8:46 pm, Steve Snodgrass phe...@gmail.com wrote:
While testingpuppet2.7, I found that one of my manifests broke
because of the following quoted string:
http://$yumserver/repos/vmware-$esxversion-rhel6-64;
Everything in the resulting string after vmware- was blank. After
some experiments I found thatpuppet2.7allowsdashes invariable
names, and was interpreting $esxversion-rhel6-64 as one big
variable. Of course adding curly braces fixes the problem, but that
seems like a significant change. Was it intended?
Results of applying a simple test manifest:
notice(Dashtest: $fqdn-is-my-hostname)
Puppet2.6.11:
notice: Scope(Class[main]): Dashtest: foobar.example.com-is-my-
hostname
Puppet2.7.5:
notice: Scope(Class[main]): Dashtest:
-Steve
--
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: Puppet 2.7 allows dash in variable names: bug or feature?
Funny, I accidentally avoided problems caused by this change because I
always suffix variables when possible.
On Fri, Oct 21, 2011 at 10:49 PM, Jason Koppe
jason.robert.ko...@gmail.comwrote:
We have interpolations like $name-tomcat all over our manifests.
It's possible to adjust them all to ${name}-tomcat but it's not
going to be fun :)
On Oct 6, 1:19 am, Evgeny eokole...@gmail.com wrote:
perhaps you should enclose the variables in quotes to something like
this:
http://${yumserver}/repos/vmware-${esxversion-rhel6-64};
On Oct 5, 8:46 pm, Steve Snodgrass phe...@gmail.com wrote:
While testingpuppet2.7, I found that one of my manifests broke
because of the following quoted string:
http://$yumserver/repos/vmware-$esxversion-rhel6-64;
Everything in the resulting string after vmware- was blank. After
some experiments I found thatpuppet2.7allowsdashes invariable
names, and was interpreting $esxversion-rhel6-64 as one big
variable. Of course adding curly braces fixes the problem, but that
seems like a significant change. Was it intended?
Results of applying a simple test manifest:
notice(Dashtest: $fqdn-is-my-hostname)
Puppet2.6.11:
notice: Scope(Class[main]): Dashtest: foobar.example.com-is-my-
hostname
Puppet2.7.5:
notice: Scope(Class[main]): Dashtest:
-Steve
--
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.
--
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.
