Bug 1088014

James, thanks for the RFE.

What exactly do you mean by raid_su and raid_sw? And whatever it is, is it all you need or do you expect any other information about HW RAID from OpenLMI?

(In reply to Jan Safranek from comment #2)
> James, thanks for the RFE.
My pleasure.

> 
> What exactly do you mean by raid_su and raid_sw? And whatever it is, is it
> all you need or do you expect any other information about HW RAID from
> OpenLMI?
There is probably other information that is useful, but I'm not sure what else I will need for now.

raid_su and raid_sw and stripe unit and stripe width respectively.
See: https://github.com/purpleidea/puppet-gluster/blob/master/manifests/brick.pp#L23

for an example.

Let me know if you need more info.

Thanks,
James

Ah, stripes, that sounds useful. Now, do you need a local library/cmdline tool, i.e. running on the machine with the HW RAID, or a remote API? I guess that Puppet handles the 'remote' part internally, so local API is what you seek, right?

(In reply to Jan Safranek from comment #4)
> Ah, stripes, that sounds useful. Now, do you need a local library/cmdline
> tool, i.e. running on the machine with the HW RAID, or a remote API? I guess
> that Puppet handles the 'remote' part internally, so local API is what you
> seek, right?

Correct, a local API, or more preferably a local command line tool with stable, parseable output is what I seek. If you only provide a local API, that is okay too, but then I would probably write a small python stub to call it and return something to Puppet.

Thanks for looking into this!

James

Local API (maybe with Python bindings) is provided by libstoragemgmt project. OpenLMI will only wrap it into CIM and make it available remotely.

(In reply to Jan Safranek from comment #6)
> Local API (maybe with Python bindings) is provided by libstoragemgmt
So I keep hearing about this libstoragemgmt. I didn't realize I was able (or allowed) to use it directly (actually I thought it was a c api). In any case, is it ready, and can you point me to a simple how-to-libstoragemgmt how to?

> project. OpenLMI will only wrap it into CIM and make it available remotely.

Sounds good! I actually don't think I need this use case.

[Updating the 'Summary' to reflect actual RFE.]

(In reply to James from comment #7)
> (In reply to Jan Safranek from comment #6)
> > Local API (maybe with Python bindings) is provided by libstoragemgmt
> So I keep hearing about this libstoragemgmt. I didn't realize I was able (or
> allowed) to use it directly (actually I thought it was a c api). In any
> case, is it ready, and can you point me to a simple how-to-libstoragemgmt
> how to?

See https://sourceforge.net/p/libstoragemgmt/wiki/Home/ for examples and uri syntax. Tony Asleson [libstoragemgmt author] should be able to answer specific questions.

(In reply to Jan Safranek from comment #8)
> [Updating the 'Summary' to reflect actual RFE.]
> 
> (In reply to James from comment #7)
> > (In reply to Jan Safranek from comment #6)
> > > Local API (maybe with Python bindings) is provided by libstoragemgmt
> > So I keep hearing about this libstoragemgmt. I didn't realize I was able (or
> > allowed) to use it directly (actually I thought it was a c api). In any
> > case, is it ready, and can you point me to a simple how-to-libstoragemgmt
> > how to?
> 
> See https://sourceforge.net/p/libstoragemgmt/wiki/Home/ for examples and uri
> syntax. Tony Asleson [libstoragemgmt author] should be able to answer
> specific questions.

I have talked to them on IRC. They were very friendly. Looks as if this work is in progress. Great stuff, just not 100% ready yet.

Cheers

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-2342.html