[jira] [Closed] (SCB-1453) [Syncer] New servicecenter plugin supported eureka
[ https://issues.apache.org/jira/browse/SCB-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin closed SCB-1453. --- > [Syncer] New servicecenter plugin supported eureka > -- > > Key: SCB-1453 > URL: https://issues.apache.org/jira/browse/SCB-1453 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Major > Fix For: service-center-1.3.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-1453) [Syncer] New servicecenter plugin supported eureka
[ https://issues.apache.org/jira/browse/SCB-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin resolved SCB-1453. - Resolution: Fixed > [Syncer] New servicecenter plugin supported eureka > -- > > Key: SCB-1453 > URL: https://issues.apache.org/jira/browse/SCB-1453 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Major > Fix For: service-center-1.3.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SCB-1453) [Syncer] New servicecenter plugin supported eureka
[ https://issues.apache.org/jira/browse/SCB-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin reassigned SCB-1453: --- Assignee: Zhinan Lin > [Syncer] New servicecenter plugin supported eureka > -- > > Key: SCB-1453 > URL: https://issues.apache.org/jira/browse/SCB-1453 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Major > Fix For: service-center-1.3.0 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1453) [Syncer] New servicecenter plugin supported eureka
[ https://issues.apache.org/jira/browse/SCB-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin updated SCB-1453: Summary: [Syncer] New servicecenter plugin supported eureka (was: [Syncer] Support servicecenter plugin of eureka ) > [Syncer] New servicecenter plugin supported eureka > -- > > Key: SCB-1453 > URL: https://issues.apache.org/jira/browse/SCB-1453 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Priority: Major > Fix For: service-center-1.3.0 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (SCB-1453) [Syncer] Support servicecenter plugin of eureka
Zhinan Lin created SCB-1453: --- Summary: [Syncer] Support servicecenter plugin of eureka Key: SCB-1453 URL: https://issues.apache.org/jira/browse/SCB-1453 Project: Apache ServiceComb Issue Type: New Feature Components: Service-Center Affects Versions: service-center-1.3.0 Reporter: Zhinan Lin Fix For: service-center-1.3.0 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1302) [Syncer]Refactor data strcture of storage module to support springcloud Eureka.
[ https://issues.apache.org/jira/browse/SCB-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin updated SCB-1302: Issue Type: New Feature (was: Task) > [Syncer]Refactor data strcture of storage module to support springcloud > Eureka. > --- > > Key: SCB-1302 > URL: https://issues.apache.org/jira/browse/SCB-1302 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Major > Fix For: service-center-1.3.0 > > > In order to support SpringCloud Eureka, we should refactor the data > structure of storage module. > Syncer modules except pulgins can only access the intance/ instaceID without > accessing other properties, all processing logic related to other properties > should be enclosed in the servicecenter plugin module. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1303) [Syncer] Support Black and white list management
[ https://issues.apache.org/jira/browse/SCB-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin updated SCB-1303: Issue Type: New Feature (was: Task) > [Syncer] Support Black and white list management > > > Key: SCB-1303 > URL: https://issues.apache.org/jira/browse/SCB-1303 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Major > Fix For: service-center-1.3.0 > > > Black and white list management to be supported from the user request. > The services in the blacklist does not allowed to be synchronized, and the > services in the whitelist allows to be synchronized. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1301) [Syncer] Syncer reliability improvement, support for etcd cluster management
[ https://issues.apache.org/jira/browse/SCB-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin updated SCB-1301: Issue Type: New Feature (was: Task) > [Syncer] Syncer reliability improvement, support for etcd cluster management > > > Key: SCB-1301 > URL: https://issues.apache.org/jira/browse/SCB-1301 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Assignee: chanzhu >Priority: Major > Fix For: service-center-1.3.0 > > > Syncer reliability improvement, support for etcd cluster management. > Each syncer have a cluster of etcd with 3 instances, to improve its > reliability > Etcd elect a syncer instance leader to wirte data to its storage and send > event to notify other syncer, other syncer instances can responsilbe for > reading messages from other syncer's requesst. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1295) Syncer for synchronize data between multiple service centers
[ https://issues.apache.org/jira/browse/SCB-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin resolved SCB-1295. - Resolution: Fixed > Syncer for synchronize data between multiple service centers > > > Key: SCB-1295 > URL: https://issues.apache.org/jira/browse/SCB-1295 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Major > Labels: features > Fix For: service-center-1.3.0 > > Attachments: Service-Center异构-v1.0.pdf > > Time Spent: 10m > Remaining Estimate: 0h > > Add basic minimal runnable version of Syncer, reference to > [README.md|https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/README.md] > to get what is Service-center Syncer. > The current Syner has a P2P network to ensure that different Service-centers > can perform peer-to-peer data synchronization when needed. When data needs to > be synchronized between Service-centers, Syner establishs a point-to-point > channel through GRPC to ensure that the less impact on network load. > I am going to make syncer to support the following capabilities in the coming > PR, > * Support for other service registration and discovery centers, such as > SpringCloud Eureka, Istio, etc. > * Enhance the reliability of the Syner itself, Syner lifecycle management. > Reference to > [TODO.md|https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/TODO.md] > to get future plans for Syncer. > It is worth noting that both Syncer and Service-center are loosely coupled in > the code and there runtime, therefore, Syncer will not affect the current > Service-center. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-1295) Syncer for synchronize data between multiple service centers
[ https://issues.apache.org/jira/browse/SCB-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin closed SCB-1295. --- > Syncer for synchronize data between multiple service centers > > > Key: SCB-1295 > URL: https://issues.apache.org/jira/browse/SCB-1295 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Major > Labels: features > Fix For: service-center-1.3.0 > > Attachments: Service-Center异构-v1.0.pdf > > Time Spent: 10m > Remaining Estimate: 0h > > Add basic minimal runnable version of Syncer, reference to > [README.md|https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/README.md] > to get what is Service-center Syncer. > The current Syner has a P2P network to ensure that different Service-centers > can perform peer-to-peer data synchronization when needed. When data needs to > be synchronized between Service-centers, Syner establishs a point-to-point > channel through GRPC to ensure that the less impact on network load. > I am going to make syncer to support the following capabilities in the coming > PR, > * Support for other service registration and discovery centers, such as > SpringCloud Eureka, Istio, etc. > * Enhance the reliability of the Syner itself, Syner lifecycle management. > Reference to > [TODO.md|https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/TODO.md] > to get future plans for Syncer. > It is worth noting that both Syncer and Service-center are loosely coupled in > the code and there runtime, therefore, Syncer will not affect the current > Service-center. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-1296) [Syncer] Store Syncer data to etcd
[ https://issues.apache.org/jira/browse/SCB-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin closed SCB-1296. --- Resolution: Duplicate > [Syncer] Store Syncer data to etcd > -- > > Key: SCB-1296 > URL: https://issues.apache.org/jira/browse/SCB-1296 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Assignee: chanzhu >Priority: Major > Labels: features > Fix For: service-center-1.3.0 > > > Use etcd to store syncer's data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1307) Store Syncer data to etcd
Zhinan Lin created SCB-1307: --- Summary: Store Syncer data to etcd Key: SCB-1307 URL: https://issues.apache.org/jira/browse/SCB-1307 Project: Apache ServiceComb Issue Type: New Feature Components: Service-Center Affects Versions: service-center-1.3.0 Reporter: Zhinan Lin Assignee: chanzhu Fix For: service-center-1.3.0 Data of syncer now is store in the disk, it should be changed to store to etcd. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-1296) [Syncer] Store Syncer data to etcd
[ https://issues.apache.org/jira/browse/SCB-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852896#comment-16852896 ] Zhinan Lin commented on SCB-1296: - Create a issue to track this, close this sub task. new issue, https://issues.apache.org/jira/browse/SCB-1307 > [Syncer] Store Syncer data to etcd > -- > > Key: SCB-1296 > URL: https://issues.apache.org/jira/browse/SCB-1296 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Assignee: chanzhu >Priority: Major > Labels: features > Fix For: service-center-1.3.0 > > > Use etcd to store syncer's data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1303) [Syncer] Support Black and white list management
Zhinan Lin created SCB-1303: --- Summary: [Syncer] Support Black and white list management Key: SCB-1303 URL: https://issues.apache.org/jira/browse/SCB-1303 Project: Apache ServiceComb Issue Type: Task Components: Service-Center Affects Versions: service-center-1.3.0 Reporter: Zhinan Lin Assignee: Zhinan Lin Fix For: service-center-1.3.0 Black and white list management to be supported from the user request. The services in the blacklist does not allowed to be synchronized, and the services in the whitelist allows to be synchronized. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1296) [Syncer] Store Syncer data to etcd
[ https://issues.apache.org/jira/browse/SCB-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin updated SCB-1296: Summary: [Syncer] Store Syncer data to etcd (was: Store Syncer data to etcd) > [Syncer] Store Syncer data to etcd > -- > > Key: SCB-1296 > URL: https://issues.apache.org/jira/browse/SCB-1296 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Assignee: chanzhu >Priority: Major > Labels: features > Fix For: service-center-1.3.0 > > > Use etcd to store syncer's data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1301) [Syncer] Syncer reliability improvement, support for etcd cluster management
[ https://issues.apache.org/jira/browse/SCB-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin updated SCB-1301: Summary: [Syncer] Syncer reliability improvement, support for etcd cluster management (was: Syncer reliability improvement, support for etcd cluster management) > [Syncer] Syncer reliability improvement, support for etcd cluster management > > > Key: SCB-1301 > URL: https://issues.apache.org/jira/browse/SCB-1301 > Project: Apache ServiceComb > Issue Type: Task > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Assignee: chanzhu >Priority: Major > Fix For: service-center-1.3.0 > > > Syncer reliability improvement, support for etcd cluster management. > Each syncer have a cluster of etcd with 3 instances, to improve its > reliability > Etcd elect a syncer instance leader to wirte data to its storage and send > event to notify other syncer, other syncer instances can responsilbe for > reading messages from other syncer's requesst. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1302) [Syncer]Refactor data strcture of storage module to support springcloud Eureka.
Zhinan Lin created SCB-1302: --- Summary: [Syncer]Refactor data strcture of storage module to support springcloud Eureka. Key: SCB-1302 URL: https://issues.apache.org/jira/browse/SCB-1302 Project: Apache ServiceComb Issue Type: Task Components: Service-Center Affects Versions: service-center-1.3.0 Reporter: Zhinan Lin Assignee: Zhinan Lin Fix For: service-center-1.3.0 In order to support SpringCloud Eureka, we should refactor the data structure of storage module. Syncer modules except pulgins can only access the intance/ instaceID without accessing other properties, all processing logic related to other properties should be enclosed in the servicecenter plugin module. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1301) Syncer reliability improvement, support for etcd cluster management
Zhinan Lin created SCB-1301: --- Summary: Syncer reliability improvement, support for etcd cluster management Key: SCB-1301 URL: https://issues.apache.org/jira/browse/SCB-1301 Project: Apache ServiceComb Issue Type: Task Components: Service-Center Affects Versions: service-center-1.3.0 Reporter: Zhinan Lin Assignee: chanzhu Fix For: service-center-1.3.0 Syncer reliability improvement, support for etcd cluster management. Each syncer have a cluster of etcd with 3 instances, to improve its reliability Etcd elect a syncer instance leader to wirte data to its storage and send event to notify other syncer, other syncer instances can responsilbe for reading messages from other syncer's requesst. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-1296) Store Syncer data to etcd
[ https://issues.apache.org/jira/browse/SCB-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin reassigned SCB-1296: --- Assignee: chanzhu > Store Syncer data to etcd > - > > Key: SCB-1296 > URL: https://issues.apache.org/jira/browse/SCB-1296 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Assignee: chanzhu >Priority: Major > Labels: features > Fix For: service-center-1.3.0 > > > Use etcd to store syncer's data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-1295) Syncer for synchronize data between multiple service centers
[ https://issues.apache.org/jira/browse/SCB-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin reassigned SCB-1295: --- Assignee: Zhinan Lin > Syncer for synchronize data between multiple service centers > > > Key: SCB-1295 > URL: https://issues.apache.org/jira/browse/SCB-1295 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Major > Labels: features > Fix For: service-center-1.3.0 > > Attachments: Service-Center异构-v1.0.pdf > > > Add basic minimal runnable version of Syncer, reference to > [README.md|https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/README.md] > to get what is Service-center Syncer. > The current Syner has a P2P network to ensure that different Service-centers > can perform peer-to-peer data synchronization when needed. When data needs to > be synchronized between Service-centers, Syner establishs a point-to-point > channel through GRPC to ensure that the less impact on network load. > I am going to make syncer to support the following capabilities in the coming > PR, > * Support for other service registration and discovery centers, such as > SpringCloud Eureka, Istio, etc. > * Enhance the reliability of the Syner itself, Syner lifecycle management. > Reference to > [TODO.md|https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/TODO.md] > to get future plans for Syncer. > It is worth noting that both Syncer and Service-center are loosely coupled in > the code and there runtime, therefore, Syncer will not affect the current > Service-center. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1296) Store Syncer data to etcd
Zhinan Lin created SCB-1296: --- Summary: Store Syncer data to etcd Key: SCB-1296 URL: https://issues.apache.org/jira/browse/SCB-1296 Project: Apache ServiceComb Issue Type: Sub-task Components: Service-Center Affects Versions: service-center-1.3.0 Reporter: Zhinan Lin Fix For: service-center-1.3.0 Use etcd to store syncer's data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-1295) Syncer for synchronize data between multiple service centers
[ https://issues.apache.org/jira/browse/SCB-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848863#comment-16848863 ] Zhinan Lin commented on SCB-1295: - I have create a PR to add the basic minimal runnable version [1]. And I am also going to fix some request before merged. [[1]https://github.com/apache/servicecomb-service-center/pull/548|https://github.com/apache/servicecomb-service-center/pull/548] > Syncer for synchronize data between multiple service centers > > > Key: SCB-1295 > URL: https://issues.apache.org/jira/browse/SCB-1295 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Priority: Major > Labels: features > Fix For: service-center-1.3.0 > > Attachments: Service-Center异构-v1.0.pdf > > > Add basic minimal runnable version of Syncer, reference to > [README.md|https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/README.md] > to get what is Service-center Syncer. > The current Syner has a P2P network to ensure that different Service-centers > can perform peer-to-peer data synchronization when needed. When data needs to > be synchronized between Service-centers, Syner establishs a point-to-point > channel through GRPC to ensure that the less impact on network load. > I am going to make syncer to support the following capabilities in the coming > PR, > * Support for other service registration and discovery centers, such as > SpringCloud Eureka, Istio, etc. > * Enhance the reliability of the Syner itself, Syner lifecycle management. > Reference to > [TODO.md|https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/TODO.md] > to get future plans for Syncer. > It is worth noting that both Syncer and Service-center are loosely coupled in > the code and there runtime, therefore, Syncer will not affect the current > Service-center. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1295) Syncer for synchronize data between multiple service centers
Zhinan Lin created SCB-1295: --- Summary: Syncer for synchronize data between multiple service centers Key: SCB-1295 URL: https://issues.apache.org/jira/browse/SCB-1295 Project: Apache ServiceComb Issue Type: New Feature Components: Service-Center Affects Versions: service-center-1.3.0 Reporter: Zhinan Lin Fix For: service-center-1.3.0 Attachments: Service-Center异构-v1.0.pdf Add basic minimal runnable version of Syncer, reference to [README.md|https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/README.md] to get what is Service-center Syncer. The current Syner has a P2P network to ensure that different Service-centers can perform peer-to-peer data synchronization when needed. When data needs to be synchronized between Service-centers, Syner establishs a point-to-point channel through GRPC to ensure that the less impact on network load. I am going to make syncer to support the following capabilities in the coming PR, * Support for other service registration and discovery centers, such as SpringCloud Eureka, Istio, etc. * Enhance the reliability of the Syner itself, Syner lifecycle management. Reference to [TODO.md|https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/TODO.md] to get future plans for Syncer. It is worth noting that both Syncer and Service-center are loosely coupled in the code and there runtime, therefore, Syncer will not affect the current Service-center. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (SCB-1295) Syncer for synchronize data between multiple service centers
[ https://issues.apache.org/jira/browse/SCB-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848863#comment-16848863 ] Zhinan Lin edited comment on SCB-1295 at 5/27/19 11:41 AM: --- I have create a PR to add the basic minimal runnable version [1]. And I am also going to fix some request before merged. [[1]https://github.com/apache/servicecomb-service-center/pull/548 was (Author: zen lin): I have create a PR to add the basic minimal runnable version [1]. And I am also going to fix some request before merged. [[1]https://github.com/apache/servicecomb-service-center/pull/548|https://github.com/apache/servicecomb-service-center/pull/548] > Syncer for synchronize data between multiple service centers > > > Key: SCB-1295 > URL: https://issues.apache.org/jira/browse/SCB-1295 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Zhinan Lin >Priority: Major > Labels: features > Fix For: service-center-1.3.0 > > Attachments: Service-Center异构-v1.0.pdf > > > Add basic minimal runnable version of Syncer, reference to > [README.md|https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/README.md] > to get what is Service-center Syncer. > The current Syner has a P2P network to ensure that different Service-centers > can perform peer-to-peer data synchronization when needed. When data needs to > be synchronized between Service-centers, Syner establishs a point-to-point > channel through GRPC to ensure that the less impact on network load. > I am going to make syncer to support the following capabilities in the coming > PR, > * Support for other service registration and discovery centers, such as > SpringCloud Eureka, Istio, etc. > * Enhance the reliability of the Syner itself, Syner lifecycle management. > Reference to > [TODO.md|https://github.com/zenlint/servicecomb-service-center/blob/master/syncer/TODO.md] > to get future plans for Syncer. > It is worth noting that both Syncer and Service-center are loosely coupled in > the code and there runtime, therefore, Syncer will not affect the current > Service-center. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-608) Add a check list section for verifying the kit to the release guide
[ https://issues.apache.org/jira/browse/SCB-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin reassigned SCB-608: -- Assignee: Yang Bo > Add a check list section for verifying the kit to the release guide > --- > > Key: SCB-608 > URL: https://issues.apache.org/jira/browse/SCB-608 > Project: Apache ServiceComb > Issue Type: Wish > Components: website >Reporter: Zhinan Lin >Assignee: Yang Bo >Priority: Minor > > As mentioned in the dev@ mail list [1], we wish someone that is formiliar > with verifying the release kit to add a check list section to release guide. > [1] > [https://www.mail-archive.com/dev@servicecomb.apache.org/msg04607.html|http://example.com] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-608) Add a check list section for verifying the kit to the release guide
[ https://issues.apache.org/jira/browse/SCB-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16550488#comment-16550488 ] Zhinan Lin commented on SCB-608: [~yangbor] Could you help to report the status?Thanks. > Add a check list section for verifying the kit to the release guide > --- > > Key: SCB-608 > URL: https://issues.apache.org/jira/browse/SCB-608 > Project: Apache ServiceComb > Issue Type: Wish > Components: website >Reporter: Zhinan Lin >Assignee: Yang Bo >Priority: Minor > > As mentioned in the dev@ mail list [1], we wish someone that is formiliar > with verifying the release kit to add a check list section to release guide. > [1] > [https://www.mail-archive.com/dev@servicecomb.apache.org/msg04607.html|http://example.com] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-519) The Website can not be running up according to the chapter "How to run the site locally" of README.md
[ https://issues.apache.org/jira/browse/SCB-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin closed SCB-519. -- > The Website can not be running up according to the chapter "How to run the > site locally" of README.md > -- > > Key: SCB-519 > URL: https://issues.apache.org/jira/browse/SCB-519 > Project: Apache ServiceComb > Issue Type: Bug > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Major > > The Website can not running up if using default version of tools according to > the guide of README.md > # Lack of verison of tools > # Should be non-root -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-524) The images in the blog 'open-design' is not the original version
[ https://issues.apache.org/jira/browse/SCB-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin closed SCB-524. -- > The images in the blog 'open-design' is not the original version > > > Key: SCB-524 > URL: https://issues.apache.org/jira/browse/SCB-524 > Project: Apache ServiceComb > Issue Type: Bug > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Minor > > The images in the blog 'open-design' is not the original version, need to be > replaced. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-609) News of the LC3 Co-Located Event Linked to The Wrong Page
[ https://issues.apache.org/jira/browse/SCB-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin closed SCB-609. -- > News of the LC3 Co-Located Event Linked to The Wrong Page > - > > Key: SCB-609 > URL: https://issues.apache.org/jira/browse/SCB-609 > Project: Apache ServiceComb > Issue Type: Bug > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-609) News of the LC3 Co-Located Event Linked to The Wrong Page
[ https://issues.apache.org/jira/browse/SCB-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin resolved SCB-609. Resolution: Fixed > News of the LC3 Co-Located Event Linked to The Wrong Page > - > > Key: SCB-609 > URL: https://issues.apache.org/jira/browse/SCB-609 > Project: Apache ServiceComb > Issue Type: Bug > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-721) Replace the Users of website to user docs
Zhinan Lin created SCB-721: -- Summary: Replace the Users of website to user docs Key: SCB-721 URL: https://issues.apache.org/jira/browse/SCB-721 Project: Apache ServiceComb Issue Type: Improvement Components: website Reporter: Zhinan Lin As we have renew a user docs in [https://huaweicse.github.io/servicecomb-java-chassis-doc/]. I suggest to replace the user part of website to this docs, my idea is: # Create several items in [http://servicecomb.incubator.apache.org/users/] , each item corresponds to a project, such as java-chassis, saga, servicecenter # Change [https://huaweicse.github.io/servicecomb-java-chassis-doc/] to [https://servicecomb.incubator.apache,org/servicecomb-java-chassis-doc/|https://huaweicse.github.io/servicecomb-java-chassis-doc/] # link [https://servicecomb.incubator.apache,org/servicecomb-java-chassis-doc/|https://huaweicse.github.io/servicecomb-java-chassis-doc/] to the Java-chassis item under [http://servicecomb.incubator.apache.org/users/] If we do it like this way , we also should change user docs of the saga and servicecenter to gitbook to keep the user experience consistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-610) Improvement Blog of easy-build-microservice-system-part-II
Zhinan Lin created SCB-610: -- Summary: Improvement Blog of easy-build-microservice-system-part-II Key: SCB-610 URL: https://issues.apache.org/jira/browse/SCB-610 Project: Apache ServiceComb Issue Type: Wish Components: website Reporter: Zhinan Lin I have gone through the Blog of easy-build-microservice-system-part-II [1], in order to promote the community, create some improvement suggestion I wished here. # I find that there is no place to describe how easily can be by using scaffold. we can describe it by comparing to the old way. For example, if we using the old way, we should first write the POM.xml, and then , something like this, Or the readers will get no feeling about what we want to express. # How about to “Easy Micro Service Series: 5 minutes to Implement customer relationship management”， in Chinese, 轻松微服务系列：5分钟实现客户关系管理, to make title more clear and less confuse. [1] [http://servicecomb.incubator.apache.org/cn/docs/easy-build-microservice-system-part-II/|http://example.com] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-609) News of the LC3 Co-Located Event Linked to The Wrong Page
Zhinan Lin created SCB-609: -- Summary: News of the LC3 Co-Located Event Linked to The Wrong Page Key: SCB-609 URL: https://issues.apache.org/jira/browse/SCB-609 Project: Apache ServiceComb Issue Type: Bug Components: website Reporter: Zhinan Lin Assignee: Zhinan Lin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-606) Keep Information about Apache ServiceComb (incubating) Day Meetup Event on Website
[ https://issues.apache.org/jira/browse/SCB-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin closed SCB-606. -- > Keep Information about Apache ServiceComb (incubating) Day Meetup Event on > Website > -- > > Key: SCB-606 > URL: https://issues.apache.org/jira/browse/SCB-606 > Project: Apache ServiceComb > Issue Type: Wish > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-606) Keep Information about Apache ServiceComb (incubating) Day Meetup Event on Website
[ https://issues.apache.org/jira/browse/SCB-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin resolved SCB-606. Resolution: Fixed > Keep Information about Apache ServiceComb (incubating) Day Meetup Event on > Website > -- > > Key: SCB-606 > URL: https://issues.apache.org/jira/browse/SCB-606 > Project: Apache ServiceComb > Issue Type: Wish > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-608) Add a check list section for verifying the kit to the release guide
Zhinan Lin created SCB-608: -- Summary: Add a check list section for verifying the kit to the release guide Key: SCB-608 URL: https://issues.apache.org/jira/browse/SCB-608 Project: Apache ServiceComb Issue Type: Wish Components: website Reporter: Zhinan Lin As mentioned in the dev@ mail list [1], we wish someone that is formiliar with verifying the release kit to add a check list section to release guide. [1] [https://www.mail-archive.com/dev@servicecomb.apache.org/msg04607.html|http://example.com] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-606) Keep Information about Apache ServiceComb (incubating) Day Meetup Event on Website
Zhinan Lin created SCB-606: -- Summary: Keep Information about Apache ServiceComb (incubating) Day Meetup Event on Website Key: SCB-606 URL: https://issues.apache.org/jira/browse/SCB-606 Project: Apache ServiceComb Issue Type: Wish Components: website Reporter: Zhinan Lin Assignee: Zhinan Lin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-560) Adding "How to use gitter" guide doc in developer guide on the website
[ https://issues.apache.org/jira/browse/SCB-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin closed SCB-560. -- > Adding "How to use gitter" guide doc in developer guide on the website > -- > > Key: SCB-560 > URL: https://issues.apache.org/jira/browse/SCB-560 > Project: Apache ServiceComb > Issue Type: Wish > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-560) Adding "How to use gitter" guide doc in developer guide on the website
[ https://issues.apache.org/jira/browse/SCB-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin resolved SCB-560. Resolution: Fixed The PR is merged, also have promoted it with a public article through wechat > Adding "How to use gitter" guide doc in developer guide on the website > -- > > Key: SCB-560 > URL: https://issues.apache.org/jira/browse/SCB-560 > Project: Apache ServiceComb > Issue Type: Wish > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-560) Adding "How to use gitter" guide doc in developer guide on the website
Zhinan Lin created SCB-560: -- Summary: Adding "How to use gitter" guide doc in developer guide on the website Key: SCB-560 URL: https://issues.apache.org/jira/browse/SCB-560 Project: Apache ServiceComb Issue Type: Wish Components: website Reporter: Zhinan Lin Assignee: Zhinan Lin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-525) It is better to delete logos of Qcon in the Blog 'distributed-transactions-saga-implementation'
[ https://issues.apache.org/jira/browse/SCB-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin closed SCB-525. -- Resolution: Not A Bug It is suitable for Qcon logos because it is a describe of a speech on Qcon. Canceled. > It is better to delete logos of Qcon in the Blog > 'distributed-transactions-saga-implementation' > > > Key: SCB-525 > URL: https://issues.apache.org/jira/browse/SCB-525 > Project: Apache ServiceComb > Issue Type: Wish > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Minor > > It is better to delete logos of Qcon in the Blog > 'distributed-transactions-saga-implementation' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-525) It is better to delete logos of Qcon in the Blog 'distributed-transactions-saga-implementation'
[ https://issues.apache.org/jira/browse/SCB-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16457447#comment-16457447 ] Zhinan Lin commented on SCB-525: It a speech on the Qcon, so it is suitable for the Qcon logos. > It is better to delete logos of Qcon in the Blog > 'distributed-transactions-saga-implementation' > > > Key: SCB-525 > URL: https://issues.apache.org/jira/browse/SCB-525 > Project: Apache ServiceComb > Issue Type: Wish > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Minor > > It is better to delete logos of Qcon in the Blog > 'distributed-transactions-saga-implementation' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-524) The images in the blog 'open-design' is not the original version
[ https://issues.apache.org/jira/browse/SCB-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin resolved SCB-524. Resolution: Fixed > The images in the blog 'open-design' is not the original version > > > Key: SCB-524 > URL: https://issues.apache.org/jira/browse/SCB-524 > Project: Apache ServiceComb > Issue Type: Bug > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Minor > > The images in the blog 'open-design' is not the original version, need to be > replaced. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-525) It is better to delete logos of Qcon in the Blog 'distributed-transactions-saga-implementation'
Zhinan Lin created SCB-525: -- Summary: It is better to delete logos of Qcon in the Blog 'distributed-transactions-saga-implementation' Key: SCB-525 URL: https://issues.apache.org/jira/browse/SCB-525 Project: Apache ServiceComb Issue Type: Wish Components: website Reporter: Zhinan Lin Assignee: Zhinan Lin It is better to delete logos of Qcon in the Blog 'distributed-transactions-saga-implementation' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-524) The images in the blog 'open-design' is not the original version
Zhinan Lin created SCB-524: -- Summary: The images in the blog 'open-design' is not the original version Key: SCB-524 URL: https://issues.apache.org/jira/browse/SCB-524 Project: Apache ServiceComb Issue Type: Bug Components: website Reporter: Zhinan Lin Assignee: Zhinan Lin The images in the blog 'open-design' is not the original version, need to be replaced. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-519) The Website can not be running up according to the chapter "How to run the site locally" of README.md
[ https://issues.apache.org/jira/browse/SCB-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin resolved SCB-519. Resolution: Fixed > The Website can not be running up according to the chapter "How to run the > site locally" of README.md > -- > > Key: SCB-519 > URL: https://issues.apache.org/jira/browse/SCB-519 > Project: Apache ServiceComb > Issue Type: Bug > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Major > > The Website can not running up if using default version of tools according to > the guide of README.md > # Lack of verison of tools > # Should be non-root -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-519) The Website can not be running up according to the chapter "How to run the site locally" of README.md
[ https://issues.apache.org/jira/browse/SCB-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin updated SCB-519: --- Summary: The Website can not be running up according to the chapter "How to run the site locally" of README.md (was: The Website can not be running up if using default version of tools according to the guide of README.md ) > The Website can not be running up according to the chapter "How to run the > site locally" of README.md > -- > > Key: SCB-519 > URL: https://issues.apache.org/jira/browse/SCB-519 > Project: Apache ServiceComb > Issue Type: Bug > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Major > > The Website can not running up if using default version of tools according to > the guide of README.md > # lack of verison of tools > # should be non-root -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-519) The Website can not be running up according to the chapter "How to run the site locally" of README.md
[ https://issues.apache.org/jira/browse/SCB-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin updated SCB-519: --- Description: The Website can not running up if using default version of tools according to the guide of README.md # Lack of verison of tools # Should be non-root was: The Website can not running up if using default version of tools according to the guide of README.md # lack of verison of tools # should be non-root > The Website can not be running up according to the chapter "How to run the > site locally" of README.md > -- > > Key: SCB-519 > URL: https://issues.apache.org/jira/browse/SCB-519 > Project: Apache ServiceComb > Issue Type: Bug > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Major > > The Website can not running up if using default version of tools according to > the guide of README.md > # Lack of verison of tools > # Should be non-root -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-519) The Website can not be running up if using default version of tools according to the guide of README.md
[ https://issues.apache.org/jira/browse/SCB-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin updated SCB-519: --- Summary: The Website can not be running up if using default version of tools according to the guide of README.md (was: The Website can not running up if using default version of tools according to the guide of README.md ) > The Website can not be running up if using default version of tools according > to the guide of README.md > > > Key: SCB-519 > URL: https://issues.apache.org/jira/browse/SCB-519 > Project: Apache ServiceComb > Issue Type: Bug > Components: website >Reporter: Zhinan Lin >Assignee: Zhinan Lin >Priority: Major > > The Website can not running up if using default version of tools according to > the guide of README.md > # lack of verison of tools > # should be non-root -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-519) The Website can not running up if using default version of tools according to the guide of README.md
Zhinan Lin created SCB-519: -- Summary: The Website can not running up if using default version of tools according to the guide of README.md Key: SCB-519 URL: https://issues.apache.org/jira/browse/SCB-519 Project: Apache ServiceComb Issue Type: Bug Components: website Reporter: Zhinan Lin Assignee: Zhinan Lin The Website can not running up if using default version of tools according to the guide of README.md # lack of verison of tools # should be non-root -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-145) For testing JIRA
Zhinan Lin created SCB-145: -- Summary: For testing JIRA Key: SCB-145 URL: https://issues.apache.org/jira/browse/SCB-145 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Affects Versions: java-chassis-1.0.0-m1 Reporter: Zhinan Lin Assignee: Zhinan Lin Fix For: java-chassis-1.0.0-m1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SCB-3) CLA and CCLA submission
[ https://issues.apache.org/jira/browse/SCB-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299758#comment-16299758 ] Zhinan Lin commented on SCB-3: -- test > CLA and CCLA submission > --- > > Key: SCB-3 > URL: https://issues.apache.org/jira/browse/SCB-3 > Project: Apache ServiceComb > Issue Type: Sub-task >Reporter: Willem Jiang >Assignee: Willem Jiang > > Ask the contributor submit the iCLA to Apache > Added the Github PULL_REQUST_Template to guide the contributor to do the PR. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-21) service orchestration
[ https://issues.apache.org/jira/browse/SCB-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin reassigned SCB-21: - Assignee: (was: Zhinan Lin) > service orchestration > - > > Key: SCB-21 > URL: https://issues.apache.org/jira/browse/SCB-21 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: Eric Lee > Attachments: Proposal for integrating ServiceComb into Camel.pdf > > > orchestration of service invocation and aggregation of data from multiple > services based on configured rule > eg. a user request requires calling service a/b/c/d in order: request -> a -> > b -> c -> d -> response > this creates a tight coupling among services a/b/c/d. > better solutions: > request -> aggregator -> response (aggregator calls a/b/c/d in sequence based > on configured rule) > request -> a -> message queue -> b -> queue -> c -> queue -> d > both ways no coupling among the services. > this epic is about solution 1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-21) service orchestration
[ https://issues.apache.org/jira/browse/SCB-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin reassigned SCB-21: - Assignee: Zhinan Lin > service orchestration > - > > Key: SCB-21 > URL: https://issues.apache.org/jira/browse/SCB-21 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: Eric Lee >Assignee: Zhinan Lin > Attachments: Proposal for integrating ServiceComb into Camel.pdf > > > orchestration of service invocation and aggregation of data from multiple > services based on configured rule > eg. a user request requires calling service a/b/c/d in order: request -> a -> > b -> c -> d -> response > this creates a tight coupling among services a/b/c/d. > better solutions: > request -> aggregator -> response (aggregator calls a/b/c/d in sequence based > on configured rule) > request -> a -> message queue -> b -> queue -> c -> queue -> d > both ways no coupling among the services. > this epic is about solution 1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
