Docker resource is disabled by default for Heat, current Blueprint is required to enable this resource for using it by Murano without additional deployment workarounds.
MOX 2.3 already contains a bunch of Murano Docker-based applications. These apps are being forward-ported to MOX 3.0. At this moment these applications are not available in MOS. To avoid further differences between MOS and MOX, we’re going to add Docker-based apps to MOS 6.1.
Currently docker resource is placed in Heat contrib directory and can not be used without installation and restarting Heat services. These changes adds ability to install docker resource on deployment step, so it makes docker resource available for Heat on first launch.
It does not require any changes in Data Base.
No API changes.
Several new packages should be installed (heat_docker and docker requirements)
User should see available docker resource in output of command:
Requires installation of addtional packages and small changes in manifests, which need to configure the right path to docker files.
- Build packages for docker requirements.
- Build package for Heat docker resource.
- Update fuel manifests to allow install packages above.
Changes about new added resource.