summaryrefslogtreecommitdiffstats
path: root/labs/arm/idf-pod7.yaml
AgeCommit message (Collapse)AuthorFilesLines
2018-04-18[fuel] Parameterize tenant VLAN rangesAlexandru Avadanii1-1/+1
- IDF: convert all tenant VLANs to ranges; - IA: convert 'M-N' to 'M:N' for `opnfv_net_tenant_vlan`; Change-Id: Ic9211235281c81ba082d10806651c35116ba4c35 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-03-22[IDF] arm-pod7: Configure hugepages and cpupinning variables for armpod7Charalampos Kominos1-0/+45
For non-dpdk scenarios we define as cpu config: 0,1 for OS 2-7 for nova For dpdk scenarios we define as cpu config: 0,1 for OS, 2,3 for DPDK drivers and processes 4-7 for nova Dpdk config is also provided for the 3 thunderx nodes which currently serve as KVM nodes. The config is similar to the config above with cores 4-47 being used for nova. JIRA: ARMBAND-364 Change-Id: I761aa8e73935b7180f4f377841cc93c9d81cf4d7 Signed-off-by: Charalampos Kominos <charalampos.kominos@enea.com> Signed-off-by: Guillermo Herrero <guillermo.herrero@enea.com>
2018-03-09[IDF] arm, lf, ericsson: Align IP ranges startAlexandru Avadanii1-0/+2
- Enea lab has infra IPs in public networks, similar to ericsson-pod1 so start assigning public IPs from .100 onwards; - since most Fuel PODs have public (and mgmt) IPs starting at .100, align this across all PODs for uniformity; - align all mgmt networks start to .10; JIRA: ARMBAND-365 Change-Id: I9df4083c9e2e4c15da5ce6a2cb24df560808161a Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-02-01[fuel] Allow MaaS timeout config via IDFAlexandru Avadanii1-0/+4
MaaS timeouts should be configurable on per-POD basis, since nodes in some labs take longer to comission/deploy than our default values. IDF SCHEMA: - add new properties to Fuel IDF section; Change-Id: Ife5ff85faeae683a8c1781cae8b29f09c1f07b82 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-01-28[IDF] Add optional 'idf.installer' arrayAlexandru Avadanii1-0/+3
There is no easy way to determine automatically if a PDF/IDF set is compatible with a specific installer adapter. Most common incompatibilities are caused by: - installer adapters hardcode more network ports than nodes have defined in PDF; - installer adapters hardcode more nodes than PDF defines; Previous attempt at handling this dynamically (cd54edf) fails for recently added PODs, so let's handle this explicitly per-pod via a new optional IDF property, 'idf.installer'. If 'idf.installer' is defined, it will be used by `check-jinja2.sh` as a filter-in list of installer adapters to check against. The default (no 'idf.installer' present) is to check all IAs. Leverage the new property for: - arm-pod5: not enough network ports on computes for Compass, Joid; - arm-pod7: same as arm-pod5; - bii-pod1: no 'storage' network defined in IDF for Daisy; - zte-pod9: 3 cluster nodes are only supported by Daisy for now; SPEC changes: - net_config (previously mandatory for IDF version '0.1') is now mandatory only if 'idf.fuel' or 'idf.daisy' is defined; Fixes: cd54edf Change-Id: I706c05519e5491ad631069d7cc090e9c8bfd3011 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-01-19arm-pod7: add new PDF and IDF filesting wu1-0/+79
- net_config is moved to IDF file; - rename 'disk' to 'disks'; - add 'name: nicN' to interface; - add 'disk_rotation: 0' for ssd drivers; Change-Id: I1ea91a65abeb9db4f2f73f25ce51cd059b4b4753 Signed-off-by: ting wu <ting.wu@enea.com>