diff options
| author | Jan Gutter <jan.gutter@netronome.com> | 2019-04-02 14:15:17 +0200 |
|---|---|---|
| committer | Jan Gutter <jan.gutter@netronome.com> | 2019-04-02 15:09:44 +0200 |
| commit | 3e703a6b2fb655157d9355f80ac2f005f9dd11c0 (patch) | |
| tree | 31becce784a1f30c25e5f65c2c011771f8897235 /doc | |
| parent | d52aacd29df9bae182e73ce6547ef08c6ada3dbd (diff) | |
| download | ironic-3e703a6b2fb655157d9355f80ac2f005f9dd11c0.tar.gz | |
Slightly rephrase note in tenant networking docs
* Taken out of context, the note could cause a bit of confusion,
explicitly note the difference between flat and neutron networking.
Change-Id: Ief0cf6861b510af50574fdf623526a1560301caf
Signed-off-by: Jan Gutter <jan.gutter@netronome.com>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/source/install/configure-tenant-networks.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/source/install/configure-tenant-networks.rst b/doc/source/install/configure-tenant-networks.rst index d7b17d42e..c5d54b8d1 100644 --- a/doc/source/install/configure-tenant-networks.rst +++ b/doc/source/install/configure-tenant-networks.rst @@ -76,11 +76,11 @@ provisioning will happen in a multi-tenant environment (which means using the tenant. .. note:: - Spawning a bare metal instance onto the provisioning network is - impossible, the deployment will fail. The node should be deployed onto a - different network than the provisioning network. When you boot a bare - metal instance from the Compute service, you should choose a different - network in the Networking service for your instance. + When using the ``flat`` network interface, bare metal instances are + normally spawned onto the "provisioning" network. This is not supported + with the ``neutron`` interface and the deployment will fail. Please + ensure a different network is chosen in the Networking service when + a bare metal instance is booted from the Compute service. .. note:: The "provisioning" and "cleaning" networks may be the same network or |