From a8a98938c3469fa51b85ad6b4e3ecf3463c5d89b Mon Sep 17 00:00:00 2001 From: Yushiro FURUKAWA Date: Mon, 24 Apr 2017 23:48:06 +0900 Subject: [PATCH] Remove future plan from portgroup document This commit removes "future plan" for portgroup to avoid misunderstanding. Change-Id: Idd64dd4af17a99d66215f3813db5484aeb40f639 --- doc/source/admin/portgroups.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/doc/source/admin/portgroups.rst b/doc/source/admin/portgroups.rst index 179bec13a7..a7fa518fe1 100644 --- a/doc/source/admin/portgroups.rst +++ b/doc/source/admin/portgroups.rst @@ -16,9 +16,7 @@ configured on the switch have to correspond to the mode and properties that will be configured on the ironic side, as bonding mode and properties may be named differently on your switch, or have possible values different from the ones described in `kernel documentation on bonding`_. Please refer to your -switch configuration documentation for more details. In the future, we may -pass the port group mode and properties to ML2 drivers so that they can do the -configuration automatically, but it is not supported as of now. +switch configuration documentation for more details. Provisioning and cleaning cannot make use of port groups if they need to boot the deployment ramdisk via (i)PXE. If your switches or desired port group