Bug 7456 - Subclusters can be interpreted as optional
Summary: Subclusters can be interpreted as optional
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Documentation (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.11.0
Assignee: Samuel Mannehed
URL:
Keywords: ossman_tester, prosaic
Depends on:
Blocks:
 
Reported: 2019-12-06 11:38 CET by Samuel Mannehed
Modified: 2019-12-10 12:27 CET (History)
0 users

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Samuel Mannehed cendio 2019-12-06 11:38:07 CET 
Our subcluster documentation starts with:

> A subcluster is a group of agents serving a specific purpose within the ThinLinc cluster. The dimension for grouping can be chosen at will and could for example be; location, project, application etc.

It's easy to misunderstand this and miss that ThinLinc always requires subcluster configuration, even with only one server machine. I think this could be clarified easily.
Comment 2 Samuel Mannehed cendio 2019-12-06 16:41:05 CET 
Documentation has been clarified.
Comment 3 Pierre Ossman cendio 2019-12-10 12:27:26 CET 
I think the new text might have a bit too strong focus on a single agent (as opposed to a single subcluster), but looks decent enough.
Note You need to log in before you can comment on or make changes to this bug.