Wiki

This is an effort to setup a basic functional assessment platform (a learning "academy") based upon OPNFV, installed as a single node (e.g. a laptop with lots of memory) or multi-node environment. This will provide a means to learn, analyze, and further develop:

• the OPNFV install process, to find where/how we need to augment it for additional components (e.g. Congress)
• the basic mechanisms supported by OPNFV components for VNF and service configuration
• the mechanisms supported by the additional components for configuration policy management
• use cases, demos, and techniques supporting the Copper scope

See Joid install procedure for the basic install, and additional notes.

See Congress install procedure for installation of OpenStack Congress in an LXC container on the JOID-based controller node.

See Congress test procedures for notes on testing Congress.

The hardware used in this includes:

• 3 Intel NUC i7 (NUC5i7RYH), each with 16GB RAM, 1TB HDD, 250MB SSD
  • The diagram below shows three NUCs used for a single non-HA "POD", i.e. jumphost, controller, and compute node hosts, with a single NIC on jumphost and compute nodes, two NICs on controller node (onboard ethernet, USB ethernet adapter)
• a router/gateway that isolates the OPNFV private network (single subnet) from the other LAN segments or the Internet, and any pesky DHCP servers that might be there
  • the private network can use any subnet; 192.168.10.0/24 is used below and in the procedures linked above

(Link to Powerpoint source of the diagram above)

See Foreman install procedure, install verification procedure, and additional notes.

The hardware used in this includes:

• 3 Intel NUC i7 (NUC5i7RYH), each with 16GB RAM, 1TB HDD, 250MB SSD
  • The diagram below shows three NUCs used for a single non-HA "POD", i.e. jumphost, controller, and compute node hosts.
  • Note: the single ethernet port on the NUCs can be augmented thru USB-NIC adapters using the 4 USB ports
• a router/gateway that isolates the OPNFV private network (single subnet) from the other LAN segments or the Internet, and any pesky DHCP servers that might be there
  • the private network can use any subnet; 192.168.1.0/24 is used below and in the procedures linked above

(Link to Powerpoint source of the diagram above)

For the record, you can review the (mostly failed) earlier attempts …