summaryrefslogtreecommitdiffstats
path: root/labs
AgeCommit message (Collapse)AuthorFilesLines
2018-08-17Merge "Add mask to the oob networks"Alexandru Avadanii23-0/+23
2018-08-17Update the pdf/idf for ericsson pod2Manuel Buil2-21/+217
Change-Id: I9b5db404cde0414f34621cf12819fd3edfcf0414 Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-08-17Add mask to the oob networksManuel Buil23-0/+23
It is not needed but it helps a lot to the xci parser Change-Id: I6943b21cd2aca2036783430cde03fb8d3b567f3b Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-08-13Complete osa and add kubespray to the idf schemaManuel Buil1-0/+37
Modify idf of lf pod4 to aoid -1 from Jenkins Change-Id: I4fbac6ed2859e79aeef61b070498833b182f2b5d Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-07-27[arm-pod9] Increase fuel maas timeoutsGuillermo Herrero1-2/+2
Change-Id: I0bf27ddc06b5c6efa64b41a32573bf09990c95b5 Signed-off-by: Guillermo Herrero <guillermo.herrero@enea.com>
2018-06-28[arm-virtual2] Add ip-range to avoid IP conflictsAlexandru Avadanii1-0/+2
Change-Id: Ib7858d57d3e0cc1a428905a63c4d342be260a673 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-06-20[unh-pod1] Increase MaaS timeoutsAlexandru Avadanii1-2/+2
Some targets (especially 96-cores computes) in UNH POD1 take longer than the average to commission/deploy, so adjust the timeouts accordingly. Change-Id: I9bf0b2ecccb3e8437cc5659688a84ee5ad0b5b87 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-06-18unh-pod1: restrict public ip range to avoid conflictPaul Vaduva1-0/+2
Change-Id: I7644fe6eedc71b4e67ea6b6d112a06685ea26602 Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
2018-06-12Merge "Adding reclass sections to idf-pod1 file"Alexandru Avadanii1-0/+28
2018-06-12Adding reclass sections to idf-pod1 filePaul Vaduva1-0/+28
reclass section is necessary to setup hugepages size to 2M per hugepage as the defaults are 1G which are not supported by thunderx. Plus adding ntp servers to unh-pod1 Change-Id: I9cd2a8105032035a519411b80f95675a997a1fbd Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
2018-06-08[idf.fuel] Add NTP for new virtual PODsAlexandru Avadanii7-0/+14
Change-Id: I6172e909c51e796b16f62f2d8e0cb0497306ce2a Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-06-08Merge "[PDF] Add arm-virtual2 PDF/IDF"Alexandru Avadanii2-0/+215
2018-06-08Merge "add ericsson vpod PDF"Alexandru Avadanii12-0/+1559
2018-06-04update ilo mac address after hw replacementmting1-1/+1
Change-Id: I9df2e117d8a2036c9555ddfe41d636b9e30910e8
2018-06-04Merge "[idf.fuel] Add NTP servers"Alexandru Avadanii6-0/+12
2018-05-31[idf.fuel] Add NTP serversAlexandru Avadanii6-0/+12
Change-Id: Ib840995b085ec9d8a585d5cf2e2a84e5801875b6 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-05-30Merge "IDF and PDF files for auto pod in unh lab"Guillermo Herrero2-0/+350
2018-05-30Merge "[IDF] arm-pod9: added as new idf and pdf"Guillermo Herrero2-0/+427
2018-05-30Merge "[IDF] arm-pod8: added as new idf and pdf"Guillermo Herrero2-0/+375
2018-05-25[IDF] arm-pod9: added as new idf and pdfGuillermo Herrero2-0/+427
Change-Id: I415eda9f493fcd70514d5f9be7d58b7b6d1cb88f Signed-off-by: Guillermo Herrero <guillermo.herrero@enea.com>
2018-05-25[IDF] arm-pod8: added as new idf and pdfGuillermo Herrero2-0/+375
Change-Id: I01c678b45fd182bef8a95bdf13054a36347e057b Signed-off-by: Guillermo Herrero <guillermo.herrero@enea.com>
2018-05-25IDF and PDF files for auto pod in unh labpava2-0/+350
Change-Id: Iad65abda66b772e8ed44c2257ebdb7cb48ecc6c1 Signed-off-by: joekidder <Joe.Kidder@enea.com> Signed-off-by: pava <Paul.Vaduva@enea.com>
2018-05-15add ericsson vpod PDFmting12-0/+1559
Change-Id: I20e70ec3264e807fb85585441d51752b13f5389d Signed-off-by: mting <dianfeng.du@ericsson.com>
2018-05-15[PDF] Add arm-virtual2 PDF/IDFAlexandru Avadanii2-0/+215
JIRA: FUEL-322 Change-Id: I3b136d6eebdaf0f09c772d2b994158af99cd8fea Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-04-30Merge "Okinawa Open Labratory(OOL) POD1 PDF/IDF"Julien2-0/+270
2018-04-24update idf file for zte-pod1zhihui wu1-1/+1
Change-Id: Iffed25c5e01aa9bf2a7b4a7103b07fb1c097d811 Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
2018-04-20Okinawa Open Labratory(OOL) POD1 PDF/IDFhhayashiool2-0/+270
Change-Id: I0980de9c2ff37654dbfd2d58002b9e61226cf749 Signed-off-by: Hideyasu Hayashi <hideyasu.hayashi@okinawaopenlabs.org>
2018-04-18[fuel] Parameterize tenant VLAN rangesAlexandru Avadanii7-7/+7
- 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-04-12JOID PDF-IDF support for intel-pod18agardner14-53/+96
More info in gerrit comments. Remove joid from all other idfs other than intel/pod18 add installer: ['apex', 'compass4nfv', 'daisy', 'fuel'] where missing Change-Id: I2afc415599070e210736c5fc304f7cb150f05029 Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-11[IDF] arm-pod6: Adjust CPU pinning variablesGuillermo Herrero1-5/+5
For non-dpdk scenarios we define as cpu config: 0-7 for OS 8-47 for nova For dpdk scenarios we define as cpu config: 0-7 for OS 8-11 for DPDK drivers and processes 12-47 for nova Change-Id: Ia9d7cfaee76f996993b94a52e1484752157a23cd Signed-off-by: Guillermo Herrero <guillermo.herrero@enea.com>
2018-03-29[IDF] zte-pod3: Remove vlan for tenant/externalAlex Yang1-2/+2
To deploy ovs_dpdk scenario by daisy. In this scenario, vlan configuration is not supported on tenant/external interface for now. Change-Id: I6e91bea92bde085079f4435fa72f20b5cef12ad3 Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
2018-03-23Merge "[IDF] arm-pod7: Configure hugepages and cpupinning variables for armpod7"Alexandru Avadanii1-0/+45
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-15[IDF] arm-pod5: Configure hugepages and cpupinning variables for armpod5Charalampos Kominos1-0/+26
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 JIRA: ARMBAND-364 Change-Id: Icc976e8511fed221b71a348afda3cbe4e0556b1a Signed-off-by: Charalampos Kominos <charalampos.kominos@enea.com>
2018-03-09[IDF] arm, lf, ericsson: Align IP ranges startAlexandru Avadanii5-1/+9
- 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-03-07[IDF, fuel] Add idf.net_config.*.ip-range supportAlexandru Avadanii1-0/+2
- labs: ericsson-pod1: Restrict management and public network IP ranges to exclude pre-existing infrastructe addresses; - fuel: Consume new ip-range network property in installer adapter; NOTE: For now, we only look at range start (and ignore end addr). JIRA: FUEL-351 Change-Id: If81d0214f896fd42dfd0855ae4cecb06335d2e00 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-03-06LF-POD4 PDF/IDFBlaisonneau David2-55/+132
PDF+IDF for LF POD4 inspired from securelab PDF and LF-pod2 XDFs. Change-Id: If7ee14efe5f279104a18d2a3281aa7b23bdf704a
2018-03-03[IDF] zte-pod1: Remove br-mgmtAlexandru Avadanii1-1/+1
All recent Fuel deploy attempts on zte-pod1 failed due to br-mgmt not being present (or up), although it is defined in IDF. Since this bridge is optional in the Fuel deployment process and mostly useful for manual debugging, let's remove it from idf.fuel. Change-Id: I130ec61427237f979f6a6212ca8c291ba203ef39 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-02-27[IDF] arm-pod6: Use 2M hugepages, 12 cores for novaAlexandru Avadanii1-4/+4
Change-Id: I03098ca3d4a90f6420cee64985c2853931a6a870 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-02-26[IDF] arm-pod6: Fix nova_cpu_pinning param exprAlexandru Avadanii1-2/+2
Constructs based on reclass interpolation (e.g. '${_param:x}') do not work when parameters are passed via reclass.storage templating, so change reclass interpolation syntax with classic YAML anchors. Change-Id: Ia974d45fc6a5869f4b30b31b947df088ea3aaf0c Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-02-23[fuel] IDF: Add DPDK parameters supportCristina Pauna1-1/+27
In order to enable DPDK for OVS scenarios in Armband, we need DPDK specific configuration to be parameterizable. The default DPDK configuration values will remain in Fuel repo and will be overriden with the values defined in IDF (only if present). Since hugepage config and CPU pinning also apply to non-DPDK scenarios, handle them together for 'common', respectively 'dpdk'. To keep things simple, we will reuse the format expected by Fuel's reclass model, so we can pass the whole config block as-is. - IDF schema: fuel: Add strict checking of new block's structure, while allowing the rvalues to be more or less freestyle; - arm-pod6 IDF: Add initial config block implementation; JIRA: ARMBAND-342 Change-Id: I9224f06bb6b9fb2387414eb2a1be35461c27fb99 Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
2018-02-15Merge "[PDF/IDF] LF-POD4"Trevor Bramwell2-0/+235
2018-02-14[IDF] LF-POD5Trevor Bramwell2-17/+19
Update networks for LF-POD5 since discovering there is a bug using non-/24 networks with Fuel, and to ensure there is no overlap with LF-POD4. Change-Id: Ie6eb6f12e8fd2831355e8bcec064e152cdc02f27 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-02-14[PDF/IDF] LF-POD4Trevor Bramwell2-0/+235
Add PDF and IDF for LF-POD4 Change-Id: Ie3e682e40f751b8f91340373fbcabd522d3686a8 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-02-01[fuel] Allow MaaS timeout config via IDFAlexandru Avadanii3-0/+12
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-02-01[IDF] lf-pod2: Add missing bridge, eth infoAlexandru Avadanii1-8/+12
Some information was lost while syncing from securedlab to pharos git repo, bring it back. Change-Id: I938f4c573234c7a9d55eb140ea02f3328373ae1d Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-01-28[fuel] Explicitly blacklist incompatible labsAlexandru Avadanii6-1/+42
Previously, we used to silently refuse to construct 'pod_config' for PODs missing mandatory PDF/IDF configuration; and instead generated an empty output YAML. Retire safety checks in Fuel IA and explicitly blacklist Fuel via new 'idf.installer' where appropiate. The following PODs do not yet support Fuel due to missing 'idf.fuel': - ericsson-pod2 - huawei-pod1 - intel-pod18 - nokia-pod1 - zte-pod2 - zte-pod3 Change-Id: Ief62d62f99a79187303e3f15b83030289e5efdcb Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-01-28[IDF] Add optional 'idf.installer' arrayAlexandru Avadanii4-0/+11
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-28Merge "[PDF] Update LF-POD5 IDF bridges, interfaces"Alexandru Avadanii1-6/+8
2018-01-28[PDF] Update LF-POD5 IDF bridges, interfacesTrevor Bramwell1-6/+8
Change-Id: Ia761d6cecc360dde729965e499a899ba4fbc6a32 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>