From aa88673c38be12368dead5e8241fb915d790c431 Mon Sep 17 00:00:00 2001 From: Julien Date: Thu, 17 Aug 2017 21:32:10 +0800 Subject: restruct documents according to opnfvdocs Use only development and release for we don't have test codes for now. JIRA: PHAROS-311 Change-Id: Iacfcaba81a7a52e09cf999b8603cc9dc2f8f2b97 Signed-off-by: Julien --- docs/specification/networkconfig.rst | 62 ------------------------------------ 1 file changed, 62 deletions(-) delete mode 100644 docs/specification/networkconfig.rst (limited to 'docs/specification/networkconfig.rst') diff --git a/docs/specification/networkconfig.rst b/docs/specification/networkconfig.rst deleted file mode 100644 index fa95faa5..00000000 --- a/docs/specification/networkconfig.rst +++ /dev/null @@ -1,62 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 -.. (c) 2016 OPNFV. - - -Networking ----------- - -**Network Hardware** - - * 24 or 48 Port TOR Switch - * NICs - Combination of 1GE and 10GE based on network topology options (per server can be on-board - or use PCI-e) - * Connectivity for each data/control network is through a separate NIC. This - simplifies Switch Management however requires more NICs on the server and also more switch ports - * BMC (Baseboard Management Controller) for lights-out mangement network using IPMI (Intelligent - Platform Management Interface) - -**Network Options** - - * Option I: 4x1G Control, 2x10G Data, 48 Port Switch - - * 1 x 1G for lights-out Management - * 1 x 1G for Admin/PXE boot - * 1 x 1G for control-plane connectivity - * 1 x 1G for storage - * 2 x 10G for data network (redundancy, NIC bonding, High bandwidth testing) - - * Option II: 1x1G Control, 2x 10G Data, 24 Port Switch - - * Connectivity to networks is through VLANs on the Control NIC - * Data NIC used for VNF traffic and storage traffic segmented through VLANs - - * Option III: 2x1G Control, 2x10G Data, 2x10G Storage, 24 Port Switch - - * Data NIC used for VNF traffic - * Storage NIC used for control plane and Storage segmented through VLANs (separate host traffic - from VNF) - * 1 x 1G for lights-out mangement - * 1 x 1G for Admin/PXE boot - * 2 x 10G for control-plane connectivity/storage - * 2 x 10G for data network - -Documented configuration to include: - - - Subnet, VLANs (may be constrained by existing lab setups or rules) - - IPs - - Types of NW - lights-out, public, private, admin, storage - - May be special NW requirements for performance related projects - - Default gateways - -**Sample Network Drawings** - -.. image:: ../images/bridge2.png - -.. image:: ../images/opnfv-pharos-diagram-v01.jpg - -.. image:: ../images/opnfv-example-lab-diagram.png - -Download the visio zip file here: -`opnfv-example-lab-diagram.vsdx.zip -`_ -- cgit 1.2.3-korg