File resource management - speed optimization
44 views
Skip to first unread message
Bostjan Skufca
Oct 22, 2012, 6:38:47 PM10/22/12
to puppe...@googlegroups.com
Hi all,
the post below was originally intended for this list, but was unfortunately misdirected to puppet-users. As some debate has already begun around it, I will not duplicate its content here, so please see for yourself:
Can you think of any showstoppers for this feature?
b.
Luke Kanies
Oct 22, 2012, 6:46:30 PM10/22/12
to puppe...@googlegroups.com
This is pretty much exactly what the static compiler does - you can selectively enable it with something like '--compile_terminus static_compiler'.
There are some issues with it (e.g., you have to build and manage a server-side filebucket that's shared across all masters), but it was built to do almost exactly what you're trying to do. And a bit more actually, because it means that server-side code can change without it affecting client-side catalogs.
I thought we had live docs on it now, but this is what we have so far, in clearly interim form:
Those links will quite possibly not work for all that long, but hopefully they'll go live somewhere soon.
Will that do what you want?
--
--
Nigel Kersten
Oct 22, 2012, 6:48:23 PM10/22/12
to puppe...@googlegroups.com
On Mon, Oct 22, 2012 at 3:46 PM, Luke Kanies <lu...@puppetlabs.com> wrote:
> On Oct 22, 2012, at 3:38 PM, Bostjan Skufca <bostjan.s...@gmail.com>
> wrote:
>
> Hi all,
>
> the post below was originally intended for this list, but was unfortunately
> misdirected to puppet-users. As some debate has already begun around it, I
> will not duplicate its content here, so please see for yourself:
> https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/d4F9ESnRTAo
>
> Can you think of any showstoppers for this feature?
>
>
> This is pretty much exactly what the static compiler does - you can
> selectively enable it with something like '--compile_terminus
> static_compiler'.
>
> There are some issues with it (e.g., you have to build and manage a
> server-side filebucket that's shared across all masters), but it was built
> to do almost exactly what you're trying to do. And a bit more actually,
> because it means that server-side code can change without it affecting
> client-side catalogs.
>
> I thought we had live docs on it now, but this is what we have so far, in
> clearly interim form:
>
> https://github.com/puppetlabs/pre-docs/blob/master/telly/static_compiler.md
Unfortunately this is a private repo we use for "pre-docs" for all
> On Oct 22, 2012, at 3:38 PM, Bostjan Skufca <bostjan.s...@gmail.com>
> wrote:
>
> Hi all,
>
> the post below was originally intended for this list, but was unfortunately
> misdirected to puppet-users. As some debate has already begun around it, I
> will not duplicate its content here, so please see for yourself:
> https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/d4F9ESnRTAo
>
> Can you think of any showstoppers for this feature?
>
>
> This is pretty much exactly what the static compiler does - you can
> selectively enable it with something like '--compile_terminus
> static_compiler'.
>
> There are some issues with it (e.g., you have to build and manage a
> server-side filebucket that's shared across all masters), but it was built
> to do almost exactly what you're trying to do. And a bit more actually,
> because it means that server-side code can change without it affecting
> client-side catalogs.
>
> I thought we had live docs on it now, but this is what we have so far, in
> clearly interim form:
>
> https://github.com/puppetlabs/pre-docs/blob/master/telly/static_compiler.md
sorts of development notes to be turned into documentation, not just
our OSS projects.
I've pasted that info into a public gist:
https://gist.github.com/3935177
>
> https://github.com/puppetlabs/puppet/blob/master/lib/puppet/indirector/catalog/static_compiler.rb
>
> Those links will quite possibly not work for all that long, but hopefully
> they'll go live somewhere soon.
>
> Will that do what you want?
>
> --
> Luke Kanies | http://about.me/lak | http://puppetlabs.com/ | +1-615-594-8199
>
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To post to this group, send email to puppe...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-dev+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-dev?hl=en.
--
Nigel Kersten | http://puppetlabs.com | @nigelkersten
Schedule Meetings at: http://tungle.me/nigelkersten
Bostjan Skufca
Oct 22, 2012, 7:32:34 PM10/22/12
to puppe...@googlegroups.com
Thanks for quick help and docs share, but it does not seem to work. I get errors about missing files, random.
# This was added to puppetmasterd.conf file (I have separate config file for master.)
catalog_terminus = static_compiler
# This was added to site.pp
filebucket { puppet: server => 'puppetmaster.example.net', path => false } # For static compiler
# This is the additional bucket for backups, in site.pp (does not work even if I remove it)
File { backup => main }
filebucket { main: server => 'puppetmaster.example.net' }
Is there anything else I might need to add somewhere? Do I need to configure fileserver.conf? Currently normal puppet runs work without it being present on the master.
b.
Andy Parker
Oct 22, 2012, 7:49:59 PM10/22/12
to puppe...@googlegroups.com
On Mon, Oct 22, 2012 at 4:32 PM, Bostjan Skufca
<bostjan.s...@gmail.com> wrote:
> Thanks for quick help and docs share, but it does not seem to work. I get
> errors about missing files, random.
>
> # This was added to puppetmasterd.conf file (I have separate config file for
> master.)
> catalog_terminus = static_compiler
>
> # This was added to site.pp
> filebucket { puppet: server => 'puppetmaster.example.net', path => false } #
> For static compiler
>
> # This is the additional bucket for backups, in site.pp (does not work even
> if I remove it)
> File { backup => main }
> filebucket { main: server => 'puppetmaster.example.net' }
>
> Is there anything else I might need to add somewhere? Do I need to configure
> fileserver.conf? Currently normal puppet runs work without it being present
> on the master.
>
From my understanding of how it should work, I think you have all of
<bostjan.s...@gmail.com> wrote:
> Thanks for quick help and docs share, but it does not seem to work. I get
> errors about missing files, random.
>
> # This was added to puppetmasterd.conf file (I have separate config file for
> master.)
> catalog_terminus = static_compiler
>
> # This was added to site.pp
> filebucket { puppet: server => 'puppetmaster.example.net', path => false } #
> For static compiler
>
> # This is the additional bucket for backups, in site.pp (does not work even
> if I remove it)
> File { backup => main }
> filebucket { main: server => 'puppetmaster.example.net' }
>
> Is there anything else I might need to add somewhere? Do I need to configure
> fileserver.conf? Currently normal puppet runs work without it being present
> on the master.
>
the important bits. The static compiler is still an experimental
feature and has a few known bugs in it as well as possible a few
unknown bugs. If you can come up with a description of your problem
and, if at all possible, a minimal reproduction case, that would help
a lot.
> b.
>
>
> On Tuesday, 23 October 2012 00:38:48 UTC+2, Bostjan Skufca wrote:
>>
>> Hi all,
>>
>> the post below was originally intended for this list, but was
>> unfortunately misdirected to puppet-users. As some debate has already begun
>> around it, I will not duplicate its content here, so please see for
>> yourself:
>>
>> https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/d4F9ESnRTAo
>>
>> Can you think of any showstoppers for this feature?
>>
>> b.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To view this discussion on the web visit
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> https://groups.google.com/d/msg/puppet-dev/-/rqJUZF5t5usJ.
Luke Kanies
Oct 22, 2012, 7:58:25 PM10/22/12
to puppe...@googlegroups.com
On Oct 22, 2012, at 4:49 PM, Andy Parker <an...@puppetlabs.com> wrote:
> On Mon, Oct 22, 2012 at 4:32 PM, Bostjan Skufca
> <bostjan.s...@gmail.com> wrote:
>> Thanks for quick help and docs share, but it does not seem to work. I get
>> errors about missing files, random.
>>
>> # This was added to puppetmasterd.conf file (I have separate config file for
>> master.)
>> catalog_terminus = static_compiler
>>
>> # This was added to site.pp
>> filebucket { puppet: server => 'puppetmaster.example.net', path => false } #
>> For static compiler
>>
>> # This is the additional bucket for backups, in site.pp (does not work even
>> if I remove it)
>> File { backup => main }
>> filebucket { main: server => 'puppetmaster.example.net' }
>>
>> Is there anything else I might need to add somewhere? Do I need to configure
>> fileserver.conf? Currently normal puppet runs work without it being present
>> on the master.
>>
>
> From my understanding of how it should work, I think you have all of
> the important bits. The static compiler is still an experimental
> feature and has a few known bugs in it as well as possible a few
> unknown bugs. If you can come up with a description of your problem
> and, if at all possible, a minimal reproduction case, that would help
> a lot.
Indeed. If you can provide example code and specific errors, that would be helpful. I know I had this working just a couple of weeks ago. It's a bit more complicated than we'd like to get right, but it definitely worked last I checked.
> On Mon, Oct 22, 2012 at 4:32 PM, Bostjan Skufca
> <bostjan.s...@gmail.com> wrote:
>> Thanks for quick help and docs share, but it does not seem to work. I get
>> errors about missing files, random.
>>
>> # This was added to puppetmasterd.conf file (I have separate config file for
>> master.)
>> catalog_terminus = static_compiler
>>
>> # This was added to site.pp
>> filebucket { puppet: server => 'puppetmaster.example.net', path => false } #
>> For static compiler
>>
>> # This is the additional bucket for backups, in site.pp (does not work even
>> if I remove it)
>> File { backup => main }
>> filebucket { main: server => 'puppetmaster.example.net' }
>>
>> Is there anything else I might need to add somewhere? Do I need to configure
>> fileserver.conf? Currently normal puppet runs work without it being present
>> on the master.
>>
>
> From my understanding of how it should work, I think you have all of
> the important bits. The static compiler is still an experimental
> feature and has a few known bugs in it as well as possible a few
> unknown bugs. If you can come up with a description of your problem
> and, if at all possible, a minimal reproduction case, that would help
> a lot.
Bostjan Skufca
Oct 22, 2012, 8:21:53 PM10/22/12
to puppe...@googlegroups.com
Unfortunately I haven't migrated to 3.x (some dynamic scope issues, fix is already mind-brewed), so 2.7.19 will have to do:
Strace of master is here:
On Tuesday, 23 October 2012 00:38:48 UTC+2, Bostjan Skufca wrote:
Class:
[root@master:/etc/puppet/dev/modules/example/example-test]# cat manifests/init.pp
class example-test {
file { '/a':
source => "puppet:///modules/itsis-test/a",
}
}
----------------
[root@master:/etc/puppet/dev/modules/example/example-test]# cat files/a
asdf
----------------
Node class definition:
----------------
class example-server::client {
include 'example-test'
}
----------------
Node definition:
----------------
node 'client.example.org' inherits 'example_org' {
..(some unused variables)...
include 'itsis-server::timeturner'
}
----------------
Client:
--------------------
# puppet agent --test
info: Retrieving plugin
err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not retrieve information from environment production source(s) modules/example-test/a at /etc/puppet/dev/modules/example/example-test/manifests/init.pp:4
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
Server:
--------------------
# puppet master --verbose --no-daemonize --trace --catalog_terminus=static_compiler --config=/etc/puppet/puppetmasterd.conf notice: Starting Puppet master version 2.7.19
info: access[^/catalog/([^/]+)$]: allowing 'method' find
info: access[^/catalog/([^/]+)$]: allowing $1 access
info: access[^/node/([^/]+)$]: allowing 'method' find
info: access[^/node/([^/]+)$]: allowing $1 access
info: access[/certificate_revocation_list/ca]: allowing 'method' find
info: access[/certificate_revocation_list/ca]: allowing * access
info: access[/report]: allowing 'method' save
info: access[/report]: allowing * access
info: access[/file]: allowing * access
info: access[/certificate/ca]: adding authentication any
info: access[/certificate/ca]: allowing 'method' find
info: access[/certificate/ca]: allowing * access
info: access[/certificate/]: adding authentication any
info: access[/certificate/]: allowing 'method' find
info: access[/certificate/]: allowing * access
info: access[/certificate_request]: adding authentication any
info: access[/certificate_request]: allowing 'method' find
info: access[/certificate_request]: allowing 'method' save
info: access[/certificate_request]: allowing * access
info: access[/]: adding authentication any
info: Inserting default '/status' (auth true) ACL because none were found in '/etc/puppet/auth.conf'
info: Expiring the node cache of client.example.org
info: Not using expired node for client.example.org from cache; expired at Tue Oct 23 02:01:25 +0200 2012
info: Caching node for client.example.org
notice: Compiled catalog for client.example.org in environment dev in 0.08 seconds
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/parameter.rb:165:in `fail'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb:166:in `metadata'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/static_compiler.rb:37:in `find_and_replace_metadata'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/static_compiler.rb:23:in `find'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/static_compiler.rb:15:in `each'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/static_compiler.rb:15:in `find'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:195:in `find'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:109:in `do_find'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:68:in `send'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:68:in `process'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick/rest.rb:24:in `service'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:45:in `listen'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:173:in `call'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:162:in `start'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:95:in `start'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:92:in `each'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:92:in `start'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:23:in `start'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:82:in `start'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:42:in `listen'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `initialize'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `new'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `listen'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:38:in `synchronize'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:38:in `listen'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/server.rb:126:in `listen'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/server.rb:141:in `start'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/daemon.rb:124:in `start'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/application/master.rb:202:in `main'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/application/master.rb:146:in `run_command'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/application.rb:416:in `hook'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/application.rb:407:in `exit_on_fail'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:69:in `execute'
/usr/local/bin/puppet:4
err: /usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/parameter.rb:165:in `fail'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb:166:in `metadata'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/static_compiler.rb:37:in `find_and_replace_metadata'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/static_compiler.rb:23:in `find'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/static_compiler.rb:15:in `each'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/static_compiler.rb:15:in `find'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:195:in `find'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:109:in `do_find'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:68:in `send'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:68:in `process'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick/rest.rb:24:in `service'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:45:in `listen'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:173:in `call'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:162:in `start'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:95:in `start'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:92:in `each'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:92:in `start'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:23:in `start'
/usr/local/puppet-2.7.19-1/lib/ruby/1.8/webrick/server.rb:82:in `start'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:42:in `listen'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `initialize'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `new'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `listen'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:38:in `synchronize'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:38:in `listen'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/server.rb:126:in `listen'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/network/server.rb:141:in `start'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/daemon.rb:124:in `start'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/application/master.rb:202:in `main'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/application/master.rb:146:in `run_command'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/application.rb:416:in `hook'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/application.rb:407:in `exit_on_fail'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/application.rb:309:in `run'
/usr/local/puppet-2.7.19-1/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:69:in `execute'
/usr/local/bin/puppet:4
err: Could not retrieve information from environment production source(s) modules/itsis-test/a at /etc/puppet/itsis_dev/modules/itsis/itsis-test/manifests/init.pp:4
info: //client.example.org/Puppet: Retrieving plugin
err: //client.example.org/Puppet: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not retrieve information from environment production source(s) modules/itsis-test/a at /etc/puppet/itsis_dev/modules/itsis/itsis-test/manifests/init.pp:4
warning: //client.example.org/Puppet: Not using cache on failed catalog
err: //client.example.org/Puppet: Could not retrieve catalog; skipping run
-----------------------------------------
I hope this helps,
b.
On Tuesday, 23 October 2012 00:38:48 UTC+2, Bostjan Skufca wrote:
Bostjan Skufca
Oct 22, 2012, 8:23:47 PM10/22/12
to puppe...@googlegroups.com
Also, puppetmaster.conf was configured as before, and site.pp included filebucket as described previously.
b.
Andy Parker
Oct 23, 2012, 4:37:05 PM10/23/12
to puppe...@googlegroups.com
And this exact setup works if you don't use the static_compiler?
On Mon, Oct 22, 2012 at 5:23 PM, Bostjan Skufca
On Mon, Oct 22, 2012 at 5:23 PM, Bostjan Skufca
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/puppet-dev/-/Un3KV5kEQx0J.
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To view this discussion on the web visit
Bostjan Skufca
Oct 23, 2012, 5:47:57 PM10/23/12
to puppe...@googlegroups.com
Yes, it works without static_compiler setting.
Erik Dalén
Oct 24, 2012, 12:50:10 PM10/24/12
to puppe...@googlegroups.com
This prompted me to test the static compiler a bit. But the following bug I found is a total show stopper:
http://projects.puppetlabs.com/issues/17183
Otherwise it looks like it works well.
Btw, that documentation kind of suggests $server is a variable available in puppet manifests, $servername is available but can't really be used as it might differ from the certificate name or IP etc. So actually having $server would also simplify using it a bit.
--
Erik Dalén
On Monday 22 October 2012 at 18:46, Luke Kanies wrote:
> To unsubscribe from this group, send email to puppet-dev+...@googlegroups.com (mailto:puppet-dev+...@googlegroups.com).
http://projects.puppetlabs.com/issues/17183
Otherwise it looks like it works well.
Btw, that documentation kind of suggests $server is a variable available in puppet manifests, $servername is available but can't really be used as it might differ from the certificate name or IP etc. So actually having $server would also simplify using it a bit.
--
Erik Dalén
On Monday 22 October 2012 at 18:46, Luke Kanies wrote:
> --
> You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
> To post to this group, send email to puppe...@googlegroups.com (mailto:puppe...@googlegroups.com).
> You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
> To unsubscribe from this group, send email to puppet-dev+...@googlegroups.com (mailto:puppet-dev+...@googlegroups.com).
Andy Parker
Oct 24, 2012, 1:03:24 PM10/24/12
to puppe...@googlegroups.com
On Wed, Oct 24, 2012 at 9:50 AM, Erik Dalén <erik.gus...@gmail.com> wrote:
> This prompted me to test the static compiler a bit. But the following bug I found is a total show stopper:
> http://projects.puppetlabs.com/issues/17183
>
Thanks for filing that. I've linked it up as a blocker for the "make
> This prompted me to test the static compiler a bit. But the following bug I found is a total show stopper:
> http://projects.puppetlabs.com/issues/17183
>
static compiler the default" bug (#12158). If any more issues come up,
then could you add them as blockers as well?
> To unsubscribe from this group, send email to puppet-dev+...@googlegroups.com.
Andy Parker
Oct 24, 2012, 1:07:58 PM10/24/12
to puppe...@googlegroups.com
Can you write this up as a bug and mark it as a blocker for #12158?
On Tue, Oct 23, 2012 at 2:47 PM, Bostjan Skufca
> https://groups.google.com/d/msg/puppet-dev/-/Nf-eCyesiW0J.
On Tue, Oct 23, 2012 at 2:47 PM, Bostjan Skufca
Luke Kanies
Oct 24, 2012, 1:43:17 PM10/24/12
to puppe...@googlegroups.com
I can't seem to pick out the actual failure here.
I just checked the code in 2.7 (current HEAD of 2.7), and the code seems to not suffer from the problems we fixed in 3.x, so I don't have a clear idea of what the problem is.
--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-dev/-/azRBK4CxfUwJ.
To post to this group, send email to puppe...@googlegroups.com.
To unsubscribe from this group, send email to puppet-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
--
Erik Dalén
Oct 24, 2012, 2:28:56 PM10/24/12
to puppe...@googlegroups.com
On Wednesday 24 October 2012 at 13:03, Andy Parker wrote:
--
Erik Dalén
> On Wed, Oct 24, 2012 at 9:50 AM, Erik Dalén <erik.gus...@gmail.com (mailto:erik.gus...@gmail.com)> wrote:
> > This prompted me to test the static compiler a bit. But the following bug I found is a total show stopper:
> > http://projects.puppetlabs.com/issues/17183
>
>
>
> Thanks for filing that. I've linked it up as a blocker for the "make
> static compiler the default" bug (#12158). If any more issues come up,
> then could you add them as blockers as well?
Thanks. Sure I'll do that.
> > This prompted me to test the static compiler a bit. But the following bug I found is a total show stopper:
> > http://projects.puppetlabs.com/issues/17183
>
>
>
> Thanks for filing that. I've linked it up as a blocker for the "make
> static compiler the default" bug (#12158). If any more issues come up,
> then could you add them as blockers as well?
--
Erik Dalén
Reply all
Reply to author
Forward
0 new messages