1. 05 Aug, 2019 2 commits
  2. 11 May, 2018 4 commits
  3. 12 Feb, 2018 9 commits
  4. 11 Feb, 2018 3 commits
    • Fix docs for IsolatedHostsFilter · 60bbec15
      The docs were using variable names from the filter code rather
      than the actual config options.
      
      Change-Id: I2694b32e9c90ad098101e41e4e3ae36ddafd8d0f
      Related-Bug: #1746483
      Matt Riedemann committed
    • Handle volume-backed instances in IsolatedHostsFilter · 0a7427dc
      The RequestSpec.image object for a volume-backed instance will
      not have the 'id' attribute set because the
      nova.utils.get_image_metadata_from_volume() method doesn't convert
      the volume['volume_image_metadata']['image_id'] into the ImageMeta.id
      field. It is unclear if there are intentional reasons for omitting
      this information, but the IsolatedHostsFilter has just never supported
      filtering for volume-backed instances based on a provided image id.
      
      The logic within the filter depends on the
      restrict_isolated_hosts_to_isolated_images config option, which
      defaults to True. When True, a volume-backed instance will not be
      put on an isolated host. When False, a volume-backed instance can
      go on any host, isolated or not.
      
      Again, it's unclear if we should actually be filtering volume-backed
      servers using the image_id from the volume_image_metadata or not,
      but it's not what we've historically done so this change simply
      fixes the regression bug.
      
      Change-Id: Ieb8abb1a3f04ce008f9617e051e4d720dbe6917a
      Closes-Bug: #1746483
      Matt Riedemann committed
    • Add regression test for BFV+IsolatedHostsFilter failure · 4f9667b7
      Creating a volume-backed server while using the IsolatedHostsFilter
      results in a NoValidHost failure because the filter tries to load
      the RequestSpec.image.id but when you create a server from a volume,
      an image is not required directly in the server create request.
      
      Change-Id: Id21e0afa5cec401555bee679193c256e55be863b
      Related-Bug: #1746483
      Matt Riedemann committed
  5. 10 Feb, 2018 5 commits
  6. 09 Feb, 2018 17 commits