Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Done
Description
During an offline discussion with eyang and arp, Eric suggested to maintain the source of the docker specific start images inside the main ozone branch (trunk) instead of the branch of the docker image.
With this approach the ozone-runner image can be a very lightweight image and the entrypoint logic can be versioned together with the ozone itself.
An other use case is a container creation script. Recently we documented that hadoop-runner/ozone-runner/ozone images are not for production (for example because they contain development tools).
We can create a helper tool (similar what Spark provides) to create Ozone container images from any production ready base image. But this tool requires the existence of the scripts inside the distribution.
(ps: I think sooner or later the functionality of envtoconf.py can be added to the OzoneConfiguration java class and we can parse the configuration values directly from environment variables.
In this patch I copied the required scripts to the ozone source tree and the new ozone-runner image (HDDS-1634) is designed to use it from this specific location.
Attachments
Issue Links
- links to
