https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/RELENG-59 releng <p>Change the way we install features for CSIT. We are not going to use featuresBoot any longer and install from the karaf shell:</p> <p><a href="https://lists.opendaylight.org/pipermail/release/2017-June/011157.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/release/2017-June/011157.html</a></p> <p>Operating System: All<br/> Platform: All</p> RELENG-59

Update CSIT: Remove featuresBoot and install from karaf shell

Bug Open Unresolved Unassigned A H Wed, 7 Jun 2017 16:02:28 +0000 Wed, 28 Feb 2018 15:53:25 +0000 unspecified Jenkins Job Builder 0 5 <p>Configuration management tools for ODL, like ansible-opendaylight and puppet-opendaylight, currently use the featuresBoot line to configure which features are installed. This logic is consumed by major users, like OPNFV. It's critical that we smoothly transition that config logic to use whatever the new method is. I have a Int/Pack Trello tacking this here:</p> <p><a href="https://trello.com/c/JsVVVDXw/502-update-puppetansible-opendaylight-feature-install-logic-to-work-with-changed-karaf-4-cfg-file" class="external-link" target="_blank" rel="nofollow noopener">https://trello.com/c/JsVVVDXw/502-update-puppetansible-opendaylight-feature-install-logic-to-work-with-changed-karaf-4-cfg-file</a></p> <p>During Developer Design Forum we were discussing this, and we have decided that the installation scripts shall stay in Releng/Builder for Nitrogen cycle.</p> <p>one main reason this option was discussed was because if features are there<br/> in featuresBoot and karaf is started, then if a user uses the command<br/> line to install other features it could cause bundles to be refreshed in<br/> some unknown and/or unpredictable way.</p> <p>My main concern about removing featuresBoot is that config management tools are much better at working with files than interactive sessions. They can check the status of a file and see if it needs to be updated, or see if it has changed and do some action. They can also work with the file before ODL is started (after an RPM install, before `sudo systemctl start opendaylight`). It's not clear how well we can do this with only interactive commands. After OPNFV Summit I can try to put together a PoC of how we could migrate config mgmt tools to be interactive, see how horrible it actually turns out to be.</p> <p>My other concern is that this seems like a bug in Karaf. Both install methods should use the same feature resolver, or generally if both are provided, it should be possible to mix them.</p> <p>I have to agree with Daniel here, if both install methods are not compatible anyomore it sounds like a karaf regression, we should at least reach the upstream community to understand better why this change if it is not a bug.</p> <p>So far it seem like featuresBoot keeps working in Karaf 4, at least when there are no feature:install commands executed at runtime.</p> <p>There may be some CSIT which need this improvement, but most of CSIT jobs are fine with the current releng/builder scripts.</p> Development External issue ID 8627 External issue URL Issue Type ODL SR Target Milestone Rank 0|i01man: