summaryrefslogtreecommitdiffstats
path: root/config/pdf/idf-pod1.schema.yaml
AgeCommit message (Collapse)AuthorFilesLines
2018-12-11[fuel] IDF: Add idf.fuel.network.interface_mtuAlexandru Avadanii1-0/+2
Allow configuring cluster-level jumbo frames via IDF. All virtual PODs default to using jumbo frames, while baremetal PODs will keep using 1500 until we confirm all switches are properly configured. While at it, update net_macros to configure MTU for VLAN interfaces too. JIRA: FUEL-336 Change-Id: Id6c7ec9377b15d53e69c8cbb16fa469b52ab7e3a Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-08-13Complete osa and add kubespray to the idf schemaManuel Buil1-1/+21
Modify idf of lf pod4 to aoid -1 from Jenkins Change-Id: I4fbac6ed2859e79aeef61b070498833b182f2b5d Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-08-08[idf.fuel] Add jumpserver.trunks for mgmtAlexandru Avadanii1-0/+7
Extend IDF schema for Fuel installer section to allow a new param, useful when jumpserver networks should be trunked for infra VMs. JIRA: FUEL-338 Change-Id: Ifda18ea017c069e29d25d48aea62a6b6b37e91b5 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-05-31[idf.fuel] Add NTP serversAlexandru Avadanii1-0/+4
Change-Id: Ib840995b085ec9d8a585d5cf2e2a84e5801875b6 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-03-06LF-POD4 PDF/IDFBlaisonneau David1-2/+5
PDF+IDF for LF POD4 inspired from securelab PDF and LF-pod2 XDFs. Change-Id: If7ee14efe5f279104a18d2a3281aa7b23bdf704a
2018-02-23[fuel] IDF: Add DPDK parameters supportCristina Pauna1-0/+55
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-05[IDF] Schema: Add OSA installer stubs6.0.0Alexandru Avadanii1-11/+21
While at it, order installers by name in IDF schema. Change-Id: I4bf1dd047a3f7a64b8bc928951fc18c4728a9b68 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-02-01[fuel] Allow MaaS timeout config via IDFAlexandru Avadanii1-0/+9
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/+8
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-24[IDF] Add IDF schema validation based on versionAlexandru Avadanii1-0/+113
- add basic structure for IDF schema validation; - fill in Fuel section; - add stub for Daisy section; - add stub for Compass section; - add stub for net_config; - enable IDF schema validation via `check-schema.sh`; - prepare for new IDF versions with different schemas, while allowing subsection schema reuse from IDF v0.1; - extend validate_schema.py for IDF; Change-Id: I59b1c9d857e9dee9e6ff9956e81b2ae6dc27a767 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>