summaryrefslogtreecommitdiffstats
path: root/docs/installationprocedure/template-os-nosdn-nofeature-ha/hardware.requirements.rst
diff options
context:
space:
mode:
authorChristopherPrice <christopher.price@ericsson.com>2016-07-26 12:05:00 +0200
committerChristopherPrice <christopher.price@ericsson.com>2016-07-26 12:05:00 +0200
commit6da365c5898a3a20638dc18b21cb1c307b61f711 (patch)
treed84fb56594670c1b16646e4055c259710ccb2c8a /docs/installationprocedure/template-os-nosdn-nofeature-ha/hardware.requirements.rst
parent7d6d582ffc69597ef82e7eed7c34e27f71b4889e (diff)
Updating the scenario installation template based on comments.
Commets from https://gerrit.opnfv.org/gerrit/#/c/16837 adressed. Change-Id: I83a58c5ec6088805a8670bc7801351d33c6e5fa8 Signed-off-by: ChristopherPrice <christopher.price@ericsson.com>
Diffstat (limited to 'docs/installationprocedure/template-os-nosdn-nofeature-ha/hardware.requirements.rst')
-rw-r--r--docs/installationprocedure/template-os-nosdn-nofeature-ha/hardware.requirements.rst88
1 files changed, 15 insertions, 73 deletions
diff --git a/docs/installationprocedure/template-os-nosdn-nofeature-ha/hardware.requirements.rst b/docs/installationprocedure/template-os-nosdn-nofeature-ha/hardware.requirements.rst
index 082d4e96b..328f92199 100644
--- a/docs/installationprocedure/template-os-nosdn-nofeature-ha/hardware.requirements.rst
+++ b/docs/installationprocedure/template-os-nosdn-nofeature-ha/hardware.requirements.rst
@@ -5,81 +5,23 @@
Hardware requirements
=====================
-The following minimum hardware requirements must be met for the
-installation of <template> scenario:
+The Pharos Lab
+--------------
-+--------------------+------------------------------------------------------+
-| **HW Aspect** | **Requirement** |
-| | |
-+====================+======================================================+
-| **# of nodes** | Minimum 5 (3 for non redundant deployment): |
-| | |
-| | - 1 Fuel deployment master (may be virtualized) |
-| | |
-| | - 3(1) Controllers (1 colocated mongo/ceilometer |
-| | role, 2 Ceph-OSD roles) |
-| | |
-| | - 1 Compute (1 co-located Ceph-OSD role) |
-| | |
-+--------------------+------------------------------------------------------+
-| **CPU** | Minimum 1 socket x86_AMD64 with Virtualization |
-| | support |
-+--------------------+------------------------------------------------------+
-| **RAM** | Minimum 16GB/server (Depending on VNF work load) |
-| | |
-+--------------------+------------------------------------------------------+
-| **Disk** | Minimum 256GB 10kRPM spinning disks |
-| | |
-+--------------------+------------------------------------------------------+
-| **Networks** | 4 Tagged VLANs (PUBLIC, MGMT, STORAGE, PRIVATE) |
-| | |
-| | 1 Un-Tagged VLAN for PXE Boot - ADMIN Network |
-| | |
-| | Note: These can be allocated to a single NIC - |
-| | or spread out over multiple NICs as your hardware |
-| | supports. |
-+--------------------+------------------------------------------------------+
+Hardware requirements for OPNFV infrastuctures are specified by the Pharos project.
+The Pharos project provides an OPNFV hardware specification for configuring your hardware
+at: http://artifacts.opnfv.org/pharos/docs/pharos-spec.html .
-Help with Hardware Requirements
-===============================
+Virtual deployment hardware requirements
+----------------------------------------
-Calculate hardware requirements:
+To perform a virtual deployment of an OPNFV scenario establised different hardware requirements.
+The server requirements for this type of deployment are outlined in the <missing spec>.
-For information on compatible hardware types available for use, please see *Reference: 11*.
-
-When choosing the hardware on which you will deploy your OpenStack
-environment, you should think about:
-
-- CPU -- Consider the number of virtual machines that you plan to deploy in your cloud environment and the CPU per virtual machine.
-
-- Memory -- Depends on the amount of RAM assigned per virtual machine and the controller node.
-
-- Storage -- Depends on the local drive space per virtual machine, remote volumes that can be attached to a virtual machine, and object storage.
-
-- Networking -- Depends on the Choose Network Topology, the network bandwidth per virtual machine, and network storage.
-
-
-Top of the rack (TOR) Configuration requirements
-================================================
-
-The switching infrastructure provides connectivity for the OPNFV
-infrastructure operations, tenant networks (East/West) and provider
-connectivity (North/South); it also provides needed connectivity for
-the Storage Area Network (SAN).
-To avoid traffic congestion, it is strongly suggested that three
-physically separated networks are used, that is: 1 physical network
-for administration and control, one physical network for tenant private
-and public networks, and one physical network for SAN.
-The switching connectivity can (but does not need to) be fully redundant,
-in such case it comprises a redundant 10GE switch pair for each of the
-three physically separated networks.
-
-The physical TOR switches are **not** automatically configured from
-the Fuel OPNFV reference platform. All the networks involved in the OPNFV
-infrastructure as well as the provider networks and the private tenant
-VLANs needs to be manually configured.
-
-Manual configuration of the Brahmaputra hardware platform should
-be carried out according to the OPNFV Pharos specification:
-<https://wiki.opnfv.org/pharos/pharos_specification>
+.. Additional Hardware requirements
+.. --------------------------------
+..
+.. Your scenario may require specific capabilities that are not explicitly stated in
+.. the Pharos spec. If this is the case add your specific hardware requirements to this
+.. section of the document under sub-headings.