The new framework does indeed support user-defined monitors. You just extend whatever monitor’d like (e.g., nova.compute.monitors.cpu.virt_driver.Monitor) and add your customized logic. And since the new framework uses stevedore-based extension points, you just need to be sure to add the appropriate entry to your project’s setup.py file (or entry_points.txt in your egg) so that stevedore can load them properly.
Hope this helps! Thanks, Joe > On Sep 10, 2015, at 2:52 AM, Hou Gang HG Liu <[email protected]> wrote: > > Hi all, > > I notice nova compute monitor now only tries to load monitors with namespace > "nova.compute.monitors.cpu", and only one monitor in one namespace can be > enabled( > https://review.openstack.org/#/c/209499/6/nova/compute/monitors/__init__.py > <https://review.openstack.org/#/c/209499/6/nova/compute/monitors/__init__.py>). > > > Is there a plan to make MonitorHandler.NAMESPACES configurable or just hard > code constraint as it is now? And how to make compute monitor support user > defined as it was? > > Thanks! > B.R > > Hougang Liu （刘侯刚） > Developer - IBM Platform Resource Scheduler > <Mail > Attachment.gif> > Systems and Technology Group > > Mobile: 86-13519121974 | Phone: 86-29-68797023 | Tie-Line: 87023 > 陕西省西安市高新六路42号中清大厦3层 > E-mail: [email protected] > Xian, Shaanxi Province 710075, > China > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
