tacker requires conductor service in pike

Bug #1710874 reported by Eduardo Gonzalez on 2017-08-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Undecided
Eduardo Gonzalez
kolla-ansible
Undecided
Eduardo Gonzalez
openstack-ansible
Low
Unassigned
puppet-tacker
High
Tim Rozet
tripleo
High
Tim Rozet

Bug Description

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

Changed in kolla:
assignee: nobody → Eduardo Gonzalez (egonzalez90)
Changed in kolla:
status: New → In Progress
Changed in kolla-ansible:
status: New → In Progress

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

Changed in kolla:
status: In Progress → Fix Released

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

Changed in kolla-ansible:
status: In Progress → Fix Released
summary: - tacker broken in pike, need conductor service
+ tacker requires conductor service in pike
description: updated
Tim Rozet (trozet) on 2017-08-23
Changed in tripleo:
assignee: nobody → Tim Rozet (trozet)
Changed in puppet-tacker:
assignee: nobody → Tim Rozet (trozet)
Changed in tripleo:
milestone: none → queens-1
status: New → Triaged
importance: Undecided → High
Changed in puppet-tacker:
importance: Undecided → High
status: New → Triaged

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

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

Changed in openstack-ansible:
status: New → Confirmed
importance: Undecided → Low
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Changed in tripleo:
milestone: stein-2 → stein-3
Changed in tripleo:
milestone: stein-3 → stein-rc1
Changed in tripleo:
milestone: stein-rc1 → train-1
Changed in tripleo:
milestone: train-1 → train-2
Changed in tripleo:
milestone: train-2 → train-3
Changed in tripleo:
milestone: train-3 → ussuri-1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers