littlechef concurrency

9 views
Skip to first unread message

chengkai liang

unread,
Jan 22, 2015, 9:12:21 PM1/22/15
to littl...@googlegroups.com
It seems like that the concurrency (-c or --concurrency) only apply to recipe, role or simply fix -c 3 node:all.  But it cannot be applied to plugin: or chef_deploy:!  Is there any reason why concurrency cannot be use to other sub-commands?  I'd like install chef-solo or run plugin against all the current existing nodes in parallel.  Can this happen or I am missing something there.

-Chengkai

Miquel Torres

unread,
Jan 26, 2015, 4:35:05 AM1/26/15
to littl...@googlegroups.com
You are right, concurrency has no effect on those commands. Created an
issue for it:
https://github.com/tobami/littlechef/issues/235
> --
> You received this message because you are subscribed to the Google Groups
> "littlechef" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to littlechef+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Miquel Torres

unread,
Jan 26, 2015, 5:46:38 AM1/26/15
to littl...@googlegroups.com
Mmm, it does work for me! If I type for example:
fix -c 4 --env staging nodes_with_role:myrole* deploy_chef

(same with plugin:X)

it does work in parallel

chengkai liang

unread,
Jan 26, 2015, 10:35:40 AM1/26/15
to littl...@googlegroups.com
I found out that command works, but if you use fix -c 5 node:all deploy_chef: ... will not work.  There are some inconsistency between each sub-command.  Also if you do fix -c 4 nodes_with_tag:... plugin:..., then only plugin will execute.  nodes that has roles assign will not execute chef role.  It will if one specific role:...  Not sure if this is a bug or a feature.

-Chengkai
Reply all
Reply to author
Forward
0 new messages