AMBARI-26066: Add ambari mpack tools support #3779
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@virajjasani Could you help review this pr? |
|
CI has failed in RAT. @JiaLiangC can you check and update? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
In day-to-day operations, 99% of changes usually occur under the Ambari Stack rather than the Ambari Server itself. In such circumstances, using MPack to solely update the stack's content becomes highly essential. For instance, when updating the Ambari service code in an already existing environment, like the management code for the HDFS service, there's no need for manual distribution or synchronization, just package it into an MPack for the update. While MPacks are convenient, manually packaging an MPack can be cumbersome, hence a tool is proposed to automate the packaging of existing services into an MPack.
How was this patch tested?
manual test
after install the stack mpack ,all service linked to the installed mpack
(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)
Please review Ambari Contributing Guide before opening a pull request.