[
https://issues.apache.org/jira/browse/AMBARI-26656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jialiang Cai updated AMBARI-26656:
----------------------------------
Description:
Ambari needs one console to manage independently owned clusters without leaking
host, request/task, configuration or UI state between them. Cluster selection
must preserve the current Dashboard, while Admin provides a clear cluster
overview, creation, host allocation, permissions and repository navigation.
This new submission consolidates the implementation and review follow-up
developed under AMBARI-26654. It includes stable cluster ownership across
server/agent/REST/STOMP boundaries; durable managed HBase dependency
deployments with binding, operation, credential and task lineage; common
dependency constraints for Blueprint and Add Service; and recoverable React
installation/navigation flows.
Acceptance covered a native RPM deployment with six registered nodes: the first
cluster owns three nodes, the other three are initially unassigned, then API
provisioning creates the second cluster and adds HBase to both. Installed HBase
SDK operations verify distinct HDFS namespaces and local ZooKeeper ownership.
Scoped-user requests, duplicate host attachment and foreign request lookup are
rejected. Real lifecycle testing found and corrected Registry DNS supervisor
shutdown and command-scoped HBase hook initialization defects.
Earlier runtime evidence also covers HBase using another cluster's managed
HDFS/ZooKeeper, actual scoped STOMP events and browser route rejection.
Production source, focused test commands, preserved failure/recovery receipts
and remaining acceptance gates are recorded in
docs/design/multi-cluster-review-and-remediation.md.
Real KDC callbacks, the complete managed provider lifecycle/retention matrix,
all crash/response-loss boundaries and full broker revocation coverage remain
open. This issue does not claim those unexecuted scenarios passed.
Pull request: [apache/ambari#4216|https://github.com/apache/ambari/pull/4216].
Submission branch: AMBARI-26656, based on trunk after #4208.
Final RPM screenshots are attached to this issue and embedded in the PR:
cluster-overview.png and host-ownership.png. The affected tests after upstream
alignment passed: 195 YARN and 22 Hive Python tests.
was:
Ambari needs one console to manage independently owned clusters without leaking
host, request/task, configuration or UI state between them. Cluster selection
must preserve the current Dashboard, while Admin provides a clear cluster
overview, creation, host allocation, permissions and repository navigation.
This new submission consolidates the implementation and review follow-up
developed under AMBARI-26654. It includes stable cluster ownership across
server/agent/REST/STOMP boundaries; durable managed HBase dependency
deployments with binding, operation, credential and task lineage; common
dependency constraints for Blueprint and Add Service; and recoverable React
installation/navigation flows.
Acceptance covered a native RPM deployment with six registered nodes: the first
cluster owns three nodes, the other three are initially unassigned, then API
provisioning creates the second cluster and adds HBase to both. Installed HBase
SDK operations verify distinct HDFS namespaces and local ZooKeeper ownership.
Scoped-user requests, duplicate host attachment and foreign request lookup are
rejected. Real lifecycle testing found and corrected Registry DNS supervisor
shutdown and command-scoped HBase hook initialization defects.
Earlier runtime evidence also covers HBase using another cluster's managed
HDFS/ZooKeeper, actual scoped STOMP events and browser route rejection.
Production source, focused test commands, preserved failure/recovery receipts
and remaining acceptance gates are recorded in
docs/design/multi-cluster-review-and-remediation.md.
Real KDC callbacks, the complete managed provider lifecycle/retention matrix,
all crash/response-loss boundaries and full broker revocation coverage remain
open. This issue does not claim those unexecuted scenarios passed.
> Implement isolated multi-cluster management and recoverable HBase dependencies
> ------------------------------------------------------------------------------
>
> Key: AMBARI-26656
> URL: https://issues.apache.org/jira/browse/AMBARI-26656
> Project: Ambari
> Issue Type: New Feature
> Reporter: Jialiang Cai
> Priority: Major
> Attachments: cluster-overview.png, host-ownership.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ambari needs one console to manage independently owned clusters without
> leaking host, request/task, configuration or UI state between them. Cluster
> selection must preserve the current Dashboard, while Admin provides a clear
> cluster overview, creation, host allocation, permissions and repository
> navigation.
> This new submission consolidates the implementation and review follow-up
> developed under AMBARI-26654. It includes stable cluster ownership across
> server/agent/REST/STOMP boundaries; durable managed HBase dependency
> deployments with binding, operation, credential and task lineage; common
> dependency constraints for Blueprint and Add Service; and recoverable React
> installation/navigation flows.
> Acceptance covered a native RPM deployment with six registered nodes: the
> first cluster owns three nodes, the other three are initially unassigned,
> then API provisioning creates the second cluster and adds HBase to both.
> Installed HBase SDK operations verify distinct HDFS namespaces and local
> ZooKeeper ownership. Scoped-user requests, duplicate host attachment and
> foreign request lookup are rejected. Real lifecycle testing found and
> corrected Registry DNS supervisor shutdown and command-scoped HBase hook
> initialization defects.
> Earlier runtime evidence also covers HBase using another cluster's managed
> HDFS/ZooKeeper, actual scoped STOMP events and browser route rejection.
> Production source, focused test commands, preserved failure/recovery receipts
> and remaining acceptance gates are recorded in
> docs/design/multi-cluster-review-and-remediation.md.
> Real KDC callbacks, the complete managed provider lifecycle/retention matrix,
> all crash/response-loss boundaries and full broker revocation coverage remain
> open. This issue does not claim those unexecuted scenarios passed.
> Pull request:
> [apache/ambari#4216|https://github.com/apache/ambari/pull/4216]. Submission
> branch: AMBARI-26656, based on trunk after #4208.
> Final RPM screenshots are attached to this issue and embedded in the PR:
> cluster-overview.png and host-ownership.png. The affected tests after
> upstream alignment passed: 195 YARN and 22 Hive Python tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
