THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Services should provide the main metainfo.xml file which provides important metadata about the service.
Apart from that, other files can be provided to give more information about the service. More details about these files are provided below.
...
Complete reference can be found in the Writing metainfo.xml page.
A good reference implementation is the HDFS metainfo.xml.
Question: Is it possible to define multiple services in the same metainfo.xml?
Yes. Though it is possible, it is discouraged to define multiple services in the same service folder.
YARN and MapReduce2 are services that are defined together in the YARN folder. Its metainfo.xml defines both services.
Scripts
With the components defined, we need to provide scripts which can handle the various stages of the service and component's lifecycle.
The scripts necessary to manage service and components are specified in the metainfo.xml (HDFS)
These scripts should be provided in the <service-id>/<service-version>/package/scripts folder.
| Folder | Purpose |
|---|---|
| package/scripts | Contains scripts invoked by Ambari. These scripts are loaded into the execution path with the correct environment |
| package/files | Contains files used by above scripts. Generally these are other scripts (bash, python, etc.) invoked as a separate process. Example: checkWebUI.py (HDFS) |
| package/templates | Template files used by above scripts to generate files on managed hosts. These are generally configuration files required by the service to operate. |
Hooks
Configuration
Files
Alerts
...