Re: [openstack-dev] [Nova] New DB column or new DB table?

2013-07-22 Thread Wang, Shane
Daniel raised a good point, I also agreed that is not a good architecture. Nova can't touch any monitoring stuffs - I don't think that is good. At least, Ceilometer can be a monitoring hub for external utilities. On the other hand, for the options Lianhao raised. Is a query on a DB and a json

Re: [openstack-dev] [Nova] New DB column or new DB table?

2013-07-19 Thread Day, Phil
] New DB column or new DB table? On 07/17/2013 10:54 PM, Lu, Lianhao wrote: Hi fellows, Currently we're implementing the BP https://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling. The main idea is to have an extensible plugin framework on nova-compute where every plugin

Re: [openstack-dev] [Nova] New DB column or new DB table?

2013-07-19 Thread Sandy Walsh
On 07/18/2013 11:12 PM, Lu, Lianhao wrote: Sean Dague wrote on 2013-07-18: On 07/17/2013 10:54 PM, Lu, Lianhao wrote: Hi fellows, Currently we're implementing the BP https://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling. The main idea is to have an extensible plugin

Re: [openstack-dev] [Nova] New DB column or new DB table?

2013-07-19 Thread Sandy Walsh
On 07/19/2013 09:43 AM, Sandy Walsh wrote: On 07/18/2013 11:12 PM, Lu, Lianhao wrote: Sean Dague wrote on 2013-07-18: On 07/17/2013 10:54 PM, Lu, Lianhao wrote: Hi fellows, Currently we're implementing the BP https://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling.

Re: [openstack-dev] [Nova] New DB column or new DB table?

2013-07-19 Thread Daniel P. Berrange
On Thu, Jul 18, 2013 at 07:05:10AM -0400, Sean Dague wrote: On 07/17/2013 10:54 PM, Lu, Lianhao wrote: Hi fellows, Currently we're implementing the BP https://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling. The main idea is to have an extensible plugin framework on

Re: [openstack-dev] [Nova] New DB column or new DB table?

2013-07-19 Thread Jiang, Yunhong
: [openstack-dev] [Nova] New DB column or new DB table? Hi all, We have to much different branches about scheduler (so I have to repeat here also). I am against to add some extra tables that will be joined to compute_nodes table on each scheduler request (or adding large text columns). Because it make

Re: [openstack-dev] [Nova] New DB column or new DB table?

2013-07-19 Thread Boris Pavlovic
Hi all, We have to much different branches about scheduler (so I have to repeat here also). I am against to add some extra tables that will be joined to compute_nodes table on each scheduler request (or adding large text columns). Because it make our non scalable scheduler even less scalable.

Re: [openstack-dev] [Nova] New DB column or new DB table?

2013-07-18 Thread Sean Dague
On 07/17/2013 10:54 PM, Lu, Lianhao wrote: Hi fellows, Currently we're implementing the BP https://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling. The main idea is to have an extensible plugin framework on nova-compute where every plugin can get different metrics(e.g. CPU

Re: [openstack-dev] [Nova] New DB column or new DB table?

2013-07-18 Thread Murray, Paul (HP Cloud Services)
Development Mailing List Subject: Re: [openstack-dev] [Nova] New DB column or new DB table? On 07/17/2013 10:54 PM, Lu, Lianhao wrote: Hi fellows, Currently we're implementing the BP https://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling. The main idea is to have an extensible plugin

Re: [openstack-dev] [Nova] New DB column or new DB table?

2013-07-18 Thread Jay Pipes
On 07/18/2013 10:44 AM, Murray, Paul (HP Cloud Services) wrote: Hi All, I would like to chip in with something from the side here (sorry to stretch the discussion out). I was looking for a mechanism to do something like this in the context of this blueprint on network aware scheduling:

Re: [openstack-dev] [Nova] New DB column or new DB table?

2013-07-18 Thread Murray, Paul (HP Cloud Services)
Hi Jay, Lianhao, All, Sorry if this comes out of order - for some reason I am not receiving the messages so I'm cut-and-pasting from the archive :( I think I might mean something closer to Brian's blue print (now I've seen it)