Thank you, that has crossed my mind but I would then have to create another
abstraction on top of the Scheduler groups to represent, well... groups. I
even thought of conventions like common prefixes to identify which
"user-group" belongs to which "group-group". Anyway, I gave up on the idea
hint: if the api doesn't allow it, it's not an envisioned scenario.
That being said, there's no limit on the worker-group configuration.
As auth relies on RBAC, workers rely on groups.
A particular group is able to process a given task ? Queue the task
assigning the correct group.
Only one
I have been testing my own hypothesis, it didn't work. I was unable to
assign a task to a specific worker, I can only assign tasks to groups.
Please correct me if I am wrong...
On Sunday, 6 May 2018 16:16:08 UTC+1, Francisco Ribeiro wrote:
>
> Thank you for confirming.
>
> I presume that I
Thank you for confirming.
I presume that I still can take a list of workers belonging to a single
group and assign the same task multiples times (once per worker), which
would still suit my needs (expect if i want to cancel it for whatever
reason which becomes harder / less convenient). Do you
No. I do not believe there is any way to guarantee that every work will
execute the same task.
On Friday, 4 May 2018 17:36:30 UTC-5, Francisco Ribeiro wrote:
>
> The question refers to submitting a task simultaneously to all workers
> within a group.
>
> Thank you
>
--
Resources:
-
5 matches
Mail list logo
