1088014 – [RFE] libstoragemgmt should be able to create/modify/read from RAID devices

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1088014 - [RFE] libstoragemgmt should be able to create/modify/read from RAID devices

Summary: [RFE] libstoragemgmt should be able to create/modify/read from RAID devices

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	libstoragemgmt
Sub Component:
Version:	7.2
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Gris Ge
QA Contact:	Barry Donahue
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2014-04-15 20:21 UTC by James (purpleidea)
Modified:	2021-09-03 14:09 UTC (History)
CC List:	8 users (show)
Fixed In Version:
Doc Type:	Rebase: Bug Fixes and Enhancements
Doc Text:	Rebase package(s) to version: 1.2.3 Add raid adapter support for: - LSI MegaRAID - HP SmartArray
Clone Of:
Environment:
Last Closed:	2015-11-19 11:46:19 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2015:2342	0	normal	SHIPPED_LIVE	libstoragemgmt bug fix and enhancement update	2015-11-19 10:30:44 UTC

Description James (purpleidea) 2014-04-15 20:21:49 UTC

Description of problem:

It would be great if OpenLMI/libstoragemgmt could make HW RAID devices, and read properties such as raid_sw, and raid_su.

This would be useful for Puppet-Gluster so that it could automatically manage RAID devices, and set the correct performance parameters too.

https://github.com/purpleidea/puppet-gluster

Cheers!

(Stephen Gallagher asked me to file this!)


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Jan Safranek 2014-04-16 11:51:56 UTC

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?

Comment 3 James (purpleidea) 2014-04-17 21:15:55 UTC

(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

Comment 4 Jan Safranek 2014-04-18 13:18:40 UTC

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?

Comment 5 James (purpleidea) 2014-04-18 16:24:04 UTC

(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

Comment 6 Jan Safranek 2014-04-22 07:41:47 UTC

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

Comment 7 James (purpleidea) 2014-04-23 06:29:24 UTC

(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.

Comment 8 Jan Safranek 2014-04-28 14:42:19 UTC

[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.

Comment 9 James (purpleidea) 2014-04-28 22:48:51 UTC

(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

Comment 10 RHEL Program Management 2014-05-06 05:48:34 UTC

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.

Comment 13 errata-xmlrpc 2015-11-19 11:46:19 UTC

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

Note You need to log in before you can comment on or make changes to this bug.