THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Gliffy Diagram | ||||
---|---|---|---|---|
|
Schema
Application
...
Definition Service
- Service name: ApplicationManagementServiceTopologyDescService
- Table name: eagle_metadata
- Prefix: applicationtopology_executiondefinition
Attribute | Type | Description | |
---|---|---|---|
tags | site | String | site name |
application | String | application physical topology name = ${site}_${application} | |
? | nametopology | String | application physical name, maybe feature or something elsetopology name |
fields | mainClass | String | application main class |
String | topology type: build-in topology or main-class topology | ||
String | topology config | ||
statusUrl | String | application tracking url | |
status | String | {SUCCESS, FAILURE} | |
statusDescription | String | application description |
...
description | String | description on this topology |
Application Execution Service
- Service name: ApplicationEnvironmentServiceApplicationExecutionService
- Table name: eagleeagle_metadata
- Prefix: application_environmentexecution
Attribute | Type | Description | ||
---|---|---|---|---|
tags | application | String | application name = ${site}_${application} | |
fields | String | application tracking url | ||
String | cluster | configname | ||
localStatus | String | application running status {INITIALIZED, STARTING, STARTED, STOPPING, STOPPED} |
Use cases
- NEW
- create a topology definition entity
- START
- click START button
- check the topology's current status on the nimbus host
- a new thread is created to execute the submitting topology task
- update status
- STOP
- click STOP button
- check the topology's current status on nimbus host
- a new thread is created to stop the topology
- update status