Resources from heat template
TODO: update for Nov 2017 R1
We have setup an instance of ONAP based on "vanilla" Openstack (Ocata). Similarly to Resources and Sizing on Rackspace I would like to have a space for vanilla Openstack installs. The table below is generated by a little script (see attachment) based on the flavors used in our setup and the onap_openstack.yaml file.
...
Limit | |
|---|---|
| Injected File Content Bytes | 10240 |
| Metadata Items | 128 |
| Server Group Members | 10 |
| Server Groups | 10 |
| RAM (MB) | 128000 |
| Key Pairs | 100 |
| Length of Injected File Path | 255 |
| Instances | 20 |
| Injected Files | 5 |
| VCPUs | 64 |
| Per Volume Size (GiB) | -1 |
| Total Size of Volumes and Snapshots (GiB) | 1000 |
| Backup Size (GiB) | 1000 |
| Volume Snapshots | 10 |
| Volumes | 15 |
| Backups | 10 |
Physical infrastructure
One controller node, two compute nodes (Blades in a pureflex center)
After we discovered a performance problem on our first lab infrastructure, we tried to setup Openstack & ONAP on a bare metal server in Softlayer. This was the break through which let a lot of issues we had before simply disappear. Nevertheless, some of the experience made it into a JIRA entry to improve the way the VMs and/or containers are started.
| Role | CPU Type | cores | Disk (Gb) | RAM (Gb) | Remarks |
| Compute | Dual processor E5 2690 v4 | 56 | 600GB SAS (RAID) | 128 | |
| Compute | Dual processor E5 2690 v4 | 56 | 600GB SAS (RAID) | 128 | |
| Controller | 4 CPU (VM) | 100 | 12 | Virtual instance on a host distinct from compute nodes |
The disk size is a bit small, we decreased the disk sizes in the big flavors (a see could see that from 160GB requested disk size only ~6GB were used after install). We will change compute nodes shortly to ones with more disk space.specs: <tbd>
Other observations
A few observations we made during the setup of on vanilla Openstack.
...