xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-05-21 11:12:04 +00:00
Code Issues Releases Wiki Activity

Spelling fixes in admin-guides/manage_clusters/ppc64le docs

Browse Source
This commit is contained in:
besawn 2022-02-11 13:39:31 -05:00
parent a681e35c0e
commit 4f99f07f5a
9 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms/discovery_using_defined.rst
View File

@ -101,7 +101,7 @@ The BMC IP address is obtained by the open range dhcp server and the plan in thi
chdef cn01 chain="runcmd=bmcsetup"
#. **[Optional]** More operation plan to do after hardware disocvery is done, ``ondiscover`` option can be used.
#. **[Optional]** More operation plan to do after hardware discovery is done, ``ondiscover`` option can be used.
For example, configure console, copy SSH key for **OpenBMC**, then disable ``powersupplyredundancy`` ::

2
docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/mtms/discovery_using_dhcp.rst
View File

@ -85,7 +85,7 @@ The BMC IP address is obtained by the open range dhcp server and the plan is to
chdef cn01 chain="runcmd=bmcsetup"
#. **[Optional]** More operation plan to do after hardware disocvery is done, ``ondiscover`` option can be used.
#. **[Optional]** More operation plan to do after hardware discovery is done, ``ondiscover`` option can be used.
For example, configure console, copy SSH key for **OpenBMC**, then disable ``powersupplyredundancy`` ::

2
docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/seq_discovery.rst
View File

@ -28,7 +28,7 @@ In order to do BMC configuration during the discovery process, set ``runcmd=bmcs
chdef cn1 chain="runcmd=bmcsetup"
**[Optional]** More operation plan to do after hardware disocvery is done, ``ondiscover`` option can be used.
**[Optional]** More operation plan to do after hardware discovery is done, ``ondiscover`` option can be used.
For example, configure console, copy SSH key for **OpenBMC**, then disable ``powersupplyredundancy`` ::

2
docs/source/guides/admin-guides/manage_clusters/ppc64le/discovery/switch_discovery.rst
View File

@ -65,7 +65,7 @@ In order to do BMC configuration during the discovery process, set ``runcmd=bmcs
chdef cn1 chain="runcmd=bmcsetup"
**[Optional]** More operation plan to do after hardware disocvery is done, ``ondiscover`` option can be used.
**[Optional]** More operation plan to do after hardware discovery is done, ``ondiscover`` option can be used.
For example, configure console, copy SSH key for **OpenBMC**, then disable ``powersupplyredundancy`` ::

2
docs/source/guides/admin-guides/manage_clusters/ppc64le/diskful/customize_image/network/cfg_network_adapter.rst
View File

@ -1,7 +1,7 @@
Configure Additional Network Interfaces - confignetwork
-------------------------------------------------------
The ``confignetwork`` postscript can be used to configure the network interfaces on the compute nodes to support Ethernet adapters, VLAN, BONDs, and BRIDGES. ``confignetwork`` can be used in postscripts during OS privision, it can also be executed in ``updatenode``. The way the ``confignetwork`` postscript decides what IP address to give the secondary adapter is by checking the ``nics`` table, in which the nic configuration information is stored. In order for the ``confignetwork`` postscript to run successfully, the following attributes must be configured for the node in the ``nics`` table:
The ``confignetwork`` postscript can be used to configure the network interfaces on the compute nodes to support Ethernet adapters, VLAN, BONDs, and BRIDGES. ``confignetwork`` can be used in postscripts during OS provisioning, it can also be executed in ``updatenode``. The way the ``confignetwork`` postscript decides what IP address to give the secondary adapter is by checking the ``nics`` table, in which the nic configuration information is stored. In order for the ``confignetwork`` postscript to run successfully, the following attributes must be configured for the node in the ``nics`` table:
* ``nicips``
* ``nictypes``

2
docs/source/guides/admin-guides/manage_clusters/ppc64le/diskless/customize_image/network/cfg_network_adapter.rst
View File

@ -1,7 +1,7 @@
Configure Additional Network Interfaces - confignetwork
-------------------------------------------------------
The ``confignetwork`` postscript can be used to configure the network interfaces on the compute nodes to support Ethernet adapters, VLAN, BONDs, and BRIDGES. ``confignetwork`` can be used in postscripts during OS privision, it can also be executed in ``updatenode``. The way the ``confignetwork`` postscript decides what IP address to give the secondary adapter is by checking the ``nics`` table, in which the nic configuration information is stored. In order for the ``confignetwork`` postscript to run successfully, the following attributes must be configured for the node in the ``nics`` table:
The ``confignetwork`` postscript can be used to configure the network interfaces on the compute nodes to support Ethernet adapters, VLAN, BONDs, and BRIDGES. ``confignetwork`` can be used in postscripts during OS provisioning, it can also be executed in ``updatenode``. The way the ``confignetwork`` postscript decides what IP address to give the secondary adapter is by checking the ``nics`` table, in which the nic configuration information is stored. In order for the ``confignetwork`` postscript to run successfully, the following attributes must be configured for the node in the ``nics`` table:
* ``nicips``
* ``nictypes``

2
docs/source/guides/admin-guides/manage_clusters/ppc64le/statelite/index.rst
View File

@ -31,7 +31,7 @@ There are two solutions: ``NFSROOT-based`` and ``RAMdisk-based``.
**Disadvantages**
However, there're still several disadvantages, especially for the ``NFSROOT-based`` solution.
However, there are still several disadvantages, especially for the ``NFSROOT-based`` solution.
#. NFS Root requires more network traffic to run as the majority of the disk image runs over NFS. This may depend on your workload, but can be minimized. Since the bulk of the image is read-only, NFS caching on the server helps minimize the disk access on the server, and NFS caching on the client helps reduce the network traffic.
#. NFS Root can be complex to set up. As more files are created in different places, there are greater chances for failures. This flexibility is also one of the great virtues of Statelite. The image can work in nearly any environment.

4
docs/source/guides/admin-guides/manage_clusters/ppc64le/statelite/provision_statelite.rst
View File

@ -119,7 +119,7 @@ Set up Post scripts for statelite
The rules to create post install scripts for statelite image is the same as the rules for stateless/diskless install images.
There're two kinds of postscripts for statelite (also for stateless/diskless).
There are two kinds of postscripts for statelite (also for stateless/diskless).
The first kind of postscript is executed at genimage time, it is executed again the image itself on the MN . It was setup in The postinstall file section before the image was generated.
@ -207,7 +207,7 @@ Boot the statelite node
Make sure you have set up all the attributes in your node definitions correctly following the node installation instructions corresponding to your hardware:
You can now deploy the node by running the following commmands: ::
You can now deploy the node by running the following commands: ::
rinstall <noderange>

2
docs/source/guides/admin-guides/manage_clusters/ppc64le/virtual_machines/FAQ.rst
View File

@ -67,7 +67,7 @@ rmigrate fails with "Error: 38, message: failed to create directory '<dir-name>'
vm1: Error: 38, message: failed to create directory '<dir-name>': File exists: Unknown issue libvirt error code.
**Solution**:
Ususally happens when `nfs:` is specified for vmstorage attribute but that NFS directory is no longer mounted. Make sure the directory /var/lib/xcat/pools is empty on the destination kvmhost.
Usually happens when `nfs:` is specified for vmstorage attribute but that NFS directory is no longer mounted. Make sure the directory /var/lib/xcat/pools is empty on the destination kvmhost.
Error: Cannot communicate via libvirt to kvmhost1