Re: [VOTE] Holding Apache ServiceComb (incubating) Meetup Hosted by Huawei Cloud as a Co-located Event in LC3 2018 Aisa

[李波]

+1

Best!
Li Bo


2018-04-09 13:25 GMT+08:00 Jean-Baptiste Onofré :

> Hi,
>
> it sounds good. Unfortunately, I'm not in the area ;)
>
> I hope next time ;)
>
> Regards
> JB
>
> On 04/08/2018 04:13 PM, Willem Jiang wrote:
> > +1 （Binding）
> >
> >
> > Willem Jiang
> >
> > Blog: http://willemjiang.blogspot.com (English)
> >   http://jnn.iteye.com  (Chinese)
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sun, Apr 8, 2018 at 3:40 PM, Zen Lin 
> wrote:
> >
> >> Hi All,
> >> This is a call for Vote to hold Apache ServiceComb (incubating) Meetup
> >> Hosted by Huawei Cloud as a Co-located Event in LC3 2018 Aisa.
> >>
> >> As discussed in the meetup propersal[1], we have plan to hold Apache
> >> ServiceComb (incubating) Mini Meetup, details are listed bellow,
> >>
> >>
> >>- What is the topic focus of the event?
> >>
> >> Topics are focused on user-pratices/technologies/ecosystem of Apache
> >> ServiceComb (incubating)
> >>
> >>- Who is organising the event?
> >>
> >> PMCs of ServiceComb (incubating) are the organizer
> >>
> >>- When is the event?
> >>
> >>  one day Between Jun 25, 2018 and Jun 27, 2018, maybe in Jun 26, 2018
> >>
> >>- How many attendees are expected?
> >>
> >> 60~100
> >>
> >>- How much PMC involvement is there already?
> >>
> >> 5
> >>
> >>- Which marks are requested?
> >>
> >> Two marks are requested,
> >> 1. Name of "Apache ServiceComb Incubating Meetup Hosted by Huawei Cloud"
> >> 2. "Powered By" Apache Incubator logo of Apache ServiceComb (incubating)
> >>
> >>- Is this for profit or non-profit? (See "Event Profits And
> Donations")?
> >>
> >> non-profit.
> >>
> >>
> >>
> >> [1]  https://www.mail-archive.com/dev@servicecomb.apache.org/
> msg03298.html
> >>
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Proposal for holding a Apache ServiceComb(incubating) mini meetupas a Co-Located Event in LC3 2018

[李波]

+1

this will help developers to know about ServiceComb a lot.

2018-04-03 9:49 GMT+08:00 bismy :

> +1 for holding this kind of event to promote ServiceComb.
>
>
>
>
> -- 原始邮件 --
> 发件人: "Sure";
> 发送时间: 2018年4月3日(星期二) 上午9:43
> 收件人: "dev";
>
> 主题: Re: Proposal for holding a Apache ServiceComb(incubating) mini
> meetupas a Co-Located Event in LC3 2018
>
>
>
> +1
>
>
>
>
> -- Original --
> From: Willem Jiang 
> Date: Mon,Apr 2,2018 9:18 PM
> To: dev 
> Subject: Re: Proposal for holding a Apache ServiceComb(incubating) mini
> meetupas a Co-Located Event in LC3 2018
>
>
>
> +1 for holding this kind of event to promote ServiceComb.
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>   http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Apr 2, 2018 at 7:00 PM, Zen Lin 
> wrote:
>
> > Hi  PMCs of the ServiceComb project,
> >
> > This is a Proposal for holding a Co-Located Event in LC3 2018 to help
> > building ServiceComb's community.
> >
> > My suggestion is to hold a mini meetup of "Apache ServiceComb(incubating)
> > meetup hosted/presented by Huawei PaaS", contents is to share
> > User-practices/ technologies/ecosystem of the project,  maybe, we can
> also
> > invite some  ASF members to share something about ASF governance.
> >
> > As I have gone through the Apache document of small-events[1] , the
> > document instruct me to get approval from the PMCs of the ServiceComb
> > first.
> >  So what about your opinions, please let me know.
> >
> > If agreed, I am going to contact comdev mail list to ask for further
> > details.
> >
> > Thanks.
> >
> > [1]http://community.apache.org/events/small-events.html
> >
>

Re: [VOTE] Release Apache ServiceComb Java-Chassis (incubating) version 1.0.0-m1 - Third Attempt

[李波]

+1

Building kit from source code OK
Running samples OK

2018-03-22 10:51 GMT+08:00 Eric Lee :

> +1
>
> All samples in the kit are passed.
>
> 2018-03-22 10:43 GMT+08:00 kirin wang :
>
> > +1
> > LGTM
> >
> > 2018-03-22 10:42 GMT+08:00 郑扬勇 :
> >
> > > +1 Non Binding
> > >
> > >  Signatures and headers are good.
> > >  Built the code from Release Candidate then check all samples using
> > > Staging Repo.
> > >  Run unit tests and integration tests,all passed.
> > >
> > >
> > >
> > >
> > >  -- Original --
> > >   From:  "Mohammad Asif Siddiqui";
> > >  Date:  Tue, Mar 20, 2018 02:13 PM
> > >  To:  "dev";
> > >
> > >  Subject:  [VOTE] Release Apache ServiceComb Java-Chassis (incubating)
> > > version 1.0.0-m1 - Third Attempt
> > >
> > >
> > >
> > > Hi All,
> > >
> > > This is a call for Vote to release Apache ServiceComb Java-Chassis
> > > (Incubating) version 1.0.0-m1
> > >
> > > Release Notes : https://github.com/apache/incubator-servicecomb-java-
> > > chassis/blob/master/etc/releaseNotes.md
> > >
> > > Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/
> > > servicecomb/incubator-servicecomb-java-chassis/1.0.0-m1/
> > >
> > > Staging Repo : https://repository.apache.org/content/repositories/
> > > orgapacheservicecomb-1196
> > >
> > > Release Tag : https://github.com/apache/incubator-servicecomb-java-
> > > chassis/releases/tag/1.0.0-m1
> > >
> > > Release CommitID : 901869b987c6f65c92b5b8b8f05eaf0f9f6e69cb
> > >
> > > Keys to verify the Release Candidate : https://dist.apache.org/repos/
> > > dist/dev/incubator/servicecomb/KEYS
> > >
> > > Voting will start now ( Tuesday, 20th March, 2018) and will remain open
> > > for next 72 hours, Request all PPMC members to give their vote.
> > >
> > > [ ] +1 Release this package as 1.0.0-m1
> > > [ ] +0 No Opinion
> > > [ ] -1 Do not release this package because
> > >
> > > Regards
> > > Asif
> > >
> >
>

Re: [VOTE] Release Apache ServiceComb Saga (incubating) version 0.1.0 - Second Attempt

[李波]

+1


Checklist:

Build kit from src code success.
Running saga demo booking success
All test were passed.


Best
LiBo



2018-03-19 9:58 GMT+08:00 Eric Lee :

>  +1
>
> Checked the signed keys and checksum.
> Checked the demo.
> Built the code from source.
> All unit tests, integration tests and acceptance tests are passed.
>
> 2018-03-19 9:27 GMT+08:00 Yang Bo :
>
> > +1
> >
> > Checks I've done:
> >
> > 1. Checked sha512sum and GPG signature.
> >
> > 2. Run rat without filter on source and binary package.
> >
> > 3. Checked DISCLAIMER/NOTICE/LICENSE for source and binary package.
> >
> > 4. Checked that no unlicensed binary files are bundled in source and
> binary
> > package.
> >
> > 5. Build from source following README.md
> >
> > 6. Run simple application following the booking demo.
> >
> >
> >
> > On Sat, Mar 17, 2018 at 3:01 AM, Mohammad Asif Siddiqui <
> > asifdxtr...@apache.org> wrote:
> >
> > > Hi All,
> > >
> > > This is a call for Vote to release Apache ServiceComb Saga (Incubating)
> > > version 0.1.0
> > >
> > > Release Notes : https://issues.apache.org/jira/secure/ReleaseNote.jspa
> ?
> > > projectId=12321626=12342353
> > >
> > > Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/
> > > servicecomb/incubator-servicecomb-saga/0.1.0/
> > >
> > > Staging Repo : https://repository.apache.org/content/repositories/
> > > orgapacheservicecomb-1166
> > >
> > > Release Tag : https://github.com/apache/incubator-servicecomb-saga/
> > > releases/tag/0.1.0
> > >
> > > Release CommitID : 708eec092988dfd4a5960ca5f232fb7421d5fbdd
> > >
> > > Keys to verify the Release Candidate : https://dist.apache.org/repos/
> > > dist/dev/incubator/servicecomb/KEYS
> > >
> > > Voting will start now ( Saturday, 17th March, 2018) and will remain
> open
> > > for next 72 hours, Request all PPMC members to give their vote
> > >
> > > [ ] +1 Release this package as 0.1.0
> > > [ ] +0 No Opinion
> > > [ ] -1 Do not release this package because
> > >
> > > Regards
> > > Asif
> > >
> > >
> >
> >
> > --
> > Best Regards,
> > Yang.
> >
>

Re: Prepare to cut the 1.0.0-m1 Release this week

[李波]

Hi,

Please refer to JIRA issue https://issues.apache.org/jira/browse/SCB-274.

2018-01-22 14:58 GMT+08:00 Willem Jiang <willem.ji...@gmail.com>:

> Hi LiBo,
>
> As the Configuration support of Apollo and Configuration Center are quite
> similar, it doesn't make sense that we put these two module into different
> places and have  different configuration codes.
>
> Please file a JIRA for it and start the discussion for it.
>
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>   http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Jan 22, 2018 at 12:55 PM, 李波 <listat...@gmail.com> wrote:
>
> > Dear all,
> >
> > There are two things left for dynamic configuration center:
> > 1.  Configuration item cse.config.client.serverUri in microservice.yaml
> is
> > still in need even using Apollo as configuration center.
> > I'm thinking it's a bad configuration for users while we have
> > apollo.config.serverUri.  It's necessary because there is a check
> condition
> > of cse.config.client.serverUri to decide whether to use configuration
> > center in previous code.
> >
> > Anybody know how to solve this problem elegantly.
> >
> > 2. As Chassis have root module named dynamic-config, we should transfer
> > foundation-config-cc module to dynamic-config too.
> >
> > Best Regards!
> > LiBo
> >
> > 2018-01-22 9:26 GMT+08:00 Willem Jiang <willem.ji...@gmail.com>:
> >
> > > Hi Team，
> > >
> > > As we plan to do the release at end of this month. It's time to do some
> > > preparation now.
> > > Current we just updated the NOTIC file of the java chassis project,  we
> > > should do the same thing on saga and service center projects.
> > >
> > > Please let me if there are some important features need to be finished
> > this
> > > week.
> > >
> > >
> > > Willem Jiang
> > >
> > > Blog: http://willemjiang.blogspot.com (English)
> > >   http://jnn.iteye.com  (Chinese)
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> >
>

Re: Prepare to cut the 1.0.0-m1 Release this week

[李波]

Dear all,

There are two things left for dynamic configuration center:
1.  Configuration item cse.config.client.serverUri in microservice.yaml is
still in need even using Apollo as configuration center.
I'm thinking it's a bad configuration for users while we have
apollo.config.serverUri.  It's necessary because there is a check condition
of cse.config.client.serverUri to decide whether to use configuration
center in previous code.

Anybody know how to solve this problem elegantly.

2. As Chassis have root module named dynamic-config, we should transfer
foundation-config-cc module to dynamic-config too.

Best Regards!
LiBo

2018-01-22 9:26 GMT+08:00 Willem Jiang :

> Hi Team，
>
> As we plan to do the release at end of this month. It's time to do some
> preparation now.
> Current we just updated the NOTIC file of the java chassis project,  we
> should do the same thing on saga and service center projects.
>
> Please let me if there are some important features need to be finished this
> week.
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>   http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>

Re: Dynamic configuration support

[李波]

Dear all,

I propose a architecture to support dynamic configuration for Chaasis.

The detailed design is at the following link:
https://issues.apache.org/jira/secure/attachment/12903770/Dynamic%20Config%20Proposal.pdf

The document explains why we choose Apollo as a centralized configuration
center,
and in order to support modify the configuration items dynamically, we need
to:
1. Implement a driver layer  to support communication with Apollo
2. Start a periodic thread to watch Apollo configurations
3. Refresh the configuration item to Archaius Dynamic Properties

Any comment is welcome!

Best Regards,
Bo Li

2017-12-21 10:56 GMT+08:00 Bin Ma <mabin1...@gmail.com>:

> Hi all,
>
> After the investigation of the config center in the open source community,
> we plan to support communicating with Apollo config center firstly for java
> chassis.
>
>
> Realization of ideas,
>
> 1.To ensure scalability, implement a driver interface layer in the
> foundation-config-cc module, which links the driver instance to open source
> config center.
>
> 2. Refactor the code of communication with cse config center as independent
> driver.
>
> 3. Implement a driver to communicate with Apollo config center. Apollo
> config center provides REST APIs and library two ways to get config data,
> in order to reduce the coupling degree, give priority to using REST APIs
> way, it will be verified next step.
>
>
> next,we will make a demo to verified it.
>
> 2017-12-15 19:13 GMT+08:00 Willem Jiang <willem.ji...@gmail.com>:
>
> > Hi Bo,
> >
> > It's a good feature to support user to change the configuration
> dynamically
> > from a configure server.
> > Please let us know your research result and made a proposal in the
> > community.
> >
> >
> >
> > Willem Jiang
> >
> > Blog: http://willemjiang.blogspot.com (English)
> >   http://jnn.iteye.com  (Chinese)
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Wed, Dec 13, 2017 at 7:58 PM, 李波 <listat...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > We plan to enable dynamic configuration in Java Chassis, After that,
> > > configurations can be changed dynamically without restarting the
> services
> > > any more.
> > >
> > > To do that, we need following steps:
> > >
> > >
> > >- Implement an adapter layer for the configuration server to
> > communicate
> > >with Java Chassis(dynamic configuration based on archaius).
> > >- A user friendly CLI/UI to manage configurations at runtime
> > >- An event store to record users' operations
> > >
> > >
> > > Before that, some researches are needed:
> > >
> > >
> > >- How do other frameworks support dynamic configurations? CSE?
> > >- Which configuration server to choose? Apollo or Disconf?
> > >
> > >
> > >
> > > Best Regards,
> > > Bo Li
> > >
> >
>