User Tools

Site Tools


pharos:pharos_specification

Pharos Specification¶

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:

  • A secure, scalable, standard and HA environment
  • Supports the full Arno deployment lifecycle (this requires a bare metal environment)
  • Supports functional and performance testing of the Arno release
  • Provides mechanisms and procedures for secure remote access to the test environment

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¶

  • One CentOS 7 jump server on which the virtualized Openstack/OPNFV installer runs
  • In the Arno release you may select a deployment toolchain to deploy from the jump server from the Foreman and Fuel ISO images.
  • 5 compute / controller nodes (BGS requires 5 nodes)
  • A configured network topology allowing for LOM, Admin, Public, Private, and Storage Networks
  • Remote access as defined by the Jenkins slave configuration guide http://artifacts.opnfv.org/arno.2015.1.0/docs/opnfv-jenkins-slave-connection.arno.2015.1.0.pdf

Hardware requirements¶

Servers

CPU:

  • Intel Xeon E5-2600v2 Series (Ivy Bridge and newer, or similar)

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.

  • Disks: 2 x 1TB + 1 x 100GB SSD
  • The first 1TB HDD should be used for OS & additional software/tool installation
  • The second 1TB HDD configured for CEPH object storage
  • Finally, the 100GB SSD should be used as the CEPH journal
  • Performance testing requires a mix of compute nodes that have CEPH(swift+Cinder) and without CEPH storage
  • Virtual ISO boot capabilities or a separate PXE boot server (DHCP/tftp or Cobbler)

Memory:

  • 32G RAM Minimum

Power Supply Single

  • Single power supply acceptable (redundant power not required/nice to have)

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¶

  • Remote access is required for â¦
    1. Developers to access deploy/test environments (credentials to be issued per POD / user)
    2. Connection of each environment to Jenkins master hosted by Linux Foundation for automated deployment and test
  • OpenVPN is generally used for remote however community hosted labs may vary due to company security rules
  • POD access rules / restrictions â¦
    • Refer to individual test-bed as each company may have different access rules and acceptable usage policies
  • Basic requirement is for SSH sessions to be established (initially on jump server)
  • Majority of packages installed on a system (tools or applications) will be pulled from an external repo so this scenario must be accomodated.

Firewall rules should include

  • SSH sessions
  • Jenkins sessions

Lights-out Management:

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

  • People with admin access to LF infrastructure:

The people who require VPN access must have a valid PGP key bearing a valid signature from one of these three people. When issuing OpenVPN credentials, LF will be sending TLS certificates and 2-factor authentication tokens, encrypted to each recipient’s PGP key.

Networking¶

Test-bed network¶

  • 24 or 48 Port TOR Switch
  • NICS - 1GE, 10GE - per server can be on-board or 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
  • Lights-out network can share with Admin/Management

Network Interfaces¶

  • Option I: 4x1G Control, 2x40G Data, 48 Port Switch
    • 1 x 1G for ILMI (Lights out Management)
    • 1 x 1G for Admin/PXE boot
    • 1 x 1G for control Plane connectivity
    • 1 x 1G for storage
    • 2 x 40G (or 10G) for data network (redundancy, NIC bonding, High bandwidth testing)
  • Option II: 1x1G Control, 2x 40G (or 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, 2x40G 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 IPMI
    • 1 x 1G for Admin/PXE boot
    • 2 x 10G for control plane connectivity/Storage
    • 2 x 40G (or 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

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
pharos/pharos_specification.txt · Last modified: 2015/06/03 13:44 by Trevor Cooper