-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
None
-
Policy Dublin 2 1/25-2/10, Policy Dublin 3 2/12-2/26, Policy Dublin 4 2/28-3/14, Policy Dublin 5 3/15-4/04
There is only one PDP-D image currently being generated.
The image is generic as it should be able to run any PDP-D based applications.
Customization scripts are run when the container is instantiated to give it a "Control Loop" flavoring. These scripts obtain the drools-applications package (currently for control loops) and goes on with the installation of anything needed to run control loops. Another drawback is that the version of the drools applications installed are the ones that match the base drools PDP.
We want to lift these constraints, and would want an image, pre-set with control loop flavoring. This would reduce the container instantiation times, and eliminate the version dependencies.
The image ideally should "extend" the generic PDP-D image produced by the policy/drools-pdp builds.
1.
|
basic version independent image | Closed | jhh | |
2.
|
supporting environment variables in properties | Closed | jhh | |
3.
|
Decouple nexus server reconfiguration from installation | Closed | jhh | |
4.
|
Use environment variables in configuration files PDP-D core | Closed | jhh | |
5.
|
Support well known topic names and environment actual topic names | Closed | jhh | |
6.
|
ci-management for drools applications image | Closed | jhh | |
7.
|
Use environment variables in configuration files PDP-D APPS | Closed | jhh | |
8.
|
new installation/environment variables in docker project | Closed | jhh | |
9.
|
new installation/environment variables in OOM project | Closed | jhh | |
10.
|
cook control loop software into the image | Closed | jhh | |
11.
|
oom use pdp-d cl image | Closed | jhh |