From 4282687699d38e4be4b39f8397f78768899ac17c Mon Sep 17 00:00:00 2001 From: Tim Rozet Date: Thu, 22 Sep 2016 15:27:56 -0400 Subject: Updates docs for scenarios/issues Changes include: - Updated scenarios table with final support info for Colorado 1.0 - Updated known issues for more scenarios - Minor RST syntax fixes Change-Id: Ied751a726a7c9cc062793c78fbac9c6e44e4a882 Signed-off-by: Tim Rozet (cherry picked from commit a0250dddb5a126000d966b2b21343ea36b9bd8e0) --- docs/installationprocedure/requirements.rst | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) (limited to 'docs/installationprocedure/requirements.rst') diff --git a/docs/installationprocedure/requirements.rst b/docs/installationprocedure/requirements.rst index d54d584b..1b3fe87d 100644 --- a/docs/installationprocedure/requirements.rst +++ b/docs/installationprocedure/requirements.rst @@ -46,14 +46,13 @@ Network requirements include: deployment. The External network is where public internet access would reside if available. -\* *These networks can be combined with each other or all combined on the - Control Plane network.* -\* *Non-External networks will be consolidated to the Control Plane network - if not specifically configured.* -\*\* *Internal API network, by default, is collapsed with provisioning in IPv4 - deployments, this is not possible with the current lack of PXE boot - support and therefore the API network is required to be its own - network in an IPv6 deployment.* +\*These networks can be combined with each other or all combined on the +Control Plane network. + +\*\*Internal API network, by default, is collapsed with provisioning in IPv4 +deployments, this is not possible with the current lack of PXE boot +support and therefore the API network is required to be its own +network in an IPv6 deployment. Bare Metal Node Requirements ---------------------------- -- cgit 1.2.3-korg