Comment 1 for bug 1603142

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
>