Hey fuel folks, So I know we have designation of conflicts[0] on roles to prevent two roles from being on the same node. Should we also support a colocation option? My thought behind this is that if we were to expose more of the underlying functionality (such as a corosync role), we could then require that roles like database[1] or rabbitmq[2] be combined with the corosync role rather than relying on dirty hiera overrides. In the longer term this could be useful for splitting apart some of the controller functionality into smaller roles but still requiring that they be next to each other on nodes. Thoughts? Thanks, -Alex [0] https://docs.fuel-infra.org/fuel-dev/develop/nailgun/customization/roles.html [1] https://github.com/openstack/fuel-plugin-detach-database/blob/master/deployment_scripts/database_hiera_override.pp#L83-L92 [2] https://github.com/openstack/fuel-plugin-detach-rabbitmq/blob/master/deployment_scripts/rabbitmq_hiera_override.pp#L47-L48 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160628/7bb613ae/attachment.html>