THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Status
IMPROVING
Principle
- Minimize user operations for managing and monitoring topologies
- REST Service centralized metadata management
- Consistent UI experience
Objective
- Make sure consistent semantics between the term application (user space) and topology (physical space only)
- Topology should read configuration from TopologyDescService#config instead of configuration file
- Use REST Service as only entry to manage application (START/STOP/HEALTH CHECKING) and ApplicationManager to schedule the task execution and update the execution information
- Eagle UI should support to manage/monitor the application on site/application page
- Single site/application may have more than one topologies (for example hdfsAuditLogMonitoring and userProfileMonitoring should have topologies running separately)
Architecture
To have a better user experience with EAGLE ui, we could provide an interface to manage a certain topology via the ui page, such as submit a topology
Schema
Topology Description Service
- Service name: TopologyDescService
- Table name: eagle_metadata
- Prefix: topology_definition
| Attribute | Type | Description | |
|---|---|---|---|
| tage | topology | String | topology desc name |
| fields | exeClass | String | topology entry class |
| type | String | topology type: build-in topology or main-class topology | |
| config | String | topology config | |
| description | String | description on this topology | |
| version | String | topology version |
Topology Execution Service
- Service name: TopologyExecutionService
- Table name: eagle_metadata
- Prefix: topology_execution
- Description: define the relation between an application and an topology, and maintain the execution status as well
| Attribute | Type | Description | |
|---|---|---|---|
| tags | site | String | topology site |
| application | String | topology application | |
| topology | String | topology desc name | |
| name | String | topology execution name: eagle_${site}_${application}_${topology} | |
| fields | url | String | topology tracking url |
| deploy | String | deploy environment description | |
| status | String | application running status {STARTING, STARTED, STOPPING, STOPPED} | |
| lastUpdateTime | long | last status update time |
Topology Operation Service
| Attribute | Type | Description | |
|---|---|---|---|
| tags | command | String | {START, STOP} |
| topology | String | application name: eagle_${site}_${application}_${topology} | |
| fields | status | String | {INITIALIZED, FAILED, DONE} |
Use Cases in BPMN diagram
1. user define a topology entity
2. user add multiply topologies to an application
3. user start/stop a topology (both push and pull mode provided)
4. Edit topology configuration
5. Periodically check/update topology healthy status
6. Edit deployment cluster?