Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1056103 - [RFE][ironic]: Utility ramdisk
Summary: [RFE][ironic]: Utility ramdisk
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: ---
: ---
Assignee: Keith Basil
QA Contact: Shai Revivo
URL: https://blueprints.launchpad.net/iron...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-21 14:20 UTC by RHOS Integration
Modified: 2016-05-19 23:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 23:27:03 UTC


Attachments (Terms of Use)

Description RHOS Integration 2014-01-21 14:20:51 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/ironic/+spec/utility-ramdisk.

Description:

Utility ramdisk is a ramdisk that is used by Ironic to perform maintenance of bare metal nodes.

The features it provides include:

– Firmware upgrades
– Hardware configuration
   – Setting up a RAID array
   – Turning on or off virtualisation features
   – Configuring iSCISI devices
– Volume management
   – Disk partitioning
   – Secure disk erasing


Utility ramdisk does not provide its own API due to overcomplexity of building such a disk. Instead the ramdisk polls an API endpoint provided by Ironic to get new tasks for a specific node and for reporting progress.

Ironic should be able to interrupt tasks. However, there is a subset of tasks, e.g., firmware upgrade, that should not be interruptible.

Specification URL (additional information):

None

Comment 4 Keith Basil 2016-05-19 23:27:03 UTC
Closed.


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