Hi

Please don't add rapidly changing data to VDSDynamic - it has major performance implications.
So, choose option B. Actually, try to expose relevant data in VDSDynamic and VDSStatistics, and VDS should call VDSDynamic and VDSStatistics and merge the data from both entities.


On Thu, Feb 20, 2014 at 11:31 AM, Liao, Chuan (Jason Liao, HPservers-Core-OE-PSC) <chuan.liao@hp.com> wrote:

Hi All,

 

I am Jason Liao from HP who are in charge of NUMA and Virtual NUMA feature.

 

Now I have some concept about the host NUMA topology data structure on engine core

 

We have VDS, VDSDynamic, VDSStatic, VdsStatistics object on engine core.

 

And we have NUMA topology information:

List<NumaNode> numaNodeList

         NumaNode

                  String ID                                                 # update from GetCapabilitiesVDSCommand

                   List<String> cpuList                           # update from GetCapabilitiesVDSCommand

Int totalMem                                        # update from GetCapabilitiesVDSCommand

                   Int freeMem                                          # update from GetStatsVDSCommand

                  

A.      Add this data structure into VDSDynamic

We should change the GetStatsVDSCommand update the VDSDynamic data.

B.      Add this data structure into VDS, and build the data structure from VDSDynamic, VdsStatistics

 

I prefer B. does anybody have some comments?

 

Best Regards,
Jason Liao

 


_______________________________________________
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel