You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 33 Next »

Principle

  • Minimize user operations for managing and monitoring topologies
  • REST Service centralized metadata management
  • Consistent UI experience

Objective

  1. Make sure consistent semantics between the term application (user space) and topology (physical space only)
  2. Topology should read configuration from SiteApplicationEntity#config instead of configuration file
  3. 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 
  4. Eagle UI should support to manage/monitor the application on site/application page
  5. 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

 

topologyManage

Schema

Topology Description Service

  • Service name: TopologyDescService
  • Table name: eagle_metadata
  • Prefix: topology_definition
 AttributeTypeDescription
tagetopologyStringtopology desc name
fieldsmainClassStringapplication main class
 typeStringtopology type: build-in topology or main-class topology
 configStringtopology config
 descriptionStringdescription on this topology
 versionStringtopology version

Topology Execution Service 

  • Service name: TopologyExecutionService
  • Table name: eagle_metadata
  • Prefix: topology_execution
 AttributeTypeDescription
tagssiteStringtopology site
 applicationStringtopology application
 topologyStringtopology desc name
 nameStringtopology execution name: eagle_${site}_${application}_${topology}
fieldsurlStringtopology tracking url
 deployStringdeploy environment description
 statusStringapplication running status {INITIALIZED, STARTING, STARTED, STOPPING, STOPPED}
 lastUpdateTimelonglast status update time

Topology Operation Service

Three use cases in BPMN diagram

  • user create a topology entity 

DefinitionTopologyBPMN

  • user add multiply topologies to an application

addApplicationTopologyBPMN

  • user start a start/stop a topology (both push and pull mode provided)

operationExecutionBPMN

 

  • No labels