ONAP on Kubernetes
|UNH laas Lab||10.10.30.157||CentOS 7.3.1611||Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz||117G||802G|
vFW blitz daily at 1200EDT until Kubecon - https://wiki.onap.org/display/DW/Vetted+vFirewall+Demo+-+Full+draft+how-to+for+F2F+and+ReadTheDocs
OOM Discussion list (post any issues here to notify and get responses from OOM personnel like the current) - https://lists.onap.org/pipermail/onap-discuss/2017-September/004616.html
In general most of the sync issues are because of the long lead time getting docker images from ONAP Nexus3 - this can be fixed by prewarming your own docker repo or running the deployment a 2nd time - There is a JIRA on running a script across the yamls to extract out the docker images and load them before bringing up the containers - see https://jira.onap.org/browse/OOM-328
|Full deploy||in progress|
clear iptables rules to deploy rancher server and agent on one machine ( solved: centos issue )
rancher can't bring up kubernetes. all pods in kube-system stay at pending state ( blocker )
|Partial deploy||in progress|
ONAP on OpenStack
|Huawei Shanghai Lab||huawei-pod4||ubuntu|
?jumphost?Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz?48?
?host1?Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz?48?
?host2?Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz?48?
?host3?Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz?48?
?host4?Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz?48?
?host5?Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz?48?
1.Set up Openstack
Deploy os-nosdn-nofeature scenario using Euphrates Compass4nfv?Containerized Compass
2. ONAP Installation in Vanilla OpenStack
|Full deploy||in progress|
Heat Template and env parameters: https://nexus.onap.org/content/sites/raw/org.onap.demo/heat/ONAP/1.1.0-SNAPSHOT/
Instance active but ONAP services not running probably due to false settings in onap_openstack.env
Remote access is required for …
- Developers to access deploy/test environments (credentials to be issued per POD / user) at 100Mbps upload and download speed
OpenVPN is generally used for remote however community hosted labs may vary due to company security rules. Please refer to individual lab documentation/wiki page as each company may have different access rules and policies.
- SSH sessions to be established (initially on the jump server)
- Packages to be installed on a system by pulling from an external repo.
Firewall rules accommodate:
- SSH sessions
Lights-out management network requirements:
- Out-of-band management for power on/off/reset and bare-metal provisioning
- Access to server is through a lights-out-management tool and/or a serial console
- Refer to applicable light-out management information from server manufacturer