Add warning for Controller+CephOSD roles combination on node

[Kyrylo Romanenko]

It's not recommend to use CephOSD + Controller role on the same node.
Actually Fuel does not give any warning or restriction to combine those roles on the same nodes. Also we have tests in fuel-qa using Controller+CephOSD roles combinations in clusters.
Ignoring of this circumstance may cause unstable cluster deployments.

[Christian Huebner (ossarchitect)]

Kyrylo,

While I wholeheartedly agree with the separation of controller and Cep, I
am curious why this leads to instability. I would expect poor performance
and operational challenges, but at least in theory stability should not be
affected.
If instability is the expected result, shouldn't we just prevent OSD
service from being deployed on the same node as the controller service
instead of warning?

Thanks

Christian

On Jul 14, 2016 09:00, "Kyrylo Romanenko" <email address hidden> wrote:

> Public bug reported:
>
> It's not recommend to use CephOSD + Controller role on the same node.
> Actually Fuel does not give any warning or restriction to combine those
> roles on the same nodes. Also we have tests in fuel-qa using
> Controller+CephOSD roles combinations in clusters.
> Ignoring of this circumstance may cause unstable cluster deployments.
>
> ** Affects: fuel
> Importance: Wishlist
> Assignee: Fuel for Openstack (fuel)
> Status: New
>
>
> ** Tags: area-ceph area-ui
>
> --
> You received this bug notification because you are a member of Fuel for
> Openstack, which is a bug assignee.
> https://bugs.launchpad.net/bugs/1603142
>
> Title:
> Add warning for Controller+CephOSD roles combination on node
>
> Status in Fuel for OpenStack:
> New
>
> Bug description:
> It's not recommend to use CephOSD + Controller role on the same node.
> Actually Fuel does not give any warning or restriction to combine those
> roles on the same nodes. Also we have tests in fuel-qa using
> Controller+CephOSD roles combinations in clusters.
> Ignoring of this circumstance may cause unstable cluster deployments.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/fuel/+bug/1603142/+subscriptions
>

[Oleksiy Molchanov (omolchanov)]

Hi,

I saw it is not recommended, but allowed. Also I saw tests failing with some strange osd-related problem when deploying osd role to controller. I do agree we should restrict osd-controller role.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/342717

[Kyrylo Romanenko (kromanenko)]

Christian, actually poor performance of testing CI environments can cause instabilities of cluster deployments due to expiration of timeouts.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/342717
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=b433ee89f0ae17e0b1d2dbda40636cb19e7c3155
Submitter: Jenkins
Branch: master

commit b433ee89f0ae17e0b1d2dbda40636cb19e7c3155
Author: Oleksiy Molchanov <email address hidden>
Date: Fri Jul 15 13:16:37 2016 +0300

    Restrict usage of controller and osd role on single host

    Update tests

    Change-Id: I64119fa3eb640c23e1f6e3d59e496b6f226be4e4
    Closes-Bug: 1603142

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/fuel-web 10.0.0rc1 release candidate.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/fuel-web 10.0.0 release.