Fix list rendering in the accelerator support doc
List bullets in the top level have to be left justified, otherwise we get "<blockquote>" html tags inserted. Change-Id: I35e80c23c7a6421a648c93767ab954e9a6d1e997
This commit is contained in:
parent
347d656c35
commit
d10f4169c9
|
@ -9,48 +9,48 @@ management for accelerators.
|
|||
To launch servers with accelerators, the administrator (or an user with
|
||||
appropriate privileges) must do the following:
|
||||
|
||||
* Create a device profile in Cyborg, which specifies what accelerator
|
||||
resources need to be provisioned. (See `Cyborg device profiles API
|
||||
<https://docs.openstack.org/api-ref/accelerator/v2/index.html#device-profiles>`_.
|
||||
* Create a device profile in Cyborg, which specifies what accelerator
|
||||
resources need to be provisioned. (See `Cyborg device profiles API
|
||||
<https://docs.openstack.org/api-ref/accelerator/v2/index.html#device-profiles>`_.
|
||||
|
||||
* Set the device profile name as an extra spec in a chosen flavor,
|
||||
with this syntax:
|
||||
* Set the device profile name as an extra spec in a chosen flavor,
|
||||
with this syntax:
|
||||
|
||||
.. code::
|
||||
.. code::
|
||||
|
||||
accel:device_profile=$device_profile_name
|
||||
accel:device_profile=$device_profile_name
|
||||
|
||||
The chosen flavor may be a newly created one or an existing one.
|
||||
The chosen flavor may be a newly created one or an existing one.
|
||||
|
||||
* Use that flavor to create a server:
|
||||
* Use that flavor to create a server:
|
||||
|
||||
.. code::
|
||||
.. code::
|
||||
|
||||
openstack server create --flavor $myflavor --image $myimage $servername
|
||||
openstack server create --flavor $myflavor --image $myimage $servername
|
||||
|
||||
As of 21.0.0 (Ussuri), nova supports only specific operations for instances
|
||||
with accelerators. The lists of supported and unsupported operations are as
|
||||
below:
|
||||
|
||||
* Supported operations.
|
||||
* Supported operations.
|
||||
|
||||
* Creation and deletion.
|
||||
* Reboots (soft and hard).
|
||||
* Pause and unpause.
|
||||
* Stop and start.
|
||||
* Take a snapshot.
|
||||
* Backup.
|
||||
* Rescue and unrescue.
|
||||
* Creation and deletion.
|
||||
* Reboots (soft and hard).
|
||||
* Pause and unpause.
|
||||
* Stop and start.
|
||||
* Take a snapshot.
|
||||
* Backup.
|
||||
* Rescue and unrescue.
|
||||
|
||||
* Unsupported operations
|
||||
* Unsupported operations
|
||||
|
||||
* Rebuild.
|
||||
* Resize.
|
||||
* Evacuate.
|
||||
* Suspend and resume.
|
||||
* Shelve and unshelve.
|
||||
* Cold migration.
|
||||
* Live migration.
|
||||
* Rebuild.
|
||||
* Resize.
|
||||
* Evacuate.
|
||||
* Suspend and resume.
|
||||
* Shelve and unshelve.
|
||||
* Cold migration.
|
||||
* Live migration.
|
||||
|
||||
Some operations, such as lock and unlock, work as they are effectively
|
||||
no-ops for accelerators.
|
||||
|
|
Loading…
Reference in New Issue