Open jhoblitt opened 11 years ago
Ah, yes. This is much more in-depth than I was understanding. I definitely agree that all these related things should live under the megaraid
namespace. I look forward to using the megacli subclass and possibly the msm bits (not sure if I will use MSM at $work yet).
I've renamed both the module https://github.com/jhoblitt/puppet-megaraid/commit/64143e4a737b620dbbc6ad339b4ecdd8408112ec and the github repo itself.
A discussion over the future of this module was started in https://github.com/jhoblitt/puppet-smartd/pull/2 by @razorsedge.
I would like this module to cover a number of separate but related functions. Related enough that I don't feel putting them in separate modules is necessary.
Those functions are:
MegaRAID Storage Manager
softwareMegaCLI
softwarestorecli
softwarelsiget
script for sending debugging data back to LSISince not all of those functions are related to MSM, I think it would make sense to change the top level namespace to
megaraid
. While the manufacture is LSI, the other major LSI product lines have no software overlap. The LSI SAS HBAs don't use the same drivers or firmware as the MegaRAID controllers and the only user space toolage support is optional (multipath) and not supplied by LSI. The 3Ware controller line is apparently not going to be updated. I was told 2 years ago by LSI that they were going to release a merged 3ware/MegaRAID firmware that would worth with both existing software management sets but that has not materialized.storcli
has emerged since then and this seems to be their way of migration 3ware users to the MegaRAID line.The module structure I'm considering is something like:
with each major software component independently installable.
Perhaps also worth noting is that there is are some PCI dev facts that are useful for autoconfiguring this module.
Any thoughts/comments/feedback?