Merge "[Trivial]Fix some typos in docs"
This commit is contained in:
commit
47d4d10008
@ -188,7 +188,7 @@ the same purpose.
|
||||
Virtual Media Ramdisk
|
||||
~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
The ``ramdisk`` deploy interface can be used in concert with the the
|
||||
The ``ramdisk`` deploy interface can be used in concert with the
|
||||
``redfish-virtual-media`` boot interface to facilitate the boot of a remote
|
||||
node utilizing pre-supplied virtual media.
|
||||
|
||||
|
@ -3,7 +3,7 @@ features:
|
||||
- Adds option ``[ansible]default_python_interpreter`` to choose
|
||||
the python interpreter that ansible uses on managed machines.
|
||||
By default, ansible uses ``/usr/bin/python`` as interpreter, making the
|
||||
assumption that that path is always present on remote managed systems.
|
||||
assumption that path is always present on remote managed systems.
|
||||
This might not be always the case, for example in custom build
|
||||
images or Python 3 native distributions.
|
||||
With this option the operator has the ability to set the absolute
|
||||
@ -12,4 +12,4 @@ features:
|
||||
The same interpreter will be used in all operations that use the
|
||||
ansible deploy interface.
|
||||
It is also possible to override the value set in the configuration for a
|
||||
node by passing ``ansible_python_interpreter`` in its ``driver_info``.
|
||||
node by passing ``ansible_python_interpreter`` in its ``driver_info``.
|
||||
|
@ -3,4 +3,4 @@ fixes:
|
||||
- |
|
||||
Fixes a minor issue with ``get_boot_option`` logic that did not account
|
||||
for Software RAID. This can erroniously cause the deployment to take the
|
||||
the incorrect deployment path and attempt to install a boot loader.
|
||||
incorrect deployment path and attempt to install a boot loader.
|
||||
|
Loading…
Reference in New Issue
Block a user