Reviewed: https://review.openstack.org/586317 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=a9083d13b0a18fb9832878e19a71d42d206f15f0 Submitter: Zuul Branch: master
commit a9083d13b0a18fb9832878e19a71d42d206f15f0 Author: karimull <[email protected]> Date: Thu Jul 26 11:19:34 2018 -0700 Updated AggregateImagePropertiesIsolation filter illustration The example given in this section was not matching the explanation of how the filter works. Updated the example with right properties and aggregate name Change-Id: Ieadeb0d736cc83a41093e6f4dfeb75d2396976ec Closes-Bug: #1684261 ** Changed in: nova Status: In Progress => Fix Released -- 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/1684261 Title: AggregateImagePropertiesIsolation example doesn't actually indicate how it works Status in OpenStack Compute (nova): Fix Released Status in openstack-manuals: Won't Fix Bug description: The AggregateImagePropertiesIsolation filter documentation in https://docs.openstack.org/ocata/config- reference/compute/schedulers.html does not actually effectively illustrate how the filter works. * "For example, the following aggregate myWinAgg has the Windows operating system as metadata (named ‘windows’):" - the subsequent `openstack aggregate show MyWinAgg` does not show any such metadata. * "In this example, because the following Win-2012 image has the windows property, it boots on the sf-devel host (all other filters being equal):" - the subsequent output for `openstack image show Win-2012` does not actually show the image properties (the output is truncated). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1684261/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
