a3b7185cae
The role makes possible the re-use of code at the time of tagging the container images. However, the tagging varies whether we are deploying the services or upgrading. In upgrade tasks we use this role to tag the new container image (from the version we're upgrading to) into the image being used by pacemaker. So, the value for the container_image parameter is an image id, not an image name, which can't be pulled. This patch adds a new parameter, pull_image, which is set to true by default and will allow us to skip the image pulling for the upgrade_tasks case. Change-Id: I6fc69f122b3f48064ed831cd622a617a02a28e02 Related-Bug: #1814104 |
||
|---|---|---|
| .. | ||
| defaults | ||
| tasks | ||
| README.md | ||
README.md
tripleo-container-tag
An Ansible role to tag Pacemaker-managed containers.
Requirements
It requires Docker or Podman on the host, depending which container CLI is used.
Role variables
- container_image: -- Name of the container image to tag.
- container_image_latest: -- Name of the tag.
- container_cli: -- Name of the Container CLI tool (default to docker).
- pull_image: -- Pulling or not the image passed in container_image variable ( default to true).
Example Playbook
Sample playbook to call the role:
- name: Tag Pacemaker containers
hosts: all
roles:
- tripleo-container-tag vars: container_image: haproxy container_image_latest: pcmklatest container_cli: docker
License
Free software: Apache License (2.0)
Author Information
OpenStack TripleO team