On Wed, Dec 03, 2014 at 01:28:36PM +0000, Mooney, Sean K wrote: > Hi > > Unfortunately a flavor + aggregate is not enough for our use case as it is > still possible for the tenant to misconfigure a vm. > > The edge case not covered by flavor + aggregate that we are trying to prevent > is as follows. > > The operator creates an aggregate containing the nodes that require all VMs > to use large pages. > The operator creates flavors with and without memory backing specified. > > The tenant selects the aggregate containing nodes that only supports > hugepages and a flavor that requires small or any. > Or > The tenant selects a flavor that requires small or any and does not select an > aggregate.
The tenant isn't responsible for selecting the aggregate. The operator should be associating the aggregate directly to the flavour. So the tenant merely has to select the right flavour. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
