Re: [Engine-devel] vds_dynamic refactor

2014-04-06 Thread Liran Zelkha
ot; < > engine-devel@ovirt.org> > > Sent: Thursday, April 3, 2014 5:16:51 PM > > Subject: Re: [Engine-devel] vds_dynamic refactor > > > > Don't go down that road. Status shouldn't be saved in the db. > > But anyway statistics is rapidly changing. So it fits..

Re: [Engine-devel] vds_dynamic refactor

2014-04-06 Thread Liran Zelkha
On Thu, Apr 3, 2014 at 5:33 PM, Gilad Chaplik wrote: > *From: *"Liran Zelkha" > *To: *"Gilad Chaplik" > *Cc: *"Omer Frenkel" , "Eli Mesika" < > emes...@redhat.com>, "engine-devel" > *Sent: *Thursday, April 3, 2014 5:27:

Re: [Engine-devel] vds_dynamic refactor

2014-04-06 Thread Gilad Chaplik
> From: "Liran Zelkha" > To: "Gilad Chaplik" > Cc: "Omer Frenkel" , "Eli Mesika" , > "engine-devel" > Sent: Thursday, April 3, 2014 5:27:56 PM > Subject: Re: [Engine-devel] vds_dynamic refactor > True but that's no re

Re: [Engine-devel] vds_dynamic refactor

2014-04-06 Thread Gilad Chaplik
- Original Message - > From: "Liran Zelkha" > To: "Gilad Chaplik" > Cc: "Eli Mesika" , "engine-devel" > Sent: Thursday, April 3, 2014 5:16:51 PM > Subject: Re: [Engine-devel] vds_dynamic refactor > > Don't go down that r

Re: [Engine-devel] vds_dynamic refactor

2014-04-06 Thread Liran Zelkha
i Mesika" > > Cc: "Gilad Chaplik" , "engine-devel" < > engine-devel@ovirt.org> > > Sent: Thursday, April 3, 2014 4:36:07 PM > > Subject: Re: [Engine-devel] vds_dynamic refactor > > > > I would be happy if we can lose vds_dynamic all together,

Re: [Engine-devel] vds_dynamic refactor

2014-04-06 Thread Gilad Chaplik
- Original Message - > From: "Liran Zelkha" > To: "Eli Mesika" > Cc: "Gilad Chaplik" , "engine-devel" > > Sent: Thursday, April 3, 2014 4:36:07 PM > Subject: Re: [Engine-devel] vds_dynamic refactor > > I would

Re: [Engine-devel] vds_dynamic refactor

2014-04-03 Thread Liran Zelkha
uot;Yair Zaslavsky" > > Cc: "engine-devel" > > Sent: Thursday, April 3, 2014 4:00:25 PM > > Subject: Re: [Engine-devel] vds_dynamic refactor > > > > - Original Message - > > > From: "Yair Zaslavsky" > > > To: &qu

Re: [Engine-devel] vds_dynamic refactor

2014-04-03 Thread Eli Mesika
- Original Message - > From: "Gilad Chaplik" > To: "Yair Zaslavsky" > Cc: "engine-devel" > Sent: Thursday, April 3, 2014 4:00:25 PM > Subject: Re: [Engine-devel] vds_dynamic refactor > > - Original Message - > > From:

Re: [Engine-devel] vds_dynamic refactor

2014-04-03 Thread Gilad Chaplik
- Original Message - > From: "Yair Zaslavsky" > To: "Liran Zelkha" > Cc: "Gilad Chaplik" , "engine-devel" > > Sent: Thursday, April 3, 2014 2:12:59 PM > Subject: Re: [Engine-devel] vds_dynamic refactor > > > >

Re: [Engine-devel] vds_dynamic refactor

2014-04-03 Thread Yair Zaslavsky
- Original Message - > From: "Liran Zelkha" > To: "Gilad Chaplik" > Cc: "engine-devel" > Sent: Thursday, April 3, 2014 2:04:29 PM > Subject: Re: [Engine-devel] vds_dynamic refactor > > Why not move it to vds_static? +1 on Liran'

Re: [Engine-devel] vds_dynamic refactor

2014-04-03 Thread Liran Zelkha
Why not move it to vds_static? On Thu, Apr 3, 2014 at 2:00 PM, Gilad Chaplik wrote: > Hi list, > > I propose to split vds_dynamic table into 2 tables: > - vds_dynamic > - vds_on_boot > We need a place to put all non-dynamic data that gets updated once the > host is booted, and I think dynamic i

[Engine-devel] vds_dynamic refactor

2014-04-03 Thread Gilad Chaplik
Hi list, I propose to split vds_dynamic table into 2 tables: - vds_dynamic - vds_on_boot We need a place to put all non-dynamic data that gets updated once the host is booted, and I think dynamic isn't the place for it. In first phase we will put there NUMA host topoplogy, but later on migrate al