On 2013-16-09 13:48, Andy Parker wrote:
The problem with this picture for being able to batch operations
together, is that everything turns into calls on the Puppet::Type
instance, which then makes all of the individual calls to the provider.
To batch, we need to group resources together and then
On 16 September 2013 06:42, Henrik Lindberg
wrote:
> On 2013-16-09 6:22, Luke Kanies wrote:
>
>> On Sep 15, 2013, at 8:55 PM, Henrik Lindberg > **com > wrote:
>>
>> On 2013-16-09 5:41, Luke Kanies wrote:
>>>
Hi Henrik,
I know we have some users who just batch all package installs u
On 2013-16-09 6:22, Luke Kanies wrote:
On Sep 15, 2013, at 8:55 PM, Henrik Lindberg
wrote:
On 2013-16-09 5:41, Luke Kanies wrote:
Hi Henrik,
I know we have some users who just batch all package installs up front. It'd
be interesting to see if that was a feasible solution. it would by pas
On Sep 15, 2013, at 8:55 PM, Henrik Lindberg
wrote:
> On 2013-16-09 5:41, Luke Kanies wrote:
>> Hi Henrik,
>>
>> I know we have some users who just batch all package installs up front.
>> It'd be interesting to see if that was a feasible solution. it would by
>> pass the graph entirely, whi
On 2013-16-09 5:41, Luke Kanies wrote:
Hi Henrik,
I know we have some users who just batch all package installs up front. It'd
be interesting to see if that was a feasible solution. it would by pass the
graph entirely, which I'm sure could have problems, but it would, at least, be
easy to b
This isn't just an optimization. There are cases where you must
resort to exec'ing yum when, for example, two interdependent packages
must be installed in the same transaction, or one incompatible package
must be replaced by another. Note that the latter entails installing
and removing in the sam
On Friday, September 13, 2013 11:52:42 AM UTC-5, henrik lindberg wrote:
>
> [...]
> To kick this off, we need to do some research and design. So, here is an
> attempt to get this started by asking a bunch of questions.
>
> Under what conditions can two (or more) packages operations be batched?
