Larry Ludwig wrote: > Hmm interesting idea. > > While the puppetmaster will work without issue, the issue becomes the > client (puppetd) must decode it. > > I suspect a code change. > > -L > > > On Mar 25, 2009, at 8:56 PM, Ben wrote: > > >> I just started a WAN Optimization trial with some Juniper gear, one of >> the components of WAN optimization is compression and the puppet >> client/server communication is compressing pretty well. According to >> the Juniper reporting the puppet data is being compressed between >> 25-50%. >> >> >> Is puppet using compression between client and server? >> >> If it is not, has it been considered? Considering most of the data >> exchanged between client and server would be text in the form of >> manifests and config files i think it could achieve good compression >> with low overhead. >> >> I have nginx in front of my puppetmasters, if i enable gzip >> compression >> there will the puppet client still work? >>
If you were going to make code changes in the client you may as well implement compression into puppet itself as a whole. In other words do not implement it at the "nginx" level for example but have puppetmaster and fileserver compress it's data using Zlib::GzipWriter and Zlib::GzipReader before serving it to the client and the client can use the same to do the reverse. This way a simple puppet.conf option would enable or disable compression in any deployment even without a more complicated configuration using "nginx", "apache" or whatever. Ben --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
