> -----Original Message----- > From: Itamar Heim [mailto:[email protected]] > Sent: Thursday, July 14, 2011 10:21 PM > > > > On Thu, 2011-07-14 at 10:52 -0400, Itamar Heim wrote: > > > Your use case is more close to backend --> vdsm, where we poll every 2 > > > seconds actually. > > > But the polling every 2 seconds is a very light poll - only list of > VM's > > > and their status. > > > The heavier polling for all detils/stats is not as frequent. > > > > > > So you should probably define the minimal data you need to poll for > more > > > frequently, and run the lighter query (the api has a 'detail' level, > > > though probably not one that light yet). > > > > Do you have any data on what details they are and how often Powershell > > can support listing all instances at that detail level ? > > I didn't say we have that detail level yet in REST, and powershell for > sure doesn't have that optimization. > but we should plan ahead for such a lightweight query on status of VMs, so > the question is do you need anything but vm_id and vm_status for such a > query? > Einav - would we need more things for a lightweight user portal query?
No - status is probably enough; the rest of the properties displayed in the user-portal are unlikely to change (name, description, OS).
