t; Date: 2018/11/28 13:09
> Subject: Re: Don't differentiate between blackbox and whitebox images
>
> I think it would be a mistake to blindly merge two container pools -
> docker actions as run today are pulled as needed and can take a long
> time, they’re subject to different kinds
Rodric Rabbah wrote on 11/28/2018 07:09:12 AM:
>
> I think it would be a mistake to blindly merge two container pools -
> docker actions as run today are pulled as needed and can take a long
> time, they’re subject to different kinds of attacks, and can affect
> performance of other tenants (highe
By configuration you can have different combinations.
Blackbox actions on blackbox invoker only, and regular actions on normal
invoker types only (ie. today)
Blackbox actions on blackbox invoker only, and regular actions on any
invoker type
Any actions on any invoker type
On Wed, Nov 28, 2018 a
I think it would be a mistake to blindly merge two container pools - docker
actions as run today are pulled as needed and can take a long time, they’re
subject to different kinds of attacks, and can affect performance of other
tenants (higher noisy neighbors).
If you want to allow more overlap
Hi,
in the past we divided the invokers into blackbox and whitebox invokers.
This has the effect that one of these two types could be overloaded while
the other type still has free capacity.
Does anyone see issues on using every invoker for everything?
Or does anyone see any action items that nee
