Remove feature installation profiles from the installer #4332
Labels
🗡️ System Decoupling
Concerns NFR activities to make DDF more robust to work with.
🌊Impacts Downstream
📈 Improvement
📦 Fix: Distribution
Refactoring task that involves fixing features and the distribution.
wontfix
Description
The different profiles in the installer are ambiguous and not heavily used. Instead of making these profiles an option in the installer, we can install a default profile on boot. This would provide the following benefits:
The system would take a bit longer to boot but the overall installation time should improve greatly since karaf will optimize for all the bundles being started at once. Some manually testing I’ve done is showing about a 40 sec speedup.
Itests currently install individual apps instead of one of these profiles. This change would make our itests more consistent with a production environment.
There are several places where we use the word “profile” in ddf, each meaning something different. Removing one of these definitions would add clarity.
This will allow us to remove the profile & app features, making our features much more flat and well defined. It would also allows us to uninstall features again.
Once the system has booted, you can reach other areas of the system without going through the installer, which will improve development time.
Expected behavior:
The "profile selection" stage of the installer is removed and the features composing the profile feature are added to the bootFeature section.
Version
Latest (2.14.0-SNAPSHOT)
Additional Information
The text was updated successfully, but these errors were encountered: