Deployment status checking generates tons of messages
Bug #1549219 reported by
Thomas Herve
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Triaged
|
Medium
|
Thomas Herve |
Bug Description
When we create/update a software deployment, we use RPC to talk to another engine for getting its status. The default interval is 1 sec, so we generate lots of messages on the bus to retrieve that status. We should try to reduce this overhead.
Changed in heat: | |
status: | New → In Progress |
Changed in heat: | |
status: | Fix Released → Triaged |
Changed in heat: | |
milestone: | none → no-priority-tag-bugs |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/281220 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=a709637a171 66cb12e5d949448 37bac6451b2851
Committed: https:/
Submitter: Jenkins
Branch: master
commit a709637a17166cb 12e5d94944837ba c6451b2851
Author: Thomas Herve <email address hidden>
Date: Tue Feb 16 16:29:51 2016 +0100
Replace SD RPC polling by long RPC call
This changes the way SoftwareDeployment updates its internal status.
Instead of querying the deployment status in a loop using RPC client, it
makes a single call, which returns once the status has been updated.
Closes-Bug: #1549219 1817be6bea764f2 3b68a39b2d4
Change-Id: I484b7c8cb4a4e7