Switch to use a container when invoking tripleo deploy

Registered by Alex Schultz on 2020-10-13

We added support to run heat-all either via a container or as a normal host process when we implemented the initial standalone framework. While the support was written into the code, we hadn't enabled it or tested it. We would like to switch to running the heat-all process in a container and work on dropping the openstach-heat-monolith packaging requirement from tripleoclient.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Medium
Drafter:
Alex Schultz
Direction:
Needs approval
Assignee:
None
Definition:
Discussion
Series goal:
Accepted for future
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

[W PTG] Deferred to the future. There doesn't appear to be a great reason to make the default switch. We have landed the fixes to the container execution so it works now.

Gerrit topic: https://review.opendev.org/#/q/topic:bp/switch-to-heat-all-container

Addressed by: https://review.opendev.org/757950
    Update heat container location

Addressed by: https://review.opendev.org/758231
    Fix heat container mounts

Addressed by: https://review.opendev.org/758232
    Switch to containerized heat-all

Addressed by: https://review.opendev.org/758234
    Add package check for heat-all

Addressed by: https://review.opendev.org/758246
    Fix acceptable podman container exist

Addressed by: https://review.opendev.org/758863
    Handle container launch

Addressed by: https://review.opendev.org/759137
    Add ability to specify heat container image

Addressed by: https://review.opendev.org/759140
    Add heat container image support

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.