[fdio] Bump compute RAM defaults for virtual PODs 09/67809/1
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Wed, 8 May 2019 20:17:23 +0000 (22:17 +0200)
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Wed, 8 May 2019 23:36:45 +0000 (23:36 +0000)
commit6d37926e32dcd89ef999cedf9adcb13cbf717964
tree4109bb3ab19ccd2d9aca901605daa5a19935a019
parentbb38e087e70dd00575e441e375b1be2a41d4c657
[fdio] Bump compute RAM defaults for virtual PODs

Hugepage count has been recently bumped for virtual PODs via IDF
changes in Pharos, so align our FDio scenarios with the new RAM
requirements.

While at it, fix wrong pod_config template evaluation by moving it
after the templated scenario files are expanded, since pod_config
relies on scenario node definition.

Also, configure VPP to use decimal interface names by default to
align with Pharos macro for the VPP interface name string.

Change-Id: Ib3a89c294a3a2755567fdbe07e3be2b8ca1a5714
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
(cherry picked from commit b381277ae274473ae4e05a1aa9dd171dbab461d6)
mcp/config/scenario/os-nosdn-fdio-ha.yaml
mcp/config/scenario/os-nosdn-fdio-noha.yaml
mcp/patches/salt-formula-linux/0002-network-Bring-in-basic-VPP-support.patch
mcp/reclass/classes/cluster/mcp-common-noha/openstack_compute_pdf.yml.j2
mcp/reclass/classes/cluster/mcp-common-noha/openstack_gateway_pdf.yml.j2
mcp/scripts/lib_template.sh