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 <[email protected]> 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 : [email protected] > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
