"Jake G." wrote on 13/08/2013 07:25:04 AM:
> On 2013/08/13, at 12:50, Robert Collins
wrote:
> >>
> >> I was wondering how to handle changing the compute_driver in
nova.conf? I
> >> currently have the default
> >>
> >> compute_driver = libvirt.LibvirtDriver
> >> libvirt_type=kvm
> >>
> >> I w
gt; >>
> >
>
> --
>
> Steve Heistand NASA Ames Research Center
> SciCon Group Mail Stop 258-6
> steve.heist...@nasa.gov
Check that you have scheduler_driver set to
nova.scheduler.filter_scheduler.FilterScheduler and that
scheduler_default_filters includes CoreFilter.
Regards,
Alex
From: Barrow Kwan
To: "openstack@lists.openstack.org"
Date: 21/08/2015 09:16 AM
Subject:[Openstack] [Juno] - cp
Hi Nasir,
You can configure different values in different host aggregates, using
AggregateCoreFilter [1].
Regards,
Alex
[1]
http://docs.openstack.org/kilo/config-reference/content/section_compute-scheduler.html#d6e14399
From: Nasir Mahmood
To: openstack
Date: 23/09/2015 07:01 PM
Another approach that I would recommend is to use the "--availability-zone
azname:hostname" flag.
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1061665
Regards,
Alex
From: Li Ma
To: Mike Wilson , David Wittman
,
Cc: OpenStack General Mailing List
Date: 17/10/2013 05:4
Hi Avi,
This is a very interesting use-case. We have been experimenting internally
with similar ideas (dynamic management of virtualized and bare-metal
resources).
In a nutshell, you can use Heat templates to provision the different
environments. For bare-metal, you can configure Nova to surfac