Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

On 03/09/2015 4:02 PM, Dan Smith wrote: - do we need to migrate the db to some handle different set of >attributes and what happens for nosql dbs? No, Nova made no schema changes as a result of moving to objects. so i don't really understand how this part works. if i have two collectors --

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

On 28/08/15 01:54 PM, Dan Smith wrote: we store everything as primitives: floats, time, integer, etc... since we need to query on attributes. it seems like versionedobjects might not be useful to our db configuration currently. I don't think the former determines the latter -- we have lots of

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

>>> we store everything as primitives: floats, time, integer, etc... since >>> we need to query on attributes. it seems like versionedobjects might not >>> be useful to our db configuration currently. >> I don't think the former determines the latter -- we have lots of things >> stored as rows of

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

On 9/1/15, 11:31 AM, "gord chung" wrote: > > >On 28/08/2015 5:18 PM, Alec Hothan (ahothan) wrote: >> >> >> >> >> On 8/28/15, 11:39 AM, "gord chung" wrote: >> >>> i should start by saying i re-read my subject line and it arguably comes >>> off aggressive -- i

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

On 02/09/2015 11:25 AM, Alec Hothan (ahothan) wrote: On 9/1/15, 11:31 AM, "gord chung" wrote: re: serialisation, that probably isn't the biggest concern for Ceilometer performance. the main items are storage -- to be addressed by Gnocchi/tsdb, and polling load. i just

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

On 28/08/2015 5:18 PM, Alec Hothan (ahothan) wrote: On 8/28/15, 11:39 AM, "gord chung" wrote: i should start by saying i re-read my subject line and it arguably comes off aggressive -- i should probably have dropped 'explain' :) On 28/08/15 01:47 PM, Alec Hothan (ahothan)

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

On Thu, 27 Aug 2015 15:37:24 -0400 gord at live.ca (gord chung) wrote: polling agent --- topic queue --- notification agent --- topic queue --- collector (direct connection to db) or OpenStack service --- topic queue --- notification agent --- topic queue --- collector (direct connection

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

there was a little skeptism because it was originally sold as magic, but reading the slides from Vancouver[1], it is not magic. I think I specifically said they're not magic in my slides. Not sure who sold you them as magic, but you should leave them a less-than-five-stars review. Ceilometer

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

On 28/08/15 12:18 PM, Roman Dobosz wrote: So imagine we have new versions of the schema for the events, alarms or samples in ceilometer introduced in Mitaka release while you have all your ceilo services on Liberty release. To upgrade ceilometer you'll have to stop all services to avoid data

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

On 28/08/15 12:49 PM, Dan Smith wrote: there was a little skeptism because it was originally sold as magic, but reading the slides from Vancouver[1], it is not magic. I think I specifically said they're not magic in my slides. Not sure who sold you them as magic, but you should leave them a

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

i should start by saying i re-read my subject line and it arguably comes off aggressive -- i should probably have dropped 'explain' :) On 28/08/15 01:47 PM, Alec Hothan (ahothan) wrote: On 8/28/15, 10:07 AM, gord chung g...@live.ca wrote: On 28/08/15 12:18 PM, Roman Dobosz wrote: So

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

On 8/28/15, 11:39 AM, gord chung g...@live.ca wrote: i should start by saying i re-read my subject line and it arguably comes off aggressive -- i should probably have dropped 'explain' :) On 28/08/15 01:47 PM, Alec Hothan (ahothan) wrote: On 8/28/15, 10:07 AM, gord chung g...@live.ca

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

On 8/28/15, 10:07 AM, gord chung g...@live.ca wrote: On 28/08/15 12:18 PM, Roman Dobosz wrote: So imagine we have new versions of the schema for the events, alarms or samples in ceilometer introduced in Mitaka release while you have all your ceilo services on Liberty release. To upgrade

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

we store everything as primitives: floats, time, integer, etc... since we need to query on attributes. it seems like versionedobjects might not be useful to our db configuration currently. I don't think the former determines the latter -- we have lots of things stored as rows of column

[openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

hi, there has been a lot of work done across the community and Ceilometer relating to versionedobjects. in Ceilometer particularly, this effort has somewhat stalled as contributors are unsure of the benefits of versionedobjects and how it relates to Ceilometer. there was a little skeptism