Hi Ambari community,
Since Apache Ambari 3.0.0, the community has been working through a broad
modernization effort. Most of the major implementation work is now
complete
on trunk, and I would like to invite the wider community to test the
current
3.1 development baseline.
This is not a formal release announcement. The 3.1.0 documentation is
still
marked as Preview, and release qualification, compatibility testing, and
the
usual Apache release process still need to be completed.
Some of the most significant changes include:
* React is now the primary Ambari Web interface, replacing Ember for the
main
operational and administrative experience. Cluster, host, service,
configuration, alert, Kerberos, upgrade, background-operation, and
administration workflows have been carried forward to the React UI.
* The monitoring architecture has been completely rebuilt. The legacy AMS
Monitor, Collector, and HBase-backed storage path has been replaced by
Agent telemetry endpoints, VMAGENT collection, Prometheus-compatible
scraping and remote write, and VictoriaMetrics time-series storage.
The React UI now provides datasource management, PromQL exploration,
scrape-target visibility, and dashboard management.
* Old third-party Python forks that were maintained inside the Ambari
source
tree have been removed from the runtime dependency model. Ambari now
uses
locked upstream distributions for APScheduler, Jinja2, STOMP/WebSocket,
cryptography, and related libraries. Standard-library APIs replace
simplejson, mock, and the standalone PBKDF2 implementation. Ambari's own
Agent and Server Python code remains part of the project.
* The build baseline has moved to JDK 17 and Maven 3.9.x. Ambari and the
managed Stack can also select separate JDK installations.
* Python ABI selection, RPM contents, dependency provenance, license
checks,
reproducible dependency preparation, and SBOM generation are now
explicit
parts of the packaging process.
* A substantial number of cluster startup, recovery, service lifecycle,
configuration propagation, authentication, sensitive-data handling, and
React workflow issues have also been addressed.
The 3.1.0 preview documentation contains the release notes, upgrade
impact,
new monitoring design, React UI guide, Python runtime contract, RPM
packaging
details, and the reviewed source baseline:
Documentation overview:
https://ambari.apache.org/docs/3.1.0/
Release notes:
https://ambari.apache.org/docs/3.1.0/release-notes
Monitoring architecture:
https://ambari.apache.org/docs/3.1.0/monitoring/architecture
React UI guide:
https://ambari.apache.org/docs/3.1.0/frontend/react-ui
Python runtime:
https://ambari.apache.org/docs/3.1.0/platform/python-runtime
To make testing easier, I have also published a community convenience
image:
https://hub.docker.com/r/jialiangcai/ambari-community
On a Linux x86_64 host with Docker Engine running, a complete demo cluster
can be started with one Docker command:
docker run --rm -it --pull=always \
-v /var/run/docker.sock:/var/run/docker.sock \
-v "$PWD:/workspace" \
-w /workspace \
jialiangcai/ambari-community:latest \
up --nodes 3 --memory 8g
Change --nodes and --memory to match the topology and resources you want
to
test. The default deployment includes ZooKeeper, HDFS, YARN, Hive, HBase,
and the new VictoriaMetrics-based monitoring service.
After deployment, open:
http://127.0.0.1:8080/latest/
The disposable test credentials are admin / admin.
This image is a community testing aid, not an official Apache release
artifact and not a production deployment image. Its Docker Hub page
records
the source revision, platform limitations, lifecycle commands, and cleanup
instructions.
Please test as many workflows as possible, particularly service lifecycle
operations, configurations, alerts, background operations and logs, the
React UI, and the new monitoring dashboards and query path.
If you find a problem, please open a GitHub issue or submit a pull
request:
Issues: https://github.com/apache/ambari/issues
Pull requests: https://github.com/apache/ambari/pulls
You are also welcome to reply on the mailing list or contact me directly
by
email. When reporting a problem, please include the image tag or digest,
host operating system and architecture, the exact command, relevant logs,
and reproduction steps.
Thank you for testing and helping us prepare the next Ambari release.
Best regards,
Jialiang Cai
