diff options
Diffstat (limited to 'doc/source/install')
| -rw-r--r-- | doc/source/install/enrollment.rst | 10 | ||||
| -rw-r--r-- | doc/source/install/standalone/enrollment.rst | 4 | ||||
| -rw-r--r-- | doc/source/install/troubleshooting.rst | 3 |
3 files changed, 7 insertions, 10 deletions
diff --git a/doc/source/install/enrollment.rst b/doc/source/install/enrollment.rst index 40c63b4bb..97e2d33d4 100644 --- a/doc/source/install/enrollment.rst +++ b/doc/source/install/enrollment.rst @@ -285,12 +285,13 @@ Adding scheduling information This is not required for standalone deployments, only for those using the Compute service for provisioning bare metal instances. -#. Update the node's properties to match the actual hardware of the node: +#. Update the node's properties to match the actual hardware of the node. + These are optional. When provided, ``memory_mb`` can be used for checking + if the instance image fits into the node's memory: .. code-block:: console $ baremetal node set $NODE_UUID \ - --property cpus=$CPU_COUNT \ --property memory_mb=$RAM_MB \ --property local_gb=$DISK_GB @@ -303,14 +304,13 @@ Adding scheduling information --driver-info ipmi_username=$USER \ --driver-info ipmi_password=$PASS \ --driver-info ipmi_address=$ADDRESS \ - --property cpus=$CPU_COUNT \ --property memory_mb=$RAM_MB \ --property local_gb=$DISK_GB These values can also be discovered during `Hardware Inspection`_. - .. warning:: - The value provided for the ``local_gb`` property must match the size of + .. note:: + The value provided for the ``local_gb`` property should match the size of the root device you're going to deploy on. By default **ironic-python-agent** picks the smallest disk which is not smaller than 4 GiB. diff --git a/doc/source/install/standalone/enrollment.rst b/doc/source/install/standalone/enrollment.rst index 305091070..4fd9ebb48 100644 --- a/doc/source/install/standalone/enrollment.rst +++ b/doc/source/install/standalone/enrollment.rst @@ -87,9 +87,7 @@ Enrolling nodes #. As in case of Compute service, you can also provide ``capabilities`` to node properties, but they will be used only by Bare Metal service (for example, - boot mode). Although you don't need to add properties like ``memory_mb``, - ``cpus`` etc. as Bare Metal service will require UUID of a node you're - going to deploy. + boot mode). #. Then create a port to inform Bare Metal service of the network interface cards which are part of the node by creating a port with each NIC's MAC diff --git a/doc/source/install/troubleshooting.rst b/doc/source/install/troubleshooting.rst index 75f19c729..a40c19efd 100644 --- a/doc/source/install/troubleshooting.rst +++ b/doc/source/install/troubleshooting.rst @@ -33,8 +33,7 @@ service and Bare Metal service:: | Property | Value | +------------------------+----------------------------------------------------------------------+ | instance_uuid | None | - | properties | {u'memory_mb': u'1024', u'cpu_arch': u'x86_64', u'local_gb': u'10', | - | | u'cpus': u'1'} | + | properties | {u'memory_mb': u'1024', u'cpu_arch': u'x86_64', u'local_gb': u'10'} | | maintenance | False | | driver_info | { [SNIP] } | | extra | {} | |