*To:* OpenStack Development Mailing List (not for usage questions)
*Cc:* jcsf; 'Carl Baldwin'; 'A, Keshava'
*Subject:* Re: [openstack-dev] [neutron][L3] VM Scheduling v/s Network as
input any consideration ?
Le 30/05/2014 10:06, jcsf a écrit :
Carl,
A new routing
Mathieu Rohon wrote:
I'm also very interested in scheduling VMs with Network requirement. This
seems to be in the scope of NFV workgroup [1].
For instance, I think that scheduling should take into account bandwith/QoS
requirement for a VM, or specific Nic
This falls in my area of interest as
Le 30/05/2014 14:44, CARVER, PAUL a écrit :
Mathieu Rohon wrote:
I'm also very interested in scheduling VMs with Network requirement.
This seems to be in the scope of NFV workgroup [1].
For instance, I think that scheduling should take into account
bandwith/QoS requirement for a VM, or
,
Keshava.A
*From:* jcsf31...@gmail.com [mailto:jcsf31...@gmail.com]
*Sent:* Thursday, May 29, 2014 9:14 AM
*To:* openstack-dev@lists.openstack.org; Carl Baldwin; Kyle Mestery;
OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [neutron][L3] VM Scheduling v/s
Hi Keshava,
To the best of my knowledge Nova does not have an explicit way to determine
VM placements based on network attributes. That said, it does have a
general mechanism called host-aggregates [1] that can be leveraged to
address what you are looking for. How certain hosts are grouped
Armando M. arma...@gmail.com wrote on 05/28/2014 07:35:52 PM:
From: Armando M. arma...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date: 05/28/2014 07:37 PM
Subject: Re: [openstack-dev] [neutron][L3] VM Scheduling v/s
: [openstack-dev] [neutron][L3] VM Scheduling v/s Network as input any consideration ?
Hi keshava,
This is an area that I am interested in. I'd be happy to collaborate with you on a blueprint. This would require enhancements to the scheduler as you suggested.
There are a number
