Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1417221 - [RFE] Deprecate Panko
[RFE] Deprecate Panko
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-panko (Show other bugs)
12.0 (Pike)
Unspecified Unspecified
high Severity medium
: Upstream M1
: 12.0 (Pike)
Assigned To: Pradeep Kilambi
Sasha Smolyak
: FutureFeature, Triaged
Depends On:
Blocks: 1442136
  Show dependency treegraph
 
Reported: 2017-01-27 10:14 EST by Julien Danjou
Modified: 2018-02-05 14:04 EST (History)
11 users (show)

See Also:
Fixed In Version: openstack-panko-2.0.1-0.20170428132720.89a6baf.el7ost
Doc Type: Deprecated Functionality
Doc Text:
The Panko service is officially deprecated in OpenStack version 12. Support for panko will be limited to usage from cloudforms only. We do not recommend using panko outside of the cloudforms use case.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-13 16:04:11 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 459822 None None None 2017-04-26 12:54 EDT
OpenStack gerrit 460230 None None None 2017-04-26 13:28 EDT
Red Hat Product Errata RHEA-2017:3462 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-15 20:43:25 EST

  None (edit)
Description Julien Danjou 2017-01-27 10:14:09 EST
Panko is barely maintained upstream and offer no interesting feature. Plus, it does not scale. The feature it offers can be achieve by using Gnocchi and Aodh.
Therefore Panko should be deprecated in OSP as of OSP12.

(there's no openstack-panko component there so setting to openstack-ceilometer for now)
Comment 11 errata-xmlrpc 2017-12-13 16:04:11 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3462

Note You need to log in before you can comment on or make changes to this bug.