[
https://issues.apache.org/jira/browse/AMBARI-26663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jialiang Cai updated AMBARI-26663:
----------------------------------
Description:
Management pack V1 currently relies on server-local installation and does not
provide a shared, recoverable lifecycle for HTTP clients and the React frontend.
Add a Server-owned lifecycle for package import, activation, update, binding,
removal and recovery while preserving the four V1 artifact types and existing
service definitions. Persist exact package, plan, operation and resource
identities. Publish immutable definition snapshots and keep accepted task
resources stable across unrelated changes.
Limit maintenance to actual definition consumers and shared resources instead
of blocking ordinary writes across the entire Server. Make publication, failed
hook reconciliation and cancellation recoverable, and reject unsupported
deployed component-model transitions.
Support importing a complete mpackstore bundle, selecting services from a
Java-resolved catalog, and handing the exact selection to new-cluster or Add
Service workflows. Provide HTTP-only Python tooling and generic React service
models/actions without adding a new workflow engine or online marketplace.
Organize the deliverable into topic commits for authoring/contracts, atomic
Server/Agent integration, React integration, and documentation/evidence. The
separate example-package repository is not part of the Ambari source commit.
Local verification completed before submission: 136 Java tests in 21 suites, 87
React tests and production asset build, 16 Python tooling tests, and 40 Agent
resource/configuration tests. Two whole-store builds produced byte-identical
archives. Rocky 8 aarch64 live acceptance has since verified the core HTTP
lifecycle, scoped maintenance, Nginx and PostgreSQL recovery paths, official
Kyuubi binary and SQL, and browser import/recovery. The complete AC-00 through
AC-20 matrix remains unfinished: empty-Server browser installation, crash/race
and interrupted recovery, advanced HDFS parity, and database upgrade/offline
restore still require validation. See docs/mpack/acceptance-results.md and
docs/mpack/conclusion-2026-09-26.md for exact evidence and limits.
was:
Management pack V1 currently relies on server-local installation and does not
provide a shared, recoverable lifecycle for HTTP clients and the React frontend.
Add a Server-owned lifecycle for package import, activation, update, binding,
removal and recovery while preserving the four V1 artifact types and existing
service definitions. Persist exact package, plan, operation and resource
identities. Publish immutable definition snapshots and keep accepted task
resources stable across unrelated changes.
Limit maintenance to actual definition consumers and shared resources instead
of blocking ordinary writes across the entire Server. Make publication, failed
hook reconciliation and cancellation recoverable, and reject unsupported
deployed component-model transitions.
Support importing a complete mpackstore bundle, selecting services from a
Java-resolved catalog, and handing the exact selection to new-cluster or Add
Service workflows. Provide HTTP-only Python tooling and generic React service
models/actions without adding a new workflow engine or online marketplace.
Organize the deliverable into topic commits for authoring/contracts, atomic
Server/Agent integration, React integration, and documentation/evidence. The
separate example-package repository is not part of the Ambari source commit.
Local verification completed before submission: 136 Java tests in 21 suites, 87
React tests and production asset build, 16 Python tooling tests, and 40 Agent
resource/configuration tests. Two whole-store builds produced byte-identical
archives. Live RPM/container deployment acceptance remains to be performed with
the deploy project and its prebuilt runtime image; it must not be inferred from
unit-test results.
> Add HTTP management pack lifecycle, scoped activation, and mpackstore service
> selection
> ---------------------------------------------------------------------------------------
>
> Key: AMBARI-26663
> URL: https://issues.apache.org/jira/browse/AMBARI-26663
> Project: Ambari
> Issue Type: Improvement
> Reporter: Jialiang Cai
> Priority: Major
> Labels: pull-request-available
>
> Management pack V1 currently relies on server-local installation and does not
> provide a shared, recoverable lifecycle for HTTP clients and the React
> frontend.
> Add a Server-owned lifecycle for package import, activation, update, binding,
> removal and recovery while preserving the four V1 artifact types and existing
> service definitions. Persist exact package, plan, operation and resource
> identities. Publish immutable definition snapshots and keep accepted task
> resources stable across unrelated changes.
> Limit maintenance to actual definition consumers and shared resources instead
> of blocking ordinary writes across the entire Server. Make publication,
> failed hook reconciliation and cancellation recoverable, and reject
> unsupported deployed component-model transitions.
> Support importing a complete mpackstore bundle, selecting services from a
> Java-resolved catalog, and handing the exact selection to new-cluster or Add
> Service workflows. Provide HTTP-only Python tooling and generic React service
> models/actions without adding a new workflow engine or online marketplace.
> Organize the deliverable into topic commits for authoring/contracts, atomic
> Server/Agent integration, React integration, and documentation/evidence. The
> separate example-package repository is not part of the Ambari source commit.
> Local verification completed before submission: 136 Java tests in 21 suites,
> 87 React tests and production asset build, 16 Python tooling tests, and 40
> Agent resource/configuration tests. Two whole-store builds produced
> byte-identical archives. Rocky 8 aarch64 live acceptance has since verified
> the core HTTP lifecycle, scoped maintenance, Nginx and PostgreSQL recovery
> paths, official Kyuubi binary and SQL, and browser import/recovery. The
> complete AC-00 through AC-20 matrix remains unfinished: empty-Server browser
> installation, crash/race and interrupted recovery, advanced HDFS parity, and
> database upgrade/offline restore still require validation. See
> docs/mpack/acceptance-results.md and docs/mpack/conclusion-2026-09-26.md for
> exact evidence and limits.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
