Hi all:
There exist nova options ('reserved_host_disk_mb' and
'reserved_host_memory_mb') which allow reserving disk and ram in
hypervisors (vCPU seems not be reservable). [1]
On the other hand, during compute scheduling process [2], weigthing
step sorts hypervisors according metrics configurable by operators.
[1] http://docs.openstack.org/trunk/config-reference/content/list-of-compute-config-options.html
[2] http://docs.openstack.org/trunk/config-reference/content/section_compute-scheduler.html
Best,
---
JuanFra Rodriguez Cardoso
2014-11-26 17:38 GMT+01:00 Don Waterloo <don.waterloo at gmail.com>:
>
>
> On 25 November 2014 at 14:39, Georgios Dimitrakakis <giorgis at acmac.uoc.gr>
> wrote:
>>
>> Hi Don!
>>
>> Yes, maybe quota is not the right word.
>>
>> What I want is somehow to adjust the total number of vCPUs and the total
>> number of RAM that can be assigned to all VMs for a specific hypervisor.
>> Then Openstack based on these settings will accept or deny the creation of a
>> new VM at that hypervisor and will continue at the next hypervisor.
>>
>> Besides that is there a way to define hypervisor priority?? For instance
>> if I want to start putting VMs on one hypervisor rather than on another but
>> don't want to do it manually using the zone setting. Can I configure it?
>>
>>
>> Thanks a lot for your answers!
>>
>>
>> All the best,
>>
>
> You will need to create a custom nova scheduler filter to achieve this.
> http://docs.openstack.org/openstack-ops/content/customize.html
> see the " Customizing the OpenStack Compute (nova) Scheduler"
> section.
>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>