Status
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 configuration can be edited on UI
- Use REST Service as only entry to manage application (START/STOP) 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 should could provide an interface to manage a certain topology via the ui page, such as START, STOP, or STATUSsubmit a topology
| Gliffy Diagram |
|---|
| |
|---|
| name | ApplicationTopologyArch |
|---|
|
Schema
Topology
...
Description Service
- Service name: AppManagementServiceTopologyDescriptionService
- Entity: TopologyDescriptionEntity
- Table name: application_definitioneagle_metadata
- Prefix: topologyDescription
| | Attribute | Type | Description |
|---|
| tagstage | sitetopology | String | site topology name |
| fields | exeClass | String | topology entry class |
| | appName | String | application/topology name |
| fields | mainClass | String | application main class |
| | jarFile | String | jar file path |
| | configFile | String | application configuration file path |
| type | String | topology type: DSL or CLASS |
| | description | String | description on this topology |
| | version | String | topology version |
Topology Execution Service
- Service name: TopologyExecutionService
- Entity: TopologyExecutionEntity
- Table name: eagle_metadata
- Prefix: topologyExecution
- 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 | String | |
| fields | fullName | String | topology execution name: eagle_${site}_${application}_${topology} |
| | url | String | topology tracking url |
| | description | String | topology running status description | | deployEnvironment | String | cluster name |
| | status | String | application status: INITIALIZED, RUNING, FAILED, STOPPED |
Cluster Definition
| running status {NEW, STARTING, STOPPING, STARTED, STOPPED} |
| | mode | String | topology running mode: cluster or local |
| | environment | String | topology execution environment, e.g., storm |
| | lastModifiedDate | long | last status update time |
Topology Operation Service
- Service name: TopologyOperationService
- Entity: TopologyOperationEntityService name: ClusterDefinitionService
- Table name: cluster_definitioneagle_metadata
- Prefix: topologyOperation
| | Attribute | Type | Description |
|---|
| tags | nameoperation | Stringcluster name | {START, STOP, STATUS} |
| | typesite | String | e.g., storm, spark |
| | configapplication | String | json | cluster config
| |
...
...
...
...
...
- NEW
- create a topology definition entity, whose initial status is INITIALIZED
- START
- choose the deployed cluster
- click START button, and after updating the status to STARTING, a new thread is created to execute the submitting topology task
- STOP
- click STOP button
| String | topology name: ${topology} |
| fields | status | String | {INITIALIZED, PENDING, FAILED, SUCCESS} |
| | message | String | exception message |
| | lastModifiedDate | long | last status update time |
Customized Restful Apis
| HTTP Method | URL | Payload | Description |
|---|
| POST | /app/operation | TopologyOperationEntity | create an topology operation |
| DELETE | /app/topology/{topology} | | delete a topology description |
...
