This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
copper:academy [2015/12/04 21:34] Bryan Sullivan |
copper:academy [2016/03/02 01:00] (current) Bryan Sullivan |
||
|---|---|---|---|
| Line 6: | Line 6: | ||
| * the mechanisms supported by the additional components for configuration policy management | * the mechanisms supported by the additional components for configuration policy management | ||
| * use cases, demos, and techniques supporting the Copper scope | * use cases, demos, and techniques supporting the Copper scope | ||
| + | |||
| + | === Multi-Node Apex-based install on 3 bare metal nodes (non-HA) === | ||
| + | |||
| + | This is a work in progress. The target system is as described for JOID below. | ||
| + | |||
| + | See [[https://wiki.opnfv.org/copper/academy/apex|Apex install procedure]] for the basic install. | ||
| === Multi-Node JOID-based install on 3 bare metal nodes (non-HA) === | === Multi-Node JOID-based install on 3 bare metal nodes (non-HA) === | ||
| - | See [[https://wiki.opnfv.org/copper/academy/joid|Joid install procedure]] | + | As shown in the diagram below, an internet connection is assumed to be available. In some cases (e.g. hackfests etc) you may need to connect thru a wifi network. Because it may not be obvious how to do this with a fixed configuration, see [[https://wiki.opnfv.org/copper/academy/wifi|getting your POD connected to the internet via wifi]]. |
| + | |||
| + | See [[https://wiki.opnfv.org/copper/academy/joid|Joid install procedure]] for the basic install, and [[https://wiki.opnfv.org/copper/academy/joid/notes|additional notes]]. | ||
| + | |||
| + | See [[https://wiki.opnfv.org/copper/academy/joid/congress|Congress install procedure]] for installation of OpenStack Congress in an LXC container on the JOID-based controller node. | ||
| + | |||
| + | See [[https://wiki.opnfv.org/copper/academy/congress/test|Congress test procedures]] for notes on testing Congress. | ||
| The hardware used in this includes: | The hardware used in this includes: | ||
| * 3 Intel NUC i7 (NUC5i7RYH), each with 16GB RAM, 1TB HDD, 250MB SSD | * 3 Intel NUC i7 (NUC5i7RYH), each with 16GB RAM, 1TB HDD, 250MB SSD | ||
| - | * The diagram below shows the initial layout in which three of the NUCs are used for a single non-HA "POD", i.e. jumphost, controller, and compute node hosts. | + | * 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) |
| - | * Single NIC on jumphost ad compute node. 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 | * 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 | * the private network can use any subnet; 192.168.10.0/24 is used below and in the procedures linked above | ||
| Line 29: | Line 40: | ||
| The hardware used in this includes: | The hardware used in this includes: | ||
| * 3 Intel NUC i7 (NUC5i7RYH), each with 16GB RAM, 1TB HDD, 250MB SSD | * 3 Intel NUC i7 (NUC5i7RYH), each with 16GB RAM, 1TB HDD, 250MB SSD | ||
| - | * The diagram below shows the initial layout in which three of the NUCs are used for a single non-HA "POD", i.e. jumphost, controller, and compute node hosts. | + | * 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 | * 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 | * 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 | ||