Re: [openstack-dev] [nova] [libvirt] enabling per node
> filtering of mempage sizes
>
> On Wed, Dec 03, 2014 at 01:28:36PM +, Mooney, Sean K wrote:
> > Hi
> >
> > Unfortunately a flavor + aggregate is not enough for our use case as
> > it is still
> possible for
On Wed, Dec 03, 2014 at 01:28:36PM +, 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 fo
...@redhat.com]
Sent: Wednesday, December 3, 2014 10:13 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [libvirt] enabling per node filtering of
mempage sizes
On Wed, Dec 03, 2014 at 10:03:06AM +0100, Sahid Orentino Ferdjaoui wrote:
> On
On Wed, Dec 03, 2014 at 10:03:06AM +0100, Sahid Orentino Ferdjaoui wrote:
> On Tue, Dec 02, 2014 at 07:44:23PM +, Mooney, Sean K wrote:
> > Hi all
> >
> > I have submitted a small blueprint to allow filtering of available memory
> > pages
> > Reported by libvirt.
>
> Can you address this wi
On Tue, Dec 02, 2014 at 07:44:23PM +, Mooney, Sean K wrote:
> Hi all
>
> I have submitted a small blueprint to allow filtering of available memory
> pages
> Reported by libvirt.
Can you address this with aggregate? this will also avoid to do
something specific in the driver libvirt. Which w
Hi all
I have submitted a small blueprint to allow filtering of available memory pages
Reported by libvirt.
https://blueprints.launchpad.net/nova/+spec/libvirt-allowed-mempage-sizes
I believe that this change is small enough to not require a spec as per
http://docs.openstack.org/developer/nova/
