For this bug: https://bugs.launchpad.net/nova/+bug/1212478 I can see the argument about not wanting the scheduler to keep trying to find a new host for the migration when the specific targeted host didn't work, but this seems like a design change so wanted to bring it up in the mailing list before trying to triage this. My initial thought is why have the RetryFilter configured for the scheduler if you don't want it to retry, but maybe you want to support both targeted and open (non-targeted) migrations. Thanks, MATT RIEDEMANN Advisory Software Engineer Cloud Solutions and OpenStack Development Phone: 1-507-253-7622 | Mobile: 1-507-990-1889 E-mail: mriedem at us.ibm.com 3605 Hwy 52 N Rochester, MN 55901-1407 United States -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130814/699c71eb/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 1851 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130814/699c71eb/attachment.gif>
