[Trivialfix]Fix typos in ironic-specs
Fix the typos in ironic-specs. Change-Id: I29c96dcc5ead50bf55a6fe32e45f790039b76aec
This commit is contained in:
parent
2df28e3e86
commit
e8979ded24
|
@ -61,7 +61,7 @@ state to the ``ACTIVE`` state, bypassing actual deployment of the node.
|
|||
- Use cases of the feature while explicitly predicating that proper
|
||||
operation requires node validation to succeed.
|
||||
- Explicitly detail that it is the operator's responsibility to
|
||||
define the node with all relevent appropriate configuration else
|
||||
define the node with all relevant appropriate configuration else
|
||||
the node could fail node state provision operations of ``rebuild``
|
||||
and ``delete``. Which would result in manual intervention being
|
||||
necessary.
|
||||
|
|
|
@ -166,7 +166,7 @@ Security impact
|
|||
---------------
|
||||
|
||||
Drivers using ``iscsi_deploy.ISCSIDeploy`` will do in-band disk erase which
|
||||
will be a security benifit for tenants.
|
||||
will be a security benefit for tenants.
|
||||
|
||||
Other end user impact
|
||||
---------------------
|
||||
|
|
|
@ -103,7 +103,7 @@ Alternatives
|
|||
- Different bootloaders will have different ways of preparing their
|
||||
configuration files.
|
||||
- Though pxelinux and syslinx.efi have same configuration changes, but
|
||||
syslinux.efi is not yet availabe on ubuntu 12/13/14. syslinux.efi is
|
||||
syslinux.efi is not yet available on ubuntu 12/13/14. syslinux.efi is
|
||||
scheduled for ubuntu utopic release.
|
||||
- We will support only elilo.efi at the moment. We can later add support
|
||||
to other efi bootloader.
|
||||
|
|
|
@ -117,7 +117,7 @@ new client that support microversions and tries to communicate with an old
|
|||
Ironic. The version that the new client uses is the maximum microversion
|
||||
it supports.
|
||||
|
||||
* The user does not specify the microversion to use in communciation with
|
||||
* The user does not specify the microversion to use in communication with
|
||||
the client. Consequentally, the client attempts to use the latest
|
||||
microversion that the client knows about.
|
||||
* The client makes a connection to an old Ironic, supplying a
|
||||
|
|
|
@ -182,7 +182,7 @@ Work Items
|
|||
* Add support to PXE drivers to consume the config drive and expose it
|
||||
to the tenants.
|
||||
|
||||
* Add tempest tests (in conjuction with the Nova driver).
|
||||
* Add tempest tests (in conjunction with the Nova driver).
|
||||
|
||||
|
||||
Dependencies
|
||||
|
|
|
@ -73,7 +73,7 @@ The logic about which disk will be picked will follow:
|
|||
#. If hints are specified and only one disk is found Ironic will pick it.
|
||||
|
||||
#. If hints are specified and multiple disks are found Ironic will pick
|
||||
the first disk that matches the all the criterias.
|
||||
the first disk that matches the all the criteria.
|
||||
|
||||
#. If hints are specified and no disks are found the deployment is aborted.
|
||||
|
||||
|
|
|
@ -54,8 +54,8 @@ architecture. Then the underlying driver API for get_supported_boot_devices()
|
|||
would just assume that this node must be of a specific architecture and always
|
||||
return a static list for that architecture.
|
||||
|
||||
This approach is limiting and would result in an unecessary increase
|
||||
in the number of drivers available for ironic, and a unecessary potential
|
||||
This approach is limiting and would result in an unnecessary increase
|
||||
in the number of drivers available for ironic, and a unnecessary potential
|
||||
duplication of code.
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue