[VOTE] Release Apache ServiceComb Pack version 0.4.0
Hi All, This is a call for Vote to release Apache ServiceComb Pack version 0.4.0 Release Candidate : https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-pack/0.4.0/rc-01/ Staging Repository : https://repository.apache.org/content/repositories/orgapacheservicecomb-1379 Release Tag : https://github.com/apache/servicecomb-pack/releases/tag/0.4.0 Release CommitID : 32588a3253d5e4573ade849c37eedd371580b1fd Release Notes : https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12344102 Keys to verify the Release Candidate : https://dist.apache.org/repos/dist/dev/servicecomb/KEYS Voting will start now ( Saturday, 30th March, 2019) and will remain open for at-least 72 hours, Request all PMC members to give their vote. [ ] +1 Release this package as 0.4.0 [ ] +0 No Opinion [ ] -1 Do not release this package because On the behalf of ServiceComb Team Mohammad Asif Siddiqui
Re: There are two dependencies which have no License definition in java-chassis
https://github.com/netzwerg/paleo Apache-2.0 https://github.com/bodiam/markdown-to-asciidoc Apache-2.0 maybe can be fixed in: https://github.com/apache/servicecomb-java-chassis/pull/1149 Willem Jiang 于2019年3月29日周五 下午5:56写道： > When I using the maven license plugin to generate the license > information for the java-chassis, I got the following error message: > > [WARNING] There are 2 dependencies with no license : > [WARNING] - ch.netzwerg--paleo-core--0.11.0 > [WARNING] - nl.jworks.markdown_to_asciidoc--markdown_to_asciidoc--1.0 > > We need to fix this issue before cutting java-chassis. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem >
Re: Microsoft Orleans Brings Distributed Transactions to Cloud
I think we could start writing a prototype for it to implement the FSM in Alpha first. I'm not sure about the persistent part, maybe we need to do some research on it. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Mar 29, 2019 at 12:07 PM zhang_...@boco.com.cn wrote: > > Do we need to do some pre-research work on akka? > > E.g. > > 1. fsm > 2. persistence > 3. cluster > > Zhang Lei. > > > > > 在 2019年3月19日，上午11:40，Willem Jiang 写道： > > > > Yeah, it's an exciting news. > > I just found another paper[1] of Phil after went through the news. > > > > Using Akka to rewrite the Alpha server is in my mind for a while. Let > > us go through the papers and find out if there any new work we could > > do in the future version of ServiceComb Pack. > > > > [1]https://www.microsoft.com/en-us/research/wp-content/uploads/2016/10/EldeebBernstein-TransactionalActors-MSR-TR-1.pdf > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Tue, Mar 19, 2019 at 8:46 AM Zheng Feng wrote: > >> > >> https://thenewstack.io/microsoft-orleans-brings-distributed-transactions-to-cloud/ > >> It could be interesting and they used Phil's paper [1]. > >> > >> Regards, > >> Zheng Feng > >> > >> [1] > >> https://www.amazon.com/Concurrency-Control-Recovery-Database-Systems/dp/0201107155 >
There are two dependencies which have no License definition in java-chassis
When I using the maven license plugin to generate the license information for the java-chassis, I got the following error message: [WARNING] There are 2 dependencies with no license : [WARNING] - ch.netzwerg--paleo-core--0.11.0 [WARNING] - nl.jworks.markdown_to_asciidoc--markdown_to_asciidoc--1.0 We need to fix this issue before cutting java-chassis. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem
Re: [PROPOSAL] ServiceComb MetaConfig
sure, mainly forcus on management , ease of use, rollback, key value version control. value validation. first we support API, later UX. bismy 于2019年3月29日周五 下午4:08写道： > Provide a centered configuration management service is very important for > ServiceComb, because all microservice governance functions are based on > dynamic properties. In ServiceComb microservice view, now we currently use > following functions( implement archaius api using apollo and config-center) > > > * pull/push configurations of key-value pair from configuration service. > > > in microservice view, no future functions is needed. So I guess the > suggested service mainly focus on management functions. How do you decide > to provide this functions? Add a management console or by REST api? > > > -- 原始邮件 -- > 发件人: "Xiaoliang Tian"; > 发送时间: 2019年3月29日(星期五) 下午2:14 > 收件人: "dev"; > > 主题: Re: [PROPOSAL] ServiceComb MetaConfig > > > > let's think how we change a timeout for a particular operation? > the key is xxx.usermanagement.user.getuser.timeout, is that key easy to be > manged by operator? I guess he has to learn a special key rule only make > sense in his team > > I want this timeout just be timeout, and easy to read > it bacame timeout(service= usermanagement , schema=user,opertion=getuser) > > Xiaoliang Tian 于2019年3月29日周五 下午12:15写道： > > > > > maybe the name confused，it is a service only for configurations，but the > key contains metadata > > key1: log_level(service=cart, version=1.0, app=mall) > > key2: log_level(service=cart, version=1.0, app=mall, ip=x.x.x.x) > > that is 2 different keys > > > > you can consider apollo has fixed metadata and one fixed view to math > > their own scenario. > > > > but in apollo, key can be very complicated, user can not easily observe > > keys, a lot of metadata will be attacted to key name, just like ip to > > "log_level" > > > > Willem Jiang 于2019年3月29日周五 上午11:36写道： > > > >> Hi Xiaoliang, > >> > >> Do you propose we start a new project to manage the micro services meta > >> datas? > >> Currently we just have a solution to integrate with with Apollo for > >> configuration management, but what's the difference between the > >> service metadata and configuration? > >> I could help us to understand the proposal, if we can drop a clear line > >> for it. > >> > >> > >> Willem Jiang > >> > >> Twitter: willemjiang > >> Weibo: 姜宁willem > >> > >> On Fri, Mar 29, 2019 at 10:52 AM Xiaoliang Tian > >> wrote: > >> > > >> > MetaConfig is a service for configuration management in an large > >> scaled > >> > distrbuted system. > >> > > >> > Currently we use ctrip appllo for config managment, but it is build > for > >> a > >> > paticular scenario. it has fixed schema > >> application,environment,cluster and > >> > namespace. Each key belong to that schema. > >> > > >> > But it is not enough for operator to manage a complicated > >> infrasctructure > >> > or application cluster. > >> > > >> > So here is the proposal to build a brand new config management > service, > >> > > >> > *Features: * > >> > *key with rich metadata: *user can define metadata for a key , that > >> > distinguish from key to another key. a key will not be stringed by > >> fixed > >> > schema. metadata is like "env=test, service=cart, version=1.0" or > >> > "cluster=xxx" or "env=test, service=cart, version=1.0, ip=x.x.x.x" > >> > *validator: *value can be checked by user defined python script, so in > >> > runtine if someone want to change this value, the script will check if > >> this > >> > value is properate. > >> > *encryption webhook: *. value can by ecrypt by your custom encryption > >> > service. > >> > *event producer: *producer will send key changes event to a target > >> > service(kafka,rabbitmq, customed). > >> > *config view: *by setting metadata criteria, MetaConfig will > aggregate a > >> > view to return all key values which match those metadata, so that > >> operator > >> > can mange key in their own understading to a distributed system in > >> > seperated views. > >> > *config batch action: * with metadate, you can batch update, delete > key > >> > values. for example: update all "service=cart version=1.0" > configuration > >> > log level to "DEBUG" or just update "service=cart version=1.0, > >> ip=x.x.x.x" > >> > . > >> > *rich value type: *not ony plain text any more, but support to be > aware > >> of > >> > ini, json,yaml,xml and java properties > >> > *heterogenous configuration system: *able to manage configuration in > k8s > >> > and consul or even more, you can update, delete, and use config view > for > >> > those systems, and you can integrate with your own config system to > >> > MetaConfig by following standardized API and model > >> > >
??????[VOTE] Release Apache ServiceComb Service-Center version 1.2.0
+1 Checks done 1. Release Notes is ok. Some minor improvements suggestion: [SCB-1059] - Bug fixes for v1.1.0 maybe we can list all related bugs. 2. Release Candidate downloaded and tested. -- -- ??: "Mohammad Asif Siddiqui"; : 2019??3??29??(??) 3:35 ??: "dev"; : [VOTE] Release Apache ServiceComb Service-Center version 1.2.0 Hi All, This is a call for a Vote to release Apache ServiceComb Service-Center version 1.2.0 Release Notes : https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12344562 Release Candidate : https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-service-center/1.2.0/rc-01/ Release Tag : https://github.com/apache/servicecomb-service-center/releases/tag/1.2.0 Release CommitID : de7166e156ddb179429e8ac4739562513f95c21d Keys to verify the Release Candidate : https://dist.apache.org/repos/dist/dev/servicecomb/KEYS Guide to build the release from source : https://github.com/apache/servicecomb-service-center/tree/master/scripts/release Voting will start now ( Friday, 29th March, 2019) and will remain open for at-least 72 hours, Request all PMC members to give their vote. [ ] +1 Release this package as 1.2.0 [ ] +0 No Opinion [ ] -1 Do not release this package because On the behalf of ServiceComb Team Mohammad Asif Siddiqui
?????? [PROPOSAL] ServiceComb MetaConfig
Provide a centered configuration management service is very important for ServiceComb, because all microservice governance functions are based on dynamic properties. In ServiceComb microservice view, now we currently use following functions( implement archaius api using apollo and config-center) * pull/push configurations of key-value pair from configuration service. in microservice view, no future functions is needed. So I guess the suggested service mainly focus on management functions. How do you decide to provide this functions? Add a management console or by REST api? -- -- ??: "Xiaoliang Tian"; : 2019??3??29??(??) 2:14 ??: "dev"; : Re: [PROPOSAL] ServiceComb MetaConfig let's think how we change a timeout for a particular operation? the key is xxx.usermanagement.user.getuser.timeout, is that key easy to be manged by operator? I guess he has to learn a special key rule only make sense in his team I want this timeout just be timeout, and easy to read it bacame timeout(service= usermanagement , schema=user,opertion=getuser) Xiaoliang Tian ??2019??3??29?? 12:15?? > > maybe the name confused??it is a service only for configurations??but the key > contains metadata > key1: log_level(service=cart, version=1.0, app=mall) > key2: log_level(service=cart, version=1.0, app=mall, ip=x.x.x.x) > that is 2 different keys > > you can consider apollo has fixed metadata and one fixed view to math > their own scenario. > > but in apollo, key can be very complicated, user can not easily observe > keys, a lot of metadata will be attacted to key name, just like ip to > "log_level" > > Willem Jiang ??2019??3??29?? 11:36?? > >> Hi Xiaoliang, >> >> Do you propose we start a new project to manage the micro services meta >> datas? >> Currently we just have a solution to integrate with with Apollo for >> configuration management, but what's the difference between the >> service metadata and configuration? >> I could help us to understand the proposal, if we can drop a clear line >> for it. >> >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: willem >> >> On Fri, Mar 29, 2019 at 10:52 AM Xiaoliang Tian >> wrote: >> > >> > MetaConfig is a service for configuration management in an large >> scaled >> > distrbuted system. >> > >> > Currently we use ctrip appllo for config managment, but it is build for >> a >> > paticular scenario. it has fixed schema >> application,environment,cluster and >> > namespace. Each key belong to that schema. >> > >> > But it is not enough for operator to manage a complicated >> infrasctructure >> > or application cluster. >> > >> > So here is the proposal to build a brand new config management service, >> > >> > *Features: * >> > *key with rich metadata: *user can define metadata for a key , that >> > distinguish from key to another key. a key will not be stringed by >> fixed >> > schema. metadata is like "env=test, service=cart, version=1.0" or >> > "cluster=xxx" or "env=test, service=cart, version=1.0, ip=x.x.x.x" >> > *validator: *value can be checked by user defined python script, so in >> > runtine if someone want to change this value, the script will check if >> this >> > value is properate. >> > *encryption webhook: *. value can by ecrypt by your custom encryption >> > service. >> > *event producer: *producer will send key changes event to a target >> > service(kafka,rabbitmq, customed). >> > *config view: *by setting metadata criteria, MetaConfig will aggregate a >> > view to return all key values which match those metadata, so that >> operator >> > can mange key in their own understading to a distributed system in >> > seperated views. >> > *config batch action: * with metadate, you can batch update, delete key >> > values. for example: update all "service=cart version=1.0" configuration >> > log level to "DEBUG" or just update "service=cart version=1.0, >> ip=x.x.x.x" >> > . >> > *rich value type: *not ony plain text any more, but support to be aware >> of >> > ini, json,yaml,xml and java properties >> > *heterogenous configuration system: *able to manage configuration in k8s >> > and consul or even more, you can update, delete, and use config view for >> > those systems, and you can integrate with your own config system to >> > MetaConfig by following standardized API and model >> >
[VOTE] Release Apache ServiceComb Service-Center version 1.2.0
Hi All, This is a call for a Vote to release Apache ServiceComb Service-Center version 1.2.0 Release Notes : https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12344562 Release Candidate : https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-service-center/1.2.0/rc-01/ Release Tag : https://github.com/apache/servicecomb-service-center/releases/tag/1.2.0 Release CommitID : de7166e156ddb179429e8ac4739562513f95c21d Keys to verify the Release Candidate : https://dist.apache.org/repos/dist/dev/servicecomb/KEYS Guide to build the release from source : https://github.com/apache/servicecomb-service-center/tree/master/scripts/release Voting will start now ( Friday, 29th March, 2019) and will remain open for at-least 72 hours, Request all PMC members to give their vote. [ ] +1 Release this package as 1.2.0 [ ] +0 No Opinion [ ] -1 Do not release this package because On the behalf of ServiceComb Team Mohammad Asif Siddiqui
Re: [PROPOSAL] ServiceComb MetaConfig
let's think how we change a timeout for a particular operation? the key is xxx.usermanagement.user.getuser.timeout, is that key easy to be manged by operator? I guess he has to learn a special key rule only make sense in his team I want this timeout just be timeout, and easy to read it bacame timeout(service= usermanagement , schema=user,opertion=getuser) Xiaoliang Tian 于2019年3月29日周五 下午12:15写道： > > maybe the name confused，it is a service only for configurations，but the key > contains metadata > key1: log_level(service=cart, version=1.0, app=mall) > key2: log_level(service=cart, version=1.0, app=mall, ip=x.x.x.x) > that is 2 different keys > > you can consider apollo has fixed metadata and one fixed view to math > their own scenario. > > but in apollo, key can be very complicated, user can not easily observe > keys, a lot of metadata will be attacted to key name, just like ip to > "log_level" > > Willem Jiang 于2019年3月29日周五 上午11:36写道： > >> Hi Xiaoliang, >> >> Do you propose we start a new project to manage the micro services meta >> datas? >> Currently we just have a solution to integrate with with Apollo for >> configuration management, but what's the difference between the >> service metadata and configuration? >> I could help us to understand the proposal, if we can drop a clear line >> for it. >> >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> On Fri, Mar 29, 2019 at 10:52 AM Xiaoliang Tian >> wrote: >> > >> > MetaConfig is a service for configuration management in an large >> scaled >> > distrbuted system. >> > >> > Currently we use ctrip appllo for config managment, but it is build for >> a >> > paticular scenario. it has fixed schema >> application,environment,cluster and >> > namespace. Each key belong to that schema. >> > >> > But it is not enough for operator to manage a complicated >> infrasctructure >> > or application cluster. >> > >> > So here is the proposal to build a brand new config management service, >> > >> > *Features: * >> > *key with rich metadata: *user can define metadata for a key , that >> > distinguish from key to another key. a key will not be stringed by >> fixed >> > schema. metadata is like "env=test, service=cart, version=1.0" or >> > "cluster=xxx" or "env=test, service=cart, version=1.0, ip=x.x.x.x" >> > *validator: *value can be checked by user defined python script, so in >> > runtine if someone want to change this value, the script will check if >> this >> > value is properate. >> > *encryption webhook: *. value can by ecrypt by your custom encryption >> > service. >> > *event producer: *producer will send key changes event to a target >> > service(kafka,rabbitmq, customed). >> > *config view: *by setting metadata criteria, MetaConfig will aggregate a >> > view to return all key values which match those metadata, so that >> operator >> > can mange key in their own understading to a distributed system in >> > seperated views. >> > *config batch action: * with metadate, you can batch update, delete key >> > values. for example: update all "service=cart version=1.0" configuration >> > log level to "DEBUG" or just update "service=cart version=1.0, >> ip=x.x.x.x" >> > . >> > *rich value type: *not ony plain text any more, but support to be aware >> of >> > ini, json,yaml,xml and java properties >> > *heterogenous configuration system: *able to manage configuration in k8s >> > and consul or even more, you can update, delete, and use config view for >> > those systems, and you can integrate with your own config system to >> > MetaConfig by following standardized API and model >> >
