Bug 597146
Summary: | Configuration-coherence of an async cluster via luci | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Frederik Bijlsma <fbijlsma> |
Component: | luci | Assignee: | Ryan McCabe <rmccabe> |
Status: | CLOSED WONTFIX | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 6.1 | CC: | bbrock, cluster-maint, nobody |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-08-22 20:45:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Configuration of clusters in stretch environments is limited to the use cases set forth in the linked Knowledge Base article; as such, the usefulness of this is limited. Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. |
Description of problem: Generally looking into more asynchronous clustering, luci needs ways to handle multi site (asynchronous) clusters. One of the problems is that asynchronous cluster don't need any automatic failover but a most possible coherent config set for the cluster services, with some sets being "local" data and some being "global" data: - service names etc (global definitions) - node names (site specific) see below conversation with pmyers: > So ideally perhaps one could define an asynchronous site in cluster.conf > just for the sake of configuration coherence. > So e.g. the 3rd site node would just get config updates etc, but not > take part in the synchronous cluster. Well, config updates are generally site specific (i.e. hostnames of nodes and of fence devices) So not sure how useful this would be. Perhaps luci functionality for defining a cluster and it's mirror, and making it clearly defined what are site specific config options vs. common (i.e. nodenames, fencing devices would be site specific. service definitions/failover domains could be common) File an RFE bug against luci in RHEL6 bz on this please.