On Fri, Apr 12, 2013 at 11:09:18AM -0700, Randy Presuhn wrote: > Hi - > > > From: "Juergen Schoenwaelder" <[email protected]> > > To: "Randy Presuhn" <[email protected]> > > Cc: <[email protected]> > > Sent: Thursday, April 11, 2013 11:36 PM > > Subject: Re: [OPSAWG] draft-asai-vmm-mib: Issues on notifications > ... > > > > o Issue 1-1) Scalability issue on notifications: The number of > ... > > I think Michael wanted to post notification definitions that help > > reduce the number of notifications emitted if for example all virtual > > machines of a hypervisor change state at about the same time (e.g., > > because the physical server is restarted). This may be a good thing > > since it reduces the number of notifications at the source and as > > such works independently of RFCs 3014 or 3877. > > For that specific use case, a notifcation identifying the hypervisor > to which those VMs belong, rather than the individual virtual machines, > would seem a better way to go. One might even argue that the > coldStart notification type could be sufficient to do the job.
Yes, for this use case - I assume Michael has more insights whether there are other use cases where subsets of all machines of a hypervisor change state together. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
