neutron

If we need a host filter in neutron ?

Bug #1603833 reported by QunyingRan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Triaged
Wishlist
Unassigned

Bug Description

There is no host filter in neutron to ensure resources available for network when booting instance。 Now, when booting instance, nova will select one host and send message to neutron agent, but the agent is inactive actually. For bandwith, it's limited in physical interfaces, if instance ports which had bandwidth-limited-rule and needed bandwidth resource more than that physical interfaces have, the qos policy will be invalid. So if we need to add a host filter in neutron, when creating a instance nova send a message to neutron to get available hosts for network resource and then boot instance.

Tags: rfe
Revision history for this message
Brandon Logan (brandon-logan) wrote :

I'm going to add rfe to this. I see it as an additional feature request.

tags: added: rfe
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Last time I checked, Nova has a pluggable scheduling system where a filter can be added to do host selection. We cannot maintain the filter in Neutron.

Changed in neutron:
status: New → Confirmed
importance: Undecided → Wishlist
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

I am tempted to say that 'No we do not need a host filter in Neutron', but I would like others to chime in.

Changed in neutron:
status: Confirmed → Triaged
Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :

What is the use case? Not oversubscribing the node bandwidth? If so, there is another RFE just for that: https://bugs.launchpad.net/neutron/+bug/1578989 It was postponed because of pending work in nova.

Revision history for this message
Carl Baldwin (carl-baldwin) wrote :

There is also work to schedule using IP availability across various segments. You should look at the generic resource pool mechanism being developed in Nova [1]. That is what we will be using for that. It is not going to be ready until Ocata.

I also agree that we do not need a host filter in Neutron. We need RFEs to speak in terms of use cases. We seem to already cover bandwidth with the RFE Ihar pointed to and we have IP availability covered too under the routed networks work. I think we should close this one.

[1] https://review.openstack.org/#/q/topic:bp/generic-resource-pools

Revision history for this message
Miguel Angel Ajo (mangelajo) wrote :

As Ihar said this is already proposed in [1]

[1] https://bugs.launchpad.net/neutron/+bug/1578989

I'd mark this as a duplicate, we need to wait on the generic resource pools to be ready.

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Status update:

http://eavesdrop.openstack.org/meetings/neutron_drivers/2016/neutron_drivers.2016-07-21-22.00.log.html#l-310

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.