Why not use consul? There are more advantages then etcd, for example multiple
dc.
-- Original --
From: wjm wjm
Date: Wed,Nov 28,2018 8:34 AM
To: dev
Subject: Re: [Discuss]Adding Etcd as a config center for Java-Chassis
it's better to make huawei config
@Sure
Yes we can use consul. I choose etcd just because service-center already
uses it. Actually, if we go with consul, we can even drop service-center,
as consul provides service registry/discovery and configuration store. We
can keep the schema data as configuration.
I've been suggesting to
+1.
I checked:
- signatures and hashes correct
- LICENSE is fine
- NOTICE is OK
- no unexpected binary files
- source files have headers checked with RAT
- can build the kit from source without any error
- can run the demoes with the staging kit
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
etcd used by service center is not allowed to expose directly to any
client, this etcd only exposed service center. unless you setup isolated
etcd cluster for config management
Yang Bo 于2018年11月28日周三 上午10:08写道：
> @Sure
> Yes we can use consul. I choose etcd just because service-center already
>
+1 binding
Checks done
1. RN is OK
2. check the source and binary release is OK
3. Checkout the released source and integrate to our integration tests and all
tests passed
-- --
??: "Sure";
: 2018??11??28??(??) 10:40
??:
it's better to make huawei config center opensource
after governance opensource, can work with huawei config center directly
Yang Bo 于2018年11月27日周二 下午2:21写道：
> Etcd in itself is good enough to be used as a config center. I don't see
> the need for an extra layer, it reduces performance and adds
If we have plan to open source the config center and governance,
it's could be better we start a discussion here to make a road map.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Wed, Nov 28, 2018 at 8:34 AM wjm wjm wrote:
>
> it's better to make huawei config center opensource
> after
+1
I checked:
1. license is ok
2. demos is work
-- Original --
From: Willem Jiang
Date: Wed,Nov 28,2018 10:37 AM
To: dev
Subject: Re: [VOTE] Release Apache ServiceComb Java-Chassis version 1.1.0
+1.
I checked:
- signatures and hashes correct
- LICENSE is
@Yang Bo
Can you start working on service center opensource? I think it's time for this
task. And there maybe some tasks need to do, like code clean up, licences and
others staffs. I can find one to help you with these works if needed.
I agree with you that servicecomb now seems to be a
@bismy
Do you mean the config-center opensource? Yes I can do that.
On Wed, Nov 28, 2018 at 11:07 AM bismy wrote:
> @Yang Bo
>
>
> Can you start working on service center opensource? I think it's time for
> this task. And there maybe some tasks need to do, like code clean up,
> licences and
+1 binding.
Checks done:
- verified signatures and hashes
- LICENSE is ok
- run demos
Thanks,
Sukesh.
-Original Message-
From: Mohammad Asif Siddiqui [mailto:asifdxtr...@apache.org]
Sent: 27 November 2018 11:38
To: dev@servicecomb.apache.org
Subject: [VOTE] Release Apache ServiceComb
+1 binding
check the source and binary release is OK
run demos is OK
Sukesh A C 于2018年11月28日周三 下午12:19写道：
> +1 binding.
>
> Checks done:
> - verified signatures and hashes
> - LICENSE is ok
> - run demos
>
> Thanks,
> Sukesh.
>
> -Original Message-
> From: Mohammad Asif Siddiqui
12 matches
Mail list logo
