This would be a spec enhancement I think, please look at the specs process here - https://specs.openstack.org/openstack/nova- specs/readme.html
** Changed in: nova Status: New => Opinion ** Changed in: nova Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1655030 Title: AggregateImagePropertiesIsolation can be circumvented using Boot from Volume Status in OpenStack Compute (nova): Opinion Bug description: I have set up AggregateImagePropertiesIsolation to boot certain images on one compute node only. It works. However, when I use Boot from Volume, the VM is launched on any node, although volume_image_metadata of the volume contains the image ID, such as: volume_image_metadata = {u'container_format': u'bare', u'min_ram': u'0', u'disk_format': u'qcow2', u'image_name': u'windows', u'image_id': u'f6add2c7-52c0-46f1-97a5-3c30562fb9b3', u'checksum': u'a11bdae56c6bb8b864fcaf35d4e1e9bb', u'min_disk': u'16', u'size': u'10131734528'} I think this makes the AggregateImagePropertiesIsolation filter next to useless and will make me resort to aggregate segregation by flavor. I think the problem is in the function get_image_metadata_from_volume. It only copies the properties size, min_ram, and min_disk and not the custom properties used for filtering with AggregateImagePropertiesIsolation http://code.metager.de/source/xref/OpenStack/nova/nova/utils.py#1338 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1655030/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp