Bernd has this right. Host aggregates (sometimes called Haggs) is the right soluton to this problem. You can setup a flavor to only run on a certain hagg. This works well (in production, at scale). On Sun, Jul 1, 2018 at 7:52 AM, Satish Patel <satish.txt at gmail.com> wrote: > Folks, > > Recently we build openstack for production and i have question related > flavor metadata. > > I have 3 kind of servers 8 core / 32 core / 40 core servers, now i > want to tell my openstack my one of specific application always go to > 32 core machine, how do i tell that to flavor metadata? > > Or should i use availability zone option and create two group? > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20180702/a86f7607/attachment.html>