Open Stack

Ok ... if you don’t mind, i might create a blueprint anyways ... for traceability and documentation purposes.
We/WindRiver tracks both blueprints and code submissions that we have worked on, as an indication of our upstream contributions.

Greg.


From: gordon chung <gord at live.ca>
Reply-To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Date: Thursday, November 16, 2017 at 2:59 PM
To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [ceilometer] Blueprint proposals for 'file' publisher: Compression and CSV file format



On 2017-11-16 02:48 PM, Waines, Greg wrote:
Cool ... i will go ahead and submit a blueprint for these.

just an fyi, we don't use blueprints in Telemetry projects. just submit
the code :)

if there's many alternatives to the solution or if it's a something
controversial, we usually discuss it here on ML. in this case, it seems
like a pretty regular feature addition.

Wrt the compression blueprint,  locally we subclassed the base python
rotating file handler class in order to optionally compress the file as
part of the “shouldRollover” stage.

sounds good.

--
gord
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171116/13453cc8/attachment.html>