It seems this feature was not widely adopted so the current maintainers would like to remove it. We have a proposed patch [1] to remove it from the main branch so it won't be in the TripleO release which accompanies Zed. It's presently in the release which accompanies Wallaby. Note that TripleO is using the independent release model [2]. What is the "Derived Parameters" feature? NFV and HCI overclouds require system tuning. There are formulas which output tuning parameters based on hardware. These parameters may then be provided as input to TripleO to deploy a tuned overcloud. There is an additional method of system tuning called “derived parameters” where TripleO uses inspected hardware data as input and automatically sets tuning parameters [3]. Removing this feature shouldn't block anyone since they can still deploy a tuned overcloud by providing standard parameters. There's also a docs patch [4] explaining how to migrate away from derived to standard parameters. John [1] https://review.opendev.org/q/topic:derive-parameters-cleanup [2] https://review.opendev.org/c/openstack/tripleo-specs/+/801512 [3] https://specs.openstack.org/openstack/tripleo-specs/specs/pike/tripleo-derive-parameters.html [4] https://review.opendev.org/c/openstack/tripleo-docs/+/854443