No-op management interface implementation.
ironic.drivers.modules.noop_mgmt.NoopManagement[source]¶Bases: ironic.drivers.base.ManagementInterface
No-op management interface implementation.
Using this implementation requires the boot order to be preconfigured to first try PXE booting, then fall back to hard drives.
get_boot_device(task)[source]¶Get the current boot device for a node.
Provides the current boot device of the node. Be aware that not all drivers support this.
| Parameters: | task – A task from TaskManager. | ||||
|---|---|---|---|---|---|
| Raises: | MissingParameterValue if a required parameter is missing | ||||
| Returns: | A dictionary containing:
|
get_properties()[source]¶Return the properties of the interface.
| Returns: | dictionary of <property name>:<property description> entries. |
|---|
get_sensors_data(task)[source]¶Get sensors data method.
| Parameters: | task – A TaskManager instance. |
|---|---|
| Raises: | FailedToGetSensorData when getting the sensor data fails. |
| Raises: | FailedToParseSensorData when parsing sensor data fails. |
| Returns: | Returns a consistent format dict of sensor data grouped by
sensor type, which can be processed by Ceilometer.
eg,{
'Sensor Type 1': {
'Sensor ID 1': {
'Sensor Reading': 'current value',
'key1': 'value1',
'key2': 'value2'
},
'Sensor ID 2': {
'Sensor Reading': 'current value',
'key1': 'value1',
'key2': 'value2'
}
},
'Sensor Type 2': {
'Sensor ID 3': {
'Sensor Reading': 'current value',
'key1': 'value1',
'key2': 'value2'
},
'Sensor ID 4': {
'Sensor Reading': 'current value',
'key1': 'value1',
'key2': 'value2'
}
}
}
|
get_supported_boot_devices(task)[source]¶Get a list of the supported boot devices.
| Parameters: | task – A task from TaskManager. |
|---|---|
| Returns: | A list with the supported boot devices defined
in ironic.common.boot_devices. |
set_boot_device(task, device, persistent=False)[source]¶Set the boot device for a node.
Set the boot device to use on next reboot of the node.
| Parameters: |
|
|---|---|
| Raises: | InvalidParameterValue if an invalid boot device is specified. |
| Raises: | MissingParameterValue if a required parameter is missing |
validate(task)[source]¶Validate the driver-specific Node deployment info.
This method validates whether the ‘driver_info’ and/or ‘instance_info’ properties of the task’s node contains the required information for this interface to function.
This method is often executed synchronously in API requests, so it should not conduct long-running checks.
| Parameters: | task – A TaskManager instance containing the node to act on. |
|---|---|
| Raises: | InvalidParameterValue on malformed parameter(s) |
| Raises: | MissingParameterValue on missing parameter(s) |
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.