Re: [openstack-dev] Custom Nova scheduler based on CPU queue length (Clint Byrum)
;>> I can submit a change to fuel-qa for adding the LMA team to the
> >>> MAINTAINERS file but I can't figure out the structure of the YAML data:
> >>> fuel-web/MAINTAINERS [2] is organized as "{directory1: [maintainer1,
> >>> maintainer2, ...], directory2: [...], ...}" while for fuel-qa [3] (and
> >>> other Fuel projects), it's "[maintainer1, maintainer2, ...]".
> >>>
> >>> BR,
> >>> Simon
> >>>
> >>> [1]
> >>>
> http://specs.fuel-infra.org/fuel-specs-master/policy/team-structure.html
> >>> [2] https://github.com/openstack/fuel-web/blob/master/MAINTAINERS
> >>> [3] https://github.com/openstack/fuel-qa/blob/master/MAINTAINERS
> >>>
> >>>
> >>> On Sat, Oct 17, 2015 at 2:21 AM, Andrew Woodward
> >>> wrote:
> >>>
> >>>> We have already discussed this to be a result of describing data
> driven
> >>>> testing, untill this spec is completed there is little sense to
> remove all
> >>>> of these since fuel-qa is 100% required to operate this way. In the
> interim
> >>>> we should just specify the appropriate SME with the MAINTAINERS file.
> >>>>
> >>>> On Fri, Oct 16, 2015 at 11:34 AM Sergii Golovatiuk <
> >>>> sgolovat...@mirantis.com> wrote:
> >>>>
> >>>>> Tests should be in plugin
> >>>>>
> >>>>> --
> >>>>> Best regards,
> >>>>> Sergii Golovatiuk,
> >>>>> Skype #golserge
> >>>>> IRC #holser
> >>>>>
> >>>>> On Fri, Oct 16, 2015 at 5:58 PM, Simon Pasquier <
> >>>>> spasqu...@mirantis.com> wrote:
> >>>>>
> >>>>>> Hello Alexey,
> >>>>>>
> >>>>>> On Fri, Oct 16, 2015 at 5:35 PM, Alexey Elagin <
> aela...@mirantis.com>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Hello Simon!
> >>>>>>>
> >>>>>>> We are going to remove plugins' functional tests from fuel-qa
> >>>>>>> because this tests don't use for our plugins CI process.
> >>>>>>>
> >>>>>>
> >>>>>> And where are the existing tests going to be stored then?
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Simon
> >>>>>>
> >>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> __
> >>>>>>> OpenStack Development Mailing List (not for usage questions)
> >>>>>>> Unsubscribe:
> >>>>>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> __
> >>>>>> OpenStack Development Mailing List (not for usage questions)
> >>>>>> Unsubscribe:
> >>>>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> __
> >>>>> OpenStack Development Mailing List (not for usage questions)
> >>>>> Unsubscribe:
> >>>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>>>>
> >>>> --
> >>>>
> >>>> --
> >>>>
> >>>> Andrew Woodward
> >>>>
> >>>> Mirantis
> >>>>
> >>>> Fuel Community Ambassador
> >>>>
> >>>> Ceph Community
> >>>>
> >>>>
> >>>>
> __
> >>>> OpenStack Development Mailing List (not for usage questions)
> &g
Re: [openstack-dev] Custom Nova scheduler based on CPU queue length
Hi Rahul, > As I understand a weigher for the filter scheduler that weighs filtered host > machines based on the host weight option, 'cpu.percent' can be > configured to prioritize the hosts based on CPU percentage, but there are > only limited options when it comes to filtering of machines in the > first place, that too using the CPU queue length. > > Also, I understand that IBM has its platform resource scheduler that can be > used to build custom plugins to get user defined metrics, is there > a similar way in pure Openstack which can be used to get the CPU queue length. > > As of now, I am thinking of writing a custom script to be kept in all compute > nodes to retrieve the CPU queue length and send it to the Nova > controller, is this the way to go, or is there a defined approach that I can > follow to implement a scheduler that uses CPU queue length to filter > physical machines. Nova has metric plugins (monitors) in the resource tracker at the compute manager that will report metric data like this to the scheduler. Any weigher plugins can use that data. To see how cpu.percentage is set and used see the following plugins: nova/compute/monitors/cpu_monitor.py nova/scheduler/weights/metrics.py You can create new monitor and weigher plugins using these as a model or propose an addition to cpu_monitor.py if you think it is generally useful. Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Custom Nova scheduler based on CPU queue length
Excerpts from Rahul Nair's message of 2015-10-20 18:53:09 -0700: > Hi All, > > I am fairly new to the OpenStack community and is trying to create a custom > scheduler for Nova. A scheduler based on CPU queue length. Kindly apologize > if there are any inaccuracies in my statements. > > As I understand a weigher for the filter scheduler that weighs filtered > host machines based on the host weight option, 'cpu.percent' can be > configured to prioritize the hosts based on CPU percentage, but there are > only limited options when it comes to filtering of machines in the first > place, that too using the CPU queue length. > > Also, I understand that IBM has its platform resource scheduler that can be > used to build custom plugins to get user defined metrics, is there a > similar way in pure Openstack which can be used to get the CPU queue length. > > As of now, I am thinking of writing a custom script to be kept in all > compute nodes to retrieve the CPU queue length and send it to the Nova > controller, is this the way to go, or is there a defined approach that I > can follow to implement a scheduler that uses CPU queue length to filter > physical machines. > > Any pointers on this would be really helpful. Rahul, I'm realy curious about what it is you're trying to accomplish here. The CPU queue length is an extremely volatile statistic. Is this maybe for a single-purpose cloud where you do have some idea what might be running? __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Custom Nova scheduler based on CPU queue length
Hi All, I am fairly new to the OpenStack community and is trying to create a custom scheduler for Nova. A scheduler based on CPU queue length. Kindly apologize if there are any inaccuracies in my statements. As I understand a weigher for the filter scheduler that weighs filtered host machines based on the host weight option, 'cpu.percent' can be configured to prioritize the hosts based on CPU percentage, but there are only limited options when it comes to filtering of machines in the first place, that too using the CPU queue length. Also, I understand that IBM has its platform resource scheduler that can be used to build custom plugins to get user defined metrics, is there a similar way in pure Openstack which can be used to get the CPU queue length. As of now, I am thinking of writing a custom script to be kept in all compute nodes to retrieve the CPU queue length and send it to the Nova controller, is this the way to go, or is there a defined approach that I can follow to implement a scheduler that uses CPU queue length to filter physical machines. Any pointers on this would be really helpful. Regards, Rahul U Nair __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
