THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Table of Contents |
---|
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 SiteApplicationEntity#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)
...
Gliffy Diagram | ||||
---|---|---|---|---|
|
Schema
Application
...
Execution Service
- Service name: ApplicationManagementServiceApplicationExecutionService
- Table name: eagle_metadata
- Prefix: application_managementexecution
Attribute | Type | Description | |
---|---|---|---|
tags | site | String | site name |
application | String | application physical topology = ${site}_${application} | |
fields | mainClass | String | application main class |
environment | String | environment name | |
url | String | application tracking url | |
status | String | {SUCCESS, FAILURE} | |
description | String | application description |
...