fuel-dev team mailing list archive

[Roman Alekseenkov <ralekseenkov@xxxxxxxxxxxx>]

Team,

Thank you. The last question that I have -- shall we consider adding an
option into Fuel UI to enable/disable Ceilometer deployment? If the things
get unstable with Ceilometer, customers would want to have an ability to
turn it off.

Thanks,
Roman

On Thursday, December 12, 2013, Nadya Privalova wrote:

> Hi all,
>
> Actually we have a mechanism for cleaning up the data, but I didn't test
> it. There is time-to-live parameter. It's implemented in MySQL and MongoDB
> backends.
> I'm not sure about MongoDB perf testing but I know that Sandy Walsh and
> his Rackspace team have plans about performance testing all Ceilometer's DB
> backends.
>
> Thanks,
> Nadya
>
>
> On Thu, Dec 12, 2013 at 3:33 PM, Roman Sokolkov <rsokolkov@xxxxxxxxxxxx>wrote:
>
> Sorry,
>
> link<https://www.zabbix.com/documentation/2.0/manual/config/items/history_and_trends> -
> how zabbix stores old data.
>
>
> On Thu, Dec 12, 2013 at 3:24 PM, Roman Sokolkov <rsokolkov@xxxxxxxxxxxx>wrote:
>
> Bogdan,
>
> Thanks for your comment. Please see my thoughts:
>
>    - this driver not merged yet.
>    - this a prototype of driver for young technology.
>    - Ceilometer developers prefer MongoDB.
>
> So i don't think we should research something regarding ElasticSearch
> right now. I suggest to focus on MongoDB.
>
> Thanks, Roman S.
>
>
> On Thu, Dec 12, 2013 at 12:38 PM, Bogdan Dobrelya <bdobrelia@xxxxxxxxxxxx>wrote:
>
>  On 12/12/2013 08:51 AM, Roman Alekseenkov wrote:
>
> Nadya,
>
>  Thanks a lot for sharing the results.
>
>  Roman S.,
>
>  What is your perspective on the things described below? I'm worried
> about Ceilometer + MySQL support in Fuel 4.0. As you can see, the DB fell
> apart in a matter of one day. We can't really afford similar behavior in
> customer's environments. So, I'm interested in the following:
>
>    1. Given that Ceilometer generates so much data, will MongoDB really
>    help to handle it better or it's a matter of time until it breaks like
>    MySQL?
>    2. Is there a cleanup mechanism in Ceilometer to clear historical
>    data? We don't want the database to grow indefinitely.
>    3. Are we pointing Ceilometer to the same Galera instance as we use
>    for OpenStack, or we deploy a different MySQL for it in Fuel?
>
>  I'd like to add here: 4) Would it make the sense to use ElasticSearch
> backend driver prototype for ceilometer
> https://blueprints.launchpad.net/ceilometer/+spec/elasticsearch-driver?
> Here is some more considerations about ES as NoSQL usage:
> https://www.found.no/foundation/elasticsearch-as-nosql/
> I believe, this is a good point for deeper research.
>
>
>    1. What are our recommended/default settings in Fuel for Ceilometer?
>    It is stats collection every 5 seconds, or something different? How safe
>    are our defaults?
>    2. Do we allow user to tweak essential Ceilometer settings through
>    Fuel UI or manually?
>
>  Thanks,
> Roman
>
> On Tuesday, December 10, 2013, Nadya Privalova wrote:
>
>     Hi colleagues,
>
>  The purpose of this letter is to describe my Ceilometer tests and just
> experience in it's deployment.
>
> First of all let me describe what I wanted to achieve. There were a lot of
> discussions on summit about Ceilometer's collector performance: community
> was not sure that it
>
>