5795c57985
This would primarily be very useful for users of an external SAN image based management solution[0] where the interaction with the storage system has been abstracted from the user but iSCSI targets are still used. [0]: https://massopen.cloud/blog/bare-metal-imaging/ Change-Id: I2d45b8a7023d053aac24e106bb027b9d0408cf3a Story: #1735478 Task: #12562
14 lines
547 B
YAML
14 lines
547 B
YAML
---
|
|
features:
|
|
- |
|
|
Adds ``external`` storage interface which is short for
|
|
"externally managed". This adds logic to allow the Bare
|
|
Metal service to identify when a BFV scenario is being
|
|
requested based upon the configuration set for
|
|
``volume targets``.
|
|
|
|
The user must create the entry, and no syncronizaiton
|
|
with a Block Storage service will occur.
|
|
`Documentation <https://docs.openstack.org/ironic/latest/admin/boot-from-volume.html#use-without-cinder>`_
|
|
has been updated to reflect how to use this interface.
|