kimmking commented on issue #6653:
URL: https://github.com/apache/shardingsphere/issues/6653#issuecomment-680758436


   According our disscussion about Orchestration&Control-Panel module, cluster 
module should be pending for the next version release, and observablity module 
should be an independent project, so we adjust them now.
   
   ### Phase 0--prepare 
   
   - [x] create branch orchestration-dev for shardingsphere&shardingsphere-ui  
@kimmking 
   
   ### Phase 1--adjust cluster
   
   - [ ] delete cluster in shardingsphere module @kimmking 
   - [ ] delete cluster in shardingsphere-ui module @menghaoranss 
   - [ ] delete cluster in all configurations @kimmking 
   - [ ] revise document for cluster @menghaoranss 
   - [ ] revise examples for cluster @menghaoranss 
   
   ### Phase 2--adjust observablity 
   
   - [ ] move metrics and opentracing module to independent project 
observablity @kimmking 
   - [ ] delete all metrics configurations @menghaoranss 
   - [ ] revise document for cluster @menghaoranss
   - [ ] make an investigation with sw-agent for metrics @yu199195 
   - [ ] integration with sw-agent for metrics @yu199195 
   - [ ] remove all references for metrics @yu199195 
   - [ ] revise examples for metrics @menghaoranss 
   
   ### Phase 3--adjust orchestration
   
   - [ ] move orchestration  module to a level 1 sub-project named governance 
@kimmking 
   - [ ] adjust all related name for governance instead of orchestration 
@kimmking 
   - [ ] adjust all related docs for governance instead of orchestration 
@kimmking 
   - [ ] adjust all related ui for governance instead of orchestration 
@menghaoranss 
   - [ ] adjust all related examples for governance instead of orchestration 
@menghaoranss 
   
   ### Phase 4--adjust API&SPI
   
   This phase will be pending for uniforming scaling & cluster configurations 
via an abstract configuration.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to