Hi, I am happy to announce we finally submitted the final changes for PDF/IDF support in Fuel. We have been using PDF for a few weeks to describe most of the hardware parameters (IPMI credentials for cluster nodes, network VLANs etc.), but we were lacking support for dynamic configuration of interface allocation (e.g. mgmt VLAN was always assigned to the Xth NIC, tagged; public was always assigned to Yth NIC etc.).
For those of you who have securedlab access, the IDF change, adding some new Fuel-specific params for lf-pod2/arm-pod5 is at [1]. For those who don't, we also provide a sample IDF in Fuel@OPNFV, which is basically a copy of lf-pod2's IDF. The Fuel code consuming the new data is at [2]. We can now model any arrangement of tagged/untagged, vlan or physical interface configuration. This means that soon after the release, we can start re-enabling all Fuel PODs that did not align with the lf-pod2/arm-pod5 hardcoded setups (ericsson-pod1, zte-pod1 etc.). To summarize, here are the PDF/IDF requirements for Fuel: - PDF (as per Pharos specification), including net_config section (which is not part of the spec yet, but it doesn't collide with it either - see sample [3], which is basically lf-pod2's PDF); - IDF - we don't depend on the shared section (yet), and the Fuel-specific section is quite lightweight and self-explanatory - see sample [4]; BR, Alex [1] https://gerrit.opnfv.org/gerrit/#/c/45587 [2] https://gerrit.opnfv.org/gerrit/#/c/45427 [3] https://github.com/opnfv/fuel/blob/master/mcp/config/labs/local/pod1.yaml [4] https://gerrit.opnfv.org/gerrit/#/c/45427/4/mcp/config/labs/local/idf-pod1.yaml _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
