Pharos Specification

Table of Contents

Objectives / Scope

The Pharos specification defines the OPNFV hardware environment upon which the OPNFV Arno platform release can be deployed on and tested. This specification defines:

Deploying Arno in a Virtualized environment is possible and will be useful, however it does not provide a fully featured deployment and test environment for the Arno release of OPNFV.

The high level architecture is outlined in the following diagram:

images/pharos-archi1.jpg

A Pharos compliant OPNFV test-bed environment provides

Hardware requirements

Servers

CPU:

Local Storage Configuration:

Below describes the minimum for the Pharos spec, which is designed to provide enough capacity for a reasonably functional environment. Additional and/or faster disks are nice to have and may produce a better result.

Memory:

Power Supply Single

Provisioning the jump server

  1. Obtain CentOS 7 Minimal ISO and install
wget http://mirrors.kernel.org/centos/7/isos/x86_64/CentOS-7-x86_64-Minimal-1503-01.iso
  1. Set parameters appropriate for your environment during installation
  2. Disable NetworkManager
systemctl disable NetworkManager
  1. Configure your /etc/sysconfig/network-scripts/ifcfg-* files for your network
  2. Restart networking
service network restart
  1. Edit /etc/resolv.conf and add a nameserver
vi /etc/resolv.conf
  1. Install libvirt & kvm
yum -y update yum -y install kvm qemu-kvm libvirt systemctl enable libvirtd
  1. Reboot:
shutdown -r now
  1. If you wish to avoid annoying delay when use ssh to log in, disable DNS lookups:
vi /etc/ssh/sshd_config Uncomment "UseDNS yes", change 'yes' to 'no'. Save
  1. Restart sshd
systemctl restart sshd
  1. Install virt-install
yum -y install virt-install
  1. Begin the installation of the Arno release
Download your preferred ISO from the OPNFV dowloads page and follow the associated installation instructions.

Remote management

Remote access

Firewall rules should include

Lights-out Management:

Linux Foundation - VPN service for accessing Lights-Out Management (LOM) infrastructure for the UCS-M hardware

  1. amaged@cisco.com
  2. cogibbs@cisco.com
  3. daniel.smith@ericsson.com
  4. dradez@redhat.com
  5. fatih.degirmenci@ericsson.com
  6. fbrockne@cisco.com
  7. jonas.bjurel@ericsson.com
  8. jose.lausuch@ericsson.com
  9. joseph.gasparakis@intel.com
  10. morgan.richomme@orange.com
  11. pbandzi@cisco.com
  12. phladky@cisco.com
  13. stefan.k.berg@ericsson.com
  14. szilard.cserey@ericsson.com
  15. trozet@redhat.com

Networking

Test-bed network

Network Interfaces

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

Controller node bridge topology overview

images/bridge1.png

compute node bridge topology overview

images/bridge2.png

Architecture

** Network Diagram **

The Pharos architecture may be described as follow: Figure 1: Standard Deployment Environment

images/opnfv-pharos-diagram-v01.jpg

Figure 1: Standard Deployment Environment

Sample Network Drawings

Files for documenting lab network layout. These were contributed as Visio VSDX format compressed as a ZIP file. Here is a sample of what the visio looks like.

Download the visio zip file here: opnfv-example-lab-diagram.vsdx.zip

images/opnfv-example-lab-diagram.png
Authors:Trevor Cooper (Intel)
Version:1.0

Documentation tracking

Revision: b221fb1e3545a8f9329ffb559ba17fcce15da03f

Build date: Fri Sep 11 09:09:15 UTC 2015