From 10260a173eda4b3210a1baa0e36dfc3a062b869a Mon Sep 17 00:00:00 2001 From: Hironori Shiina Date: Wed, 12 Oct 2016 22:11:12 +0900 Subject: [PATCH] A few fixes in Multitenancy document This patch fixes the following items in Multitenancy documentation[1]. - A security group rule for iSCSI should be ingress because a node is connected from ironic conductor. - A URL of an article of ML2 plugin configuration has been changed at Newton. [1] http://docs.openstack.org/developer/ironic/deploy/multitenancy.html Change-Id: I65400cd6717ce4d9c23f41a20f24ee96f9415c4d --- doc/source/deploy/multitenancy.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/deploy/multitenancy.rst b/doc/source/deploy/multitenancy.rst index 72628aabd2..d61940152a 100644 --- a/doc/source/deploy/multitenancy.rst +++ b/doc/source/deploy/multitenancy.rst @@ -98,7 +98,7 @@ interface as stated above): * egress port used for ironic (6385 by default) * ingress port used for ironic-python-agent (9999 by default) * if using the iSCSI deploy method (``pxe_*`` and ``iscsi_*`` drivers), - the egress port used for iSCSI (3260 by default) + the ingress port used for iSCSI (3260 by default) * if using the direct deploy method (``agent_*`` drivers), the egress port used for swift (typically 80 or 443) * if using iPXE, the egress port used for the HTTP server running @@ -106,7 +106,7 @@ interface as stated above): #. Install and configure a compatible ML2 mechanism driver which supports bare metal provisioning for your switch. See `ML2 plugin configuration manual - `_ + `_ for details. #. Restart the ironic conductor and API services after the modifications: