Ask Your Question

GroupAntiAffinityFilter Heat

asked 2014-03-07 14:34:35 -0600

kfox1111 gravatar image

I'm working on creating a set of MongoDB heat templates. I would like to ensure that as Mongo replica set's come and go, they are placed on seperate hosts.

The some older documentation makes it sound like you can specify a group name like "MongoDB-ReplicaSets" and have the scheduler figure out what instances are tagged that way. Some newer documentation makes it sound like you must specify the set of all instances you want it on different hosts from. Which is it? The group name only is much better then needing to know all the instances, which I'm not sure I have access to.

It is also unclear, how I would specify that I want the GroupAntiAffinityFilter and not the GroupAffinity filter in the template. What is the correct nova hint for this?

Maybe there is a better way to do this too. Any suggestions?

Thanks, Kevin

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2015-01-19 04:05:25 -0600

pas-ha gravatar image

It seems that Nova Server Group resource is what you need:

It has a policy property, dafaulting to anti-affinity.

This resource type is pretty new (available since Juno) and might be underdeveloped yet, so if you have ane comments on features missing or find any bugs with it, please raise your concerns via Launchpad bugs for Heat.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-03-07 14:34:35 -0600

Seen: 513 times

Last updated: Jan 19 '15