Configuration management integration (chef / puppet / ansible / etc.)

[krig]

Should we include a chef recipe / puppet module using crmsh to configure a cluster?

[dmuhamedagic]

@tserong After your long stint in clouds could you offer some advice?

[tserong]

The short answer is: I don't know. The long answer is, possibly not, but I could be wrong. AFAIK there have been a number of pacemaker/corosync chef cookbooks in various places, so I suspect including one in crmsh might be a case of adding yet another set of cookbooks to the mix; unless crmsh became an authoritative source for pacemaker cookbooks, it might not be worthwhile.

We should also ask @aspiers, as he's spent a fair bit of time in this area :-)

[krig]

The reasoning behind this request is that when we visited Linbit, they mentioned that people had been asking for that.

Using or referring to the cloud cookbooks by @aspiers makes sense to me, but that only covers one of the CM tools...

[aspiers]

What are the other CM tools? Not sure what CM refers to.

Please see https://trello.com/c/5t563xX1

I think it makes sense to keep the Chef LWRPs and Ruby bindings in separate repos, but they could be officially adopted and maintained as part of the ClusterLabs project if you want?

[krig]

I can't access that trello board :/ By CM I meant Configuration management tool, like chef / puppet / etc.

Yeah, keeping them separate makes sense to me as well.

[aspiers]

The card is entitled "P8 #HA: upstream corosync/pacemaker cookbooks" and it's in progress but sort of stalled.

[krig]

I found out that there is now a project to create an ansible playbook for pacemaker here:

https://github.com/egroeper/ansible-pacemaker