I was curious while reading this, it seems like we're touching on a few
different potentials.
1) Sending catalog diffs.
2) Asynchronous catalog compilation.
I think that #2 might be critical to scaling and sort of mirrors what Peter
was doing with the CM Guard. Basically, instead of the Puppet cl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
> Is there already some kind of code doing that, or any
> opinion/feedback on this idea?
I have written once a change management guard, that does some of the
stuff you mentioned and as a side-effect also includes caching - or I
abused caching
On Fri, Jul 3, 2015 at 10:13 AM, Erik Dalén
wrote:
>
>
> On Fri, 3 Jul 2015 at 11:05 Chris Price wrote:
>
>> On Fri, Jul 3, 2015 at 9:50 AM, Erik Dalén
>> wrote:
>>
>>>
>>>
>>> On Fri, 3 Jul 2015 at 09:25 Chris Price wrote:
>>>
On Monday, June 29, 2015 at 6:02:17 PM UTC+1, Luke
On Fri, 3 Jul 2015 at 11:05 Chris Price wrote:
> On Fri, Jul 3, 2015 at 9:50 AM, Erik Dalén
> wrote:
>
>>
>>
>> On Fri, 3 Jul 2015 at 09:25 Chris Price wrote:
>>
>>>
>>>
>>> On Monday, June 29, 2015 at 6:02:17 PM UTC+1, Luke Kanies wrote:
On Jun 29, 2015, at 8:43 AM, Raphaël Pinson
>
On Fri, Jul 3, 2015 at 9:50 AM, Erik Dalén
wrote:
>
>
> On Fri, 3 Jul 2015 at 09:25 Chris Price wrote:
>
>>
>>
>> On Monday, June 29, 2015 at 6:02:17 PM UTC+1, Luke Kanies wrote:
>>>
>>> On Jun 29, 2015, at 8:43 AM, Raphaël Pinson
>>> wrote:
>>> >
>>> > Hello,
>>> >
>>> >
>>> > I've activated c
On Fri, 3 Jul 2015 at 09:25 Chris Price wrote:
>
>
> On Monday, June 29, 2015 at 6:02:17 PM UTC+1, Luke Kanies wrote:
>>
>> On Jun 29, 2015, at 8:43 AM, Raphaël Pinson
>> wrote:
>> >
>> > Hello,
>> >
>> >
>> > I've activated caching on our Puppetservers, using the admin API to
>> invalidate the
On Monday, June 29, 2015 at 6:02:17 PM UTC+1, Luke Kanies wrote:
>
> On Jun 29, 2015, at 8:43 AM, Raphaël Pinson > wrote:
> >
> > Hello,
> >
> >
> > I've activated caching on our Puppetservers, using the admin API to
> invalidate the cache upon deploying new environments. However, this onl
