On 06/28/2016 06:15 PM, Alex Schultz wrote:
> 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
Good point. A role definition looking like this:
roles_metadata:
controller:
name: "Controller"
description: "..."
conflicts:
- compute
- ceph_osd
colocates(/contains/requires?):
- corosync
- haproxy
- database
- messaging
Would look a way better than hacky code examples you provided.
> 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
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Best regards,
Bogdan Dobrelya,
Irc #bogdando