THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Ambari supports the concept of Stacks and associated Services in a Stack Definition. By leveraging the Stack Definition, Ambari has a consistent and defined interface to install, manage and monitor a set of Services and provides extensibility model for new Stacks + Services to be introduced.
From Ambari 2.4, there is also support for the concept of Extensions and its associated custom Services in an Extension Definition.
Terminology
| Term | Description |
|---|---|
| Stack | Defines a set of Services and where to obtain the software packages for those Services. A Stack can have one or more versionversions, and each version can be active/inactive. For example, Stack = "HDP-1.3.3". |
| Extension | Defines a set of custom Services which can be added to a stack version. An Extension can have one or more versions. |
| Service | Defines the Components (MASTER, SLAVE, CLIENT) that make up the Service. For example, Service = "HDFS" |
| Component | Defines and The individual Components that adhere to a certain defined lifecycle (start, stop, install, etc). For example, Service = "HDFS" has Components = "NameNode (MASTER)", "Secondary NameNode (MASTER)", "DataNode (SLAVE)" and "HDFS Client (CLIENT)" |
Learn More
In Ambari 1.4.x or earlier, refer to Overview (Ambari 1.4.x or earlier) for more information
- Overview
- How-To Define Stacks and Services
- Custom Services
- Examples: Defining a Custom Service
- Extensions
- Management Packs
- Stack Inheritance
- Stack Properties
- Writing metainfo.xml
- Hooks
- FAQ
In Ambari 1.5.0 or later, refer to Overview (Ambari 1.5.0 or later) for more information