On Sat, Oct 13, 2012 at 10:50:05PM +0200, Jakov Sosic wrote: > On 10/13/2012 05:55 PM, Dan White wrote: > > Is this module posted somewhere public ? > > Looks interesting enough to try out. > > It's not posted yet but it will be soon. I'm currently rewriting some > providers from CLI cobbler to XMLRPC calls, and I'm not yet fully > satisfied with integration with puppetlabs/apache module. I had to > modify apache module to make it work... > > > Also I have some minor issues, like first run adds system without > interfaces to cobbler, and subsequent run add interfaces. So you have to > run it twice to properly add the system. > > Maybe someone can point out is there a way to fix this, because I've > implemented interfaces as property and not param, so provider has > separate methods for checking/modifying current state, and I don't quite > get it why it doesn't run seamlessly in the first run >
If puppet has to sync ensure it will not sync any other property. That means if your type defines "ensurable" or you have defined an ensure property manually and your system is not yet present, your create method is called and puppet expects the create method to create your system with interfaces. Otherwise you will see the described behaviour: 1) First run: Puppet finds out ensure is out of sync (is absent, should be present) and calls create 2) Second run: Puppet finds out interfaces is out of sync and and calls interfaces= (or whatever method you have defined for that) (see lib/puppet/transaction/resource_harness.rb#perform_changes) -Stefan -- 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.
