Improve support for Chef-Solo

[hufman]

Some organizations may want to deploy some of their Ceph stack using Chef-Solo, and some pieces naturally lend themselves to it, like the radosgw or iscsi nodes. This issue is a way to brainstorm for ways to improve support for Chef-Solo.

[hufman]

The current main things that Chef Server is needed for are:

• Searching for monitor nodes mon_nodes, only used by mon_addresses and mon_secret
• Getting the IP addresses of those monitor nodes, for inserting into ceph.conf mon_addresses
• Getting the mon_secret from the monitors, for setting up keys mon_secret
• (future) Getting the cluster fsid from the monitors, for inserting into ceph.conf

[hufman]

Because of how Chef-Solo works, this data will have to be provided as node attributes. All of the above data would have to be added:

• monitor ips
• monitor secret, if generating keys is desired
• perhaps preloading any client keys instead of fetching/generating it during runtime
• cluster fsid will be needed for OSDs and MONs

[lccheung]

Hi Hufman,

Any fix plan or target fix-by-date of this issue? My organization is also using chef-solo and would like to deploy ceph by chef-solo.

Regards,
Taurus

[tomzo]

I have added some initial work towards handling chef-solo. Most notably, I added more detailed error messages in cases when search was called and chef-solo was used. The work is in branch chef-solo in my fork b47a2e0
It is not complete, but enough to create an all-in-one node using chef-solo.