Project

General

Profile

Actions

Feature #8948

closed

Allow MONs and OSDs to be assigned to specific targets

Added by Shambhu Rajak over 9 years ago. Updated over 9 years ago.

Status:
Won't Fix
Priority:
Normal
Assignee:
-
Category:
-
% Done:

0%

Source:
Q/A
Tags:
Backport:
Reviewed:
Affected Versions:

Description

I am using Teuthology extensively, and i have servers which are of different specification depending on the usage monitor,osd, client.

The order of targets and roles dont mapped as the way we provide it in yaml, as result of which i am not able to use the role for the desired node.

How to take care of this situation

Actions #1

Updated by Ian Colle over 9 years ago

  • Assignee deleted (Zack Cerza)
Actions #2

Updated by Sage Weil over 9 years ago

  • Status changed from New to Need More Info

you're right, it's not deterministic. does it need to be?

Actions #3

Updated by Sage Weil over 9 years ago

  • Status changed from Need More Info to Won't Fix
Actions #4

Updated by Shambhu Rajak over 9 years ago

I need to have different server for monitors and osds.
So, its essential for me to map the servers with the services to run upon correctly.

There should be way to understand the order in which we pair the roles and
target nodes, to correctly map.

Actions #5

Updated by Ian Colle over 9 years ago

  • Tracker changed from Bug to Feature
Actions #6

Updated by Ian Colle over 9 years ago

  • Subject changed from The order in which roles are assinged to targets is not fixed to Allow MONs and OSDs to be assigned to specific targets
Actions

Also available in: Atom PDF