Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1093841

Summary: [RFE] Schedule based on interface speed and link information
Product: Red Hat OpenStack Reporter: Stephen Gordon <sgordon>
Component: openstack-novaAssignee: RHOS Maint <rhos-maint>
Status: CLOSED WONTFIX QA Contact: Ami Jeain <ajeain>
Severity: medium Docs Contact:
Priority: high    
Version: unspecifiedCC: dyuan, honzhang, mzhan, ndipanov, rbalakri, weizhan, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: libvirt-api-interface-info Environment:
Last Closed: 2015-04-15 15:46:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1076960, 1088713    
Bug Blocks: 1077198, 1078542    

Description Stephen Gordon 2014-05-02 19:27:30 UTC 
+++ This bug was initially created as a clone of Bug #1076960 +++

Description of problem:

OpenStack to take account of link status and speed when scheduling instances. Key questions:

1) What to do if link is down? Disable host?
2) What to do with link speed - particularly where it is less than expected?
Comment 3 Stephen Gordon 2014-05-22 15:11:45 UTC 
There was a somewhat related thread here - though it proposes disabling the host entirely if an interface link is down rather than just making it unavailable for passthrough:

    http://lists.openstack.org/pipermail/openstack-dev/2014-April/033840.html

...and these two proposals:

    nic-state-aware-scheduling: https://review.openstack.org/#/c/87978/2
    pci-device-capability-aware-scheduling: https://review.openstack.org/#/c/92843/

None of which appears to initially be particularly popular (understatement). We need to work out with the community what the correct approach is.