| | |
| | These can be allocated to a single NIC |
| | or spread out over multiple NICs. |
+| | |
+| | .. WARNING:: |
+| | |
+| | No external ``DHCP`` server should be present |
+| | in the ``PXE/admin`` network segment, as it |
+| | would interfere with ``MaaS`` ``DHCP`` during |
+| | ``baremetal`` node commissioning/deploying. |
+------------------+------------------------------------------------------+
| **Power mgmt** | All targets need to have power management tools that |
| | allow rebooting the hardware (e.g. ``IPMI``). |
+=================================+===========================================+
| ``nova_cpu_pinning`` | List of CPU cores nova will be pinned to. |
| | |
-| | .. WARNING:: |
+| | .. NOTE:: |
| | |
| | Currently disabled. |
+---------------------------------+-------------------------------------------+
During ``MaaS`` commissioning phase, IP addresses are handed out by
``MaaS``'s DHCP.
-.. NOTE::
+.. WARNING::
Default addresses in below table correspond to a ``PXE/admin`` CIDR of
``192.168.11.0/24`` (the usual value used in OPNFV labs).
``management`` often has an IP range offset defined in ``IDF``.
-.. NOTE::
-
- Default addresses in below table correspond to a ``management`` CIDR of
- ``172.16.10.0/24`` (one of the commonly used values in OPNFV labs).
- This is defined in ``IDF`` and can easily be changed to something else.
-
.. WARNING::
Default addresses in below table correspond to a ``management`` IP range of
``internal`` does not usually use an IP range offset in ``IDF``.
-.. NOTE::
+.. WARNING::
Default addresses in below table correspond to an ``internal`` CIDR of
``10.1.0.0/24`` (the usual value used in OPNFV labs).
``public`` often has an IP range offset defined in ``IDF``.
-.. NOTE::
-
- Default addresses in below table correspond to a ``public`` CIDR of
- ``172.30.10.0/24`` (one of the used values in OPNFV labs).
- This is defined in ``IDF`` and can easily be changed to something else.
-
.. WARNING::
Default addresses in below table correspond to a ``public`` IP range of