tacker requires conductor service in pike

[Eduardo Gonzalez]

Tacker implemented new tacker-conductor service in pike, it is not backward compatible and need this service to communicate with mistral for VIM monitoring.

Without conductor service connecting with mistral, VIM creation will stuck forever in creating state and not being able to do any other action/resource creation.

Also for make tacker HA, barbican should be used for sharing vim fernet keys or mount /etc/tacker/fernet_keys in a shared storage with all tacker-server instances.

From release notes:

The component tacker-conductor is introduced for tacker mistral actions to execute policy actions on tacker side. The conductor is listening on TACKER_CONDUCTOR queue ( in the rabbitmq terms). Mistral actions RPC calls the conductor.

Vim monitoring via mistral workflow is used to replace old in-place vim monitoring in tacker server. Mistral is an integral part of tacker MANO system. To make full use of it, and make the tacker server scale well, the feature creates a mistral workflow and execute it. The mistral workflow action task then monitors ( currently, pings) the vim, and notifies the tacker conductor to update the VIM status.

This means, tacker now requires a new conductor service and also have a hard dependency with mistral.

Refs:

https://docs.openstack.org/tacker/latest/contributor/tacker_conductor.html
https://docs.openstack.org/releasenotes/tacker/unreleased.html (Pike)
https://specs.openstack.org/openstack/tacker-specs/specs/pike/encryption-with-barbican.html

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/477494
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=7b2dea5506375cb868d6acb6a99b0aca916fad6c
Submitter: Jenkins
Branch: master

commit 7b2dea5506375cb868d6acb6a99b0aca916fad6c
Author: Eduardo Gonzalez <email address hidden>
Date: Mon Jun 26 13:05:24 2017 +0200

    Implement tacker-conductor image, rework all tacker

    Tacker is broken in pike without conductor images.
    Conductor is needed to communicate with mistral for
    VIM monitoring
    This change rework tacker image to allow tacker-conductor
    service image.
    Split tacker global image into tacker-server and tacker-conductor.

    Closes-Bug: #1710874
    Change-Id: I52778e86e4f2c297ead8d4b09983e5e38ca88c70

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/477517
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=ecc022177c7569b4c2066d64a93d47d72bfa7bdf
Submitter: Jenkins
Branch: master

commit ecc022177c7569b4c2066d64a93d47d72bfa7bdf
Author: Eduardo Gonzalez <email address hidden>
Date: Mon Jun 26 14:35:05 2017 +0200

    Fix missing tacker-conductor service

    Tacker has included a new conductor service
    to manage mistral workflows for VIM monitoring.

    Without conductor, Tacker cannot create VIMs.

    This change reworks tacker to include tacker-conductor
    service.

    Depends-On: I52778e86e4f2c297ead8d4b09983e5e38ca88c70
    Closes-Bug: #1710874
    Change-Id: I6901e919887551bedc9dba8983ac904e8c48c9ce

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla-ansible 5.0.0.0rc1 release candidate.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla 5.0.0.0rc1 release candidate.

[Mark Goddard (mgoddard)]

This bug is marked incomplete for tripleo. Please remove the milestone to stop the spam with each RC :)

[Takashi Kajinami (kajinamit)]

This was fixed by https://review.opendev.org/c/openstack/puppet-tacker/+/799553 .

Though the change was made during Xena cycle. I'm wondering whether anybody is really interested in using this module. If no then we might want to just drop the module.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/openstack-ansible-os_tacker/+/861870

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/openstack-ansible-os_tacker/+/861870
Committed: https://opendev.org/openstack/openstack-ansible-os_tacker/commit/a2800f0d284eaf0b1749dc761d3ecb388fed3bfd
Submitter: "Zuul (22348)"
Branch: master

commit a2800f0d284eaf0b1749dc761d3ecb388fed3bfd
Author: Dmitriy Rabotyagov <email address hidden>
Date: Wed Oct 19 12:52:03 2022 +0200

    Add deployment of tacker-scheduler

    There's a long-standing bug from 2017 that tacker requires scheduler
    service to run. However it seemed no real interest to tacker among OSA
    users. Nevertheless it's better late then never fixing it.

    Change-Id: I70264ef5ffd6ebb851e4d3c4c86c28ea222f7139
    Closes-Bug: #1710874