Bug 1217505

Summary:	IPMI driver for Ironic should support RAID for operating system/root parition
Product:	[Community] RDO	Reporter:	Tushar Katarki <tkatarki>
Component:	openstack-ironic	Assignee:	Dmitry Tantsur <dtantsur>
Status:	CLOSED EOL	QA Contact:	Toure Dunnon <tdunnon>
Severity:	high	Docs Contact:
Priority:	medium
Version:	Kilo	CC:	dyocum, markmc, mburns, srevivo
Target Milestone:	---	Flags:	dtantsur: needinfo?
Target Release:	Kilo
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-19 15:48:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tushar Katarki 2015-04-30 14:00:04 UTC

Description of problem:

As of today (04/30/2105), as part of the overcloud deployment, when using the the IPMI driver for Ironic, RDO-Manager workflow will install the glance image (operating system) for a bare metal node (which depends on the role of the node) on a single disk.

From what I understand, there are no plans to support install of images on a RAID volume.

A RAID volume for the operating system is very typical in production environments. RAID mirrors protects against disk failures. Without RAID mirrors, the system can be unusable until the disk failure is rectified. And this might require sometime thus increasing the MTTR (mean time to recovery) significantly. This is generally unacceptable in production environments.

This RFE is to request an enhancement to the RDO-Manager, wherein during the RDO-Manager overcloud deployment workflow (and when using IPMI drivers for Ironic) to support, RAID volumes for the operating system.

Note that when using Ironic with for vendor-specific Ironic drivers, RAID configuration is possible during Ready State Configuration step of the workflow. This provides an opportunity for RAID volumes to setup for the root/OS partition on the bare metal nodes before the overcloud is deployed.

The IPMI driver lacks this functionality during Ready State, in part because it is generic and therefore lacks the vendor specific tools to configure RAID. Maybe a "solution" to this RFE could be just a release note and documentation that admins would be best advised to pre-configure RAID volumes (with mirroring) for the root/operating system before the start of the RDO-Manager workflow.

Comment 1 Dan Yocum 2015-12-23 15:38:56 UTC

cc'ing mburns so he can get this into the workflow.  

I consider this NOT an RFE, but essential for a Production overcloud deployed by Director.

I see 2 tasks here:

1) auto configuration of a software RAID device given the drive unique hints (see:http://docs.openstack.org/developer/ironic/deploy/install-guide.html#specifying-the-disk-for-deployment).

2) auto configuration of hardware RAID1 for approved vendors and appropriate IPMI drivers (i.e., Dell PERC).

It is unclear to me if this is an OSP-d issue or an ironic issue, given this blueprint:

http://specs.openstack.org/openstack/ironic-specs/specs/approved/ironic-generic-raid-interface.html

and 

https://blueprints.launchpad.net/ironic/+spec/ironic-generic-raid-interface

Furthermore, this work will directly benefit the creation of RAID1 journals for Ceph OSD servers.

Comment 2 Dmitry Tantsur 2016-01-04 16:50:10 UTC

Generic IPMI does not have support for RAID. Do you want software RAID? Could someone please clarify?

Comment 3 Chandan Kumar 2016-05-19 15:48:48 UTC

This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.