This is an old revision of the document!
Work environment for Bootstrap/Get-started
Note: The below is a first draft cut at a work environment for Bootstrap/Get-started (BGS).
BGS is to deploy to both bare metal as well as to a virtual environment. This requires a physical server environment for BGS.
Development Environment Layout
Assumption is that a total of 5 PODs is required:
BGS targets a deployment with HA/cluster support. As a result, the following POD configuration is assumed:
3 x Control node (for HA/clustered setup of OpenStack and OpenDaylight)
2 x Compute node (to bring up/run VNFs)
1 x Jump Server/Landing Server in which the installer runs in a VM (FUEL)
Total: A total of 35 servers (5 PODs with 7 Servers each) is required.
Server configuration
Typical server configuration (same server for all components of the POD assumed for reasons of simplicity)
Server:
CPU: Intel Xeon E5-2600 (or similar)
Disk: 6 x 500G-3T (leave some room for experiments)
Virtual ISO boot capabilities or a separate PXE boot server (DHCP/tftp or Cobbler)
Access to console ports/lights-out-management through management tool and/or serial console server
Lights-out-management/Out-of-band management for power on/off/reset
Memory: >= 32G RAM (Minimum)
I/O: 4 x 1G Control Nics, 2 x 10/40G data NICS (at least for compute nodes for testing)
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 10G/40G for data network (redundancy, NIC bonding, High bandwidth testing)
Switch:
TOR switch should support 1G/10G/40G links (either 4 of them or VLAN isolated to support 4 networks)
Uplink from the Jump server to Internet must be 1G or better.
Public IP address Pool per pod (8)
Private address pool per pod 3 x /24 subnets (either not shared or vlan isolated)
Additional requirements (if servers are offered as MaaS):
Example Server