[Ceilometer] Ceilometer API runs under development server
Bug #1546001 reported by
Nadya Privalova
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Medium
|
Max Yatsenko | ||
Mitaka |
Won't Fix
|
Medium
|
Max Yatsenko | ||
Newton |
Fix Committed
|
Medium
|
Max Yatsenko |
Bug Description
Currently, Ceilometer API is running under werkzeug. It is a development server, so we need to use a production one.
Changed in fuel: | |
status: | New → Confirmed |
assignee: | nobody → MOS Ceilometer (mos-ceilometer) |
Changed in fuel: | |
importance: | Undecided → High |
milestone: | none → 9.0 |
assignee: | MOS Ceilometer (mos-ceilometer) → MOS Puppet Team (mos-puppet) |
Changed in fuel: | |
assignee: | MOS Puppet Team (mos-puppet) → Max Yatsenko (myatsenko) |
tags: | added: area-ceilometer |
Changed in fuel: | |
status: | Confirmed → In Progress |
tags: | added: feature |
To post a comment you must log in.
Looks like an enhancement to me, so I've added "feature" tag. The only reason to treat this is as a High priority bug would be if it were making an existing feature unusable, or broke deployment altogether with a simple workaround: /wiki.openstack .org/wiki/ Fuel/How_ to_contribute# Confirm_ and_triage_ bugs
https:/
If there is no evidence that this is causing signficant problems in production, it can't be higher priority than Medium. If we already had the same configuration in 8.0 and earlier releases, it's a feature and not a regression, so we can't be fixing it after feature freeze.