date:20180524

[incubator-servicecomb-docs] branch master updated (73313f5 -> 15a21ea)

2018-05-24 Thread liubao

This is an automated email from the ASF dual-hosted git repository.

liubao pushed a change to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-docs.git.


from 73313f5  [SCB-585]Add reference guide for java chassis, initial commit 
including folder structures and zh_CN docs
 add c66f0df  [SCB-585]add README.md for this project
 new 15a21ea  Merge pull request #1 from liubao68/readme

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 README.md|  5 +
 java-chassis-reference/README.md | 33 +
 2 files changed, 38 insertions(+)
 create mode 100644 README.md
 create mode 100644 java-chassis-reference/README.md

-- 
To stop receiving notification emails like this one, please contact
liu...@apache.org.

[GitHub] liubao68 opened a new pull request #2: 修改启用HTTP2的错误， h2应该为http2

2018-05-24 Thread GitBox

liubao68 opened a new pull request #2:  修改启用HTTP2的错误， h2应该为http2
URL: https://github.com/apache/incubator-servicecomb-docs/pull/2
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[incubator-servicecomb-docs] 01/01: Merge pull request #1 from liubao68/readme

2018-05-24 Thread liubao

This is an automated email from the ASF dual-hosted git repository.

liubao pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-servicecomb-docs.git

commit 15a21ea41522562e67e2650c845c24ddc665cece
Merge: 73313f5 c66f0df
Author: bao liu 
AuthorDate: Fri May 25 11:34:50 2018 +0800

Merge pull request #1 from liubao68/readme

[SCB-585]add README.md for this project

 README.md|  5 +
 java-chassis-reference/README.md | 33 +
 2 files changed, 38 insertions(+)

-- 
To stop receiving notification emails like this one, please contact
liu...@apache.org.

[GitHub] liubao68 closed pull request #1: [SCB-585]add README.md for this project

2018-05-24 Thread GitBox

liubao68 closed pull request #1: [SCB-585]add README.md for this project
URL: https://github.com/apache/incubator-servicecomb-docs/pull/1
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/README.md b/README.md
new file mode 100644
index 000..06095de
--- /dev/null
+++ b/README.md
@@ -0,0 +1,5 @@
+# ServiceComb Documents
+This project hosts ServiceComb documents, please check individual sub folders 
for details.
+
+# ServiceComb资料开发项目
+本项目是ServiceComb各个组件的开发文档源码，请查看各个子目录获取详细的说明。
diff --git a/java-chassis-reference/README.md b/java-chassis-reference/README.md
new file mode 100644
index 000..98ba558
--- /dev/null
+++ b/java-chassis-reference/README.md
@@ -0,0 +1,33 @@
+
+## 本项目是servicecomb-java-chassis开发指南。
+
+* [访问地址](https://huaweicse.github.io/servicecomb-java-chassis-doc)（临时）
+
+* 编辑  
+  1. Fork本项目代码  
+  2. 方式一：直接编辑md源码  
+  3. 方式二：下载[GitBook Editor](https://legacy.gitbook.com/editor)编辑  
+  4. 提交PR
+
+* 发布/查看  
+  1. 
参考[GitBook安装指南](https://github.com/GitbookIO/gitbook/blob/master/docs/setup.md),安装gitbook
  
+  2. 发布：gitbook build . ../docs
+  3. 本地查看：gitbook serve . ../docs
+
+## This project is the servicecomb-java-chassis developers guide
+
+* [Web 
address](https://huaweicse.github.io/servicecomb-java-chassis-doc)(temporary)
+
+* Submit PR  
+  1. Fork this project  
+  2. Edit md source file, or  
+  3. Edit using [GitBook Editor](https://legacy.gitbook.com/editor)  
+  4. Submit PR
+
+* Publish  
+  1. see [GitBook installation 
guide](https://github.com/GitbookIO/gitbook/blob/master/docs/setup.md)  
+  2. publish using command：gitbook build . ../docs
+  3. for local reading：gitbook serve . ../docs
+
+
+


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] wujimin opened a new pull request #728: [SCB-589] Consumer producer upgrade unordered

2018-05-24 Thread GitBox

wujimin opened a new pull request #728:  [SCB-589] Consumer producer upgrade 
unordered
URL: https://github.com/apache/incubator-servicecomb-java-chassis/pull/728
 
 
   1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge
   2.consumer microserviceMeta will not save in microserviceMetaManager any 
more, just like edge, use appManager; and change consumer default versionRule 
from latest to all
   3.allow consumer schema set or method set bigger than contract
   4.protobuf dynamic class created in microservice classloader
   
   integration test case:
   1.start old producer
   2.start new consumer, which have new schems or new method belongs to old 
schema
 features about old producer no problem
   3.start new producer
 not restart consumer, features about new producer become no problem
 
   
   All commits are logically related, difficult to split to subtasks
   please review commits one by one.
   
   there is no automatic integration test case, because need a controller to do 
this,  our integration test not support this now.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[incubator-servicecomb-website] 01/02: merge the master branch

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch asf-site
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit df540022a559a903c42f4baaf514b20188ad8a4e
Merge: d9e1f5a af93917
Author: Willem Jiang 
AuthorDate: Thu May 24 21:50:38 2018 +0800

merge the master branch

 _pages/cn/home.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] 02/02: Publish the website

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch asf-site
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit d4b2b6b328b2ca815f7c45ba66a8fad02fd62496
Author: Willem Jiang 
AuthorDate: Thu May 24 21:51:47 2018 +0800

Publish the website
---
 content/cn/index.html | 2 +-
 content/feed.xml  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/cn/index.html b/content/cn/index.html
index 52fa134..d3c5191 100644
--- a/content/cn/index.html
+++ b/content/cn/index.html
@@ -293,7 +293,7 @@
   
 
   最新新闻
-  微服务 Meetup：Apache 
ServiceComb (incubating) Day   ServiceComb 
第一个Apache孵化版本发布了！   号外：现在ServiceComb提供了微服务场景下的数据一致性解决方案Saga！
  
+  微服务 
Meetup：Apache ServiceComb (incubating) Day   ServiceComb 第一个Apache孵化版本发布了！   号外：现在ServiceComb提供了微服务场景下的数据一致性解决方案Saga！
  
 
 
   
diff --git a/content/feed.xml b/content/feed.xml
index 92187fe..4beefbf 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -1,4 +1,4 @@
-http://www.w3.org/2005/Atom; >https://jekyllrb.com/; 
version="3.4.3">Jekyll2018-05-24T15:04:54+08:00/Apache ServiceComb (incubating)The homepage of 
ServiceComb{name=nil, 
avatar= [...]
+http://www.w3.org/2005/Atom; >https://jekyllrb.com/; 
version="3.4.3">Jekyll2018-05-24T21:50:48+08:00/Apache ServiceComb (incubating)The homepage of 
ServiceComb{name=nil, 
avatar= [...]
 p在前一篇博文a 
href=http://servicecomb.incubator.apache.org/cn/docs/easy-build-microservice-system-part-I/《轻松微服务系列：从一键构建微服务和DDD设计开始》/a，我们已经详细介绍了如何快速构建微服务和DDD相关概念，并引入了一个经典场景——地产CRM。通过a
 href=https://en.wikipedia.org/wiki/Event_stormingEvent 
Storming/a实践获得了系统设计：/p
 
 pimg 
src=/assets/images/scaffold/MicroserviceDesign4.png 
alt=MicroserviceDesign4 //p

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] branch asf-site updated (d9e1f5a -> d4b2b6b)

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a change to branch asf-site
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git.


from d9e1f5a  Publish the website
 add 938b701  Update the home page formate
 add af93917  fix bug of reference from chinese home page to blog of Apache 
ServiceComb (incubating) Day
 new df54002  merge the master branch
 new d4b2b6b  Publish the website

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 _pages/cn/home.md | 2 +-
 content/cn/index.html | 2 +-
 content/feed.xml  | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] branch master updated: fix bug of reference from chinese home page to blog of Apache ServiceComb (incubating) Day

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git


The following commit(s) were added to refs/heads/master by this push:
 new af93917  fix bug of reference from chinese home page to blog of Apache 
ServiceComb (incubating) Day
af93917 is described below

commit af9391750b9a0b7fe9640fe0186d420fa8946f0c
Author: linzhinan 
AuthorDate: Thu May 24 17:30:38 2018 +0800

fix bug of reference from chinese home page to blog of Apache ServiceComb 
(incubating) Day

Signed-off-by: linzhinan 
---
 _pages/cn/home.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_pages/cn/home.md b/_pages/cn/home.md
index ae9830c..0cc7aed 100644
--- a/_pages/cn/home.md
+++ b/_pages/cn/home.md
@@ -22,7 +22,7 @@ intro:
 
 
   
- 微服务 Meetup：Apache 
ServiceComb (incubating) Day
+ 微服务 Meetup：Apache 
ServiceComb (incubating) Day
   
   
 ServiceComb 第一个Apache孵化版本发布了！

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[GitHub] WillemJiang closed pull request #94: [SCB-609] Fix bug of reference from chinese home page to blog of Apache Service…

2018-05-24 Thread GitBox

WillemJiang closed pull request #94: [SCB-609] Fix bug of reference from 
chinese home page to blog of Apache Service…
URL: https://github.com/apache/incubator-servicecomb-website/pull/94
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/_pages/cn/home.md b/_pages/cn/home.md
index ae9830c..0cc7aed 100644
--- a/_pages/cn/home.md
+++ b/_pages/cn/home.md
@@ -22,7 +22,7 @@ intro:
 
 
   
- 微服务 Meetup：Apache 
ServiceComb (incubating) Day
+ 微服务 Meetup：Apache 
ServiceComb (incubating) Day
   
   
 ServiceComb 第一个Apache孵化版本发布了！


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] coveralls commented on issue #727: [SCB-607] Accesslog support invocation context item

2018-05-24 Thread GitBox

coveralls commented on issue #727: [SCB-607] Accesslog support invocation 
context item
URL: 
https://github.com/apache/incubator-servicecomb-java-chassis/pull/727#issuecomment-391718562
 
 
   
   [![Coverage 
Status](https://coveralls.io/builds/17147271/badge)](https://coveralls.io/builds/17147271)
   
   Coverage increased (+0.009%) to 87.5% when pulling 
**80f4e3362664f6598efcb30728cd16d56bb37a1e on 
yhs0092:accesslog_support_invocation_context_item** into 
**f1415fe328c321fcd82c81cacb11166571d8a172 on apache:master**.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] yhs0092 opened a new pull request #727: [SCB-607] Accesslog support invocation context item

2018-05-24 Thread GitBox

yhs0092 opened a new pull request #727: [SCB-607] Accesslog support invocation 
context item
URL: https://github.com/apache/incubator-servicecomb-java-chassis/pull/727
 
 
   Follow this checklist to help us incorporate your contribution quickly and 
easily:
   
- [ ] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/SCB) filed for the change (usually 
before you start working on it).  Trivial changes like typos do not require a 
JIRA issue.  Your pull request should address just this issue, without pulling 
in other changes.
- [ ] Each commit in the pull request should have a meaningful subject line 
and body.
- [ ] Format the pull request title like `[SCB-XXX] Fixes bug in 
ApproximateQuantiles`, where you replace `SCB-XXX` with the appropriate JIRA 
issue.
- [ ] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
- [ ] Run `mvn clean install` to make sure basic checks pass. A more 
thorough check will be performed on your pull request automatically.
- [ ] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   ---
   See details in [SCB-607](https://issues.apache.org/jira/browse/SCB-607)
   
   - set Invocation into RoutingContext
   - add an AccessLogItem to get content from invocation context


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] liubao68 opened a new pull request #726: [SCB-611]Provide a default Dispatcher to make user using edge service easier

2018-05-24 Thread GitBox

liubao68 opened a new pull request #726: [SCB-611]Provide a default Dispatcher 
to make user using edge service easier
URL: https://github.com/apache/incubator-servicecomb-java-chassis/pull/726
 
 
   
   Follow this checklist to help us incorporate your contribution quickly and 
easily:
   
- [ ] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/SCB) filed for the change (usually 
before you start working on it).  Trivial changes like typos do not require a 
JIRA issue.  Your pull request should address just this issue, without pulling 
in other changes.
- [ ] Each commit in the pull request should have a meaningful subject line 
and body.
- [ ] Format the pull request title like `[SCB-XXX] Fixes bug in 
ApproximateQuantiles`, where you replace `SCB-XXX` with the appropriate JIRA 
issue.
- [ ] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
- [ ] Run `mvn clean install` to make sure basic checks pass. A more 
thorough check will be performed on your pull request automatically.
- [ ] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   ---
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] highosimida opened a new issue #725: 使用容器部署，注册中心获取到的是容器内的IP

2018-05-24 Thread GitBox

highosimida opened a new issue #725: 使用容器部署，注册中心获取到的是容器内的IP
URL: https://github.com/apache/incubator-servicecomb-java-chassis/issues/725
 
 
   如题，把微服务放入 docker 容器后，能在服务中心注册上， 但是注册的 endpoint 确是 docker 的内网网址如 
highway://172.30.28.4:7070?login=true，而不是宿主机器的，如何注册成宿主机器的。


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[incubator-servicecomb-website] 01/03: Merge branch 'master' into asf-site

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch asf-site
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit 93fcc3d973ed0b438dd29f0205315fa0d0da02fc
Merge: 94ddd87 0708112
Author: Willem Jiang 
AuthorDate: Thu May 24 14:55:45 2018 +0800

Merge branch 'master' into asf-site

 _pages/home.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] 03/03: Publish the website

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch asf-site
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit d9e1f5ad171f25a0ee7bae57488ddf0f36d9ba80
Author: Willem Jiang 
AuthorDate: Thu May 24 15:06:40 2018 +0800

Publish the website
---
 content/cn/index.html | 3 +--
 content/feed.xml  | 2 +-
 content/index.html| 3 +--
 3 files changed, 3 insertions(+), 5 deletions(-)

diff --git a/content/cn/index.html b/content/cn/index.html
index 90c6d34..52fa134 100644
--- a/content/cn/index.html
+++ b/content/cn/index.html
@@ -293,8 +293,7 @@
   
 
   最新新闻
-  微服务 Meetup：Apache 
ServiceComb (incubating) Day   ServiceComb 
第一个Apache孵化版本发布了！   号外：现在ServiceComb提供了微服务场景下的数据一致性解决方案Saga！
  /ul
-
+  微服务 Meetup：Apache 
ServiceComb (incubating) Day   ServiceComb 
第一个Apache孵化版本发布了！   号外：现在ServiceComb提供了微服务场景下的数据一致性解决方案Saga！
  
 
 
   
diff --git a/content/feed.xml b/content/feed.xml
index 4a0f044..92187fe 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -1,4 +1,4 @@
-http://www.w3.org/2005/Atom; >https://jekyllrb.com/; 
version="3.4.3">Jekyll2018-05-24T14:50:06+08:00/Apache ServiceComb (incubating)The homepage of 
ServiceComb{name=nil, 
avatar= [...]
+http://www.w3.org/2005/Atom; >https://jekyllrb.com/; 
version="3.4.3">Jekyll2018-05-24T15:04:54+08:00/Apache ServiceComb (incubating)The homepage of 
ServiceComb{name=nil, 
avatar= [...]
 p在前一篇博文a 
href=http://servicecomb.incubator.apache.org/cn/docs/easy-build-microservice-system-part-I/《轻松微服务系列：从一键构建微服务和DDD设计开始》/a，我们已经详细介绍了如何快速构建微服务和DDD相关概念，并引入了一个经典场景——地产CRM。通过a
 href=https://en.wikipedia.org/wiki/Event_stormingEvent 
Storming/a实践获得了系统设计：/p
 
 pimg 
src=/assets/images/scaffold/MicroserviceDesign4.png 
alt=MicroserviceDesign4 //p
diff --git a/content/index.html b/content/index.html
index 87ca93a..b76d60f 100644
--- a/content/index.html
+++ b/content/index.html
@@ -291,8 +291,7 @@
   
 
   Latest News
-  Microservice 
Meetup: Apache ServiceComb (incubating) Day   ServiceComb announces it's first Apache Incubating Release to 
the community.   ServiceComb now provides data 
consistency solutions(Saga) in microservice application.  /ul
-
+  Microservice 
Meetup: Apache ServiceComb (incubating) Day   ServiceComb announces it's first Apache Incubating Release to 
the community.   ServiceComb now provides data 
consistency solutions(Saga) in microservice application.  
 
 
   

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] 02/03: Update the home page formate

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch asf-site
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit 6f544e69f60cd468c22fa93b9338b74640ccf1a9
Author: Willem Jiang 
AuthorDate: Thu May 24 15:06:13 2018 +0800

Update the home page formate
---
 _pages/cn/home.md | 4 ++--
 _pages/home.md| 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/_pages/cn/home.md b/_pages/cn/home.md
index 3de164e..ae9830c 100644
--- a/_pages/cn/home.md
+++ b/_pages/cn/home.md
@@ -22,8 +22,8 @@ intro:
 
 
   
- 微服务 Meetup：Apache 
ServiceComb (incubating) Day
-  
+ 微服务 Meetup：Apache 
ServiceComb (incubating) Day
+  
   
 ServiceComb 第一个Apache孵化版本发布了！
   
diff --git a/_pages/home.md b/_pages/home.md
index 8220290..115e140 100644
--- a/_pages/home.md
+++ b/_pages/home.md
@@ -21,7 +21,7 @@ intro:
 
 
   
- Microservice Meetup: 
Apache ServiceComb (incubating) Day
+ Microservice Meetup: 
Apache ServiceComb (incubating) Day
   
   
   ServiceComb announces it's first Apache Incubating 
Release to the community.

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] branch asf-site updated (94ddd87 -> d9e1f5a)

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a change to branch asf-site
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git.


from 94ddd87  publish the website
 add 0708112  Update the format error of home page
 new 93fcc3d  Merge branch 'master' into asf-site
 new 6f544e6  Update the home page formate
 new d9e1f5a  Publish the website

The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 _pages/cn/home.md | 4 ++--
 _pages/home.md| 4 ++--
 content/cn/index.html | 3 +--
 content/feed.xml  | 2 +-
 content/index.html| 3 +--
 5 files changed, 7 insertions(+), 9 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] branch master updated: Update the home page formate

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git


The following commit(s) were added to refs/heads/master by this push:
 new 938b701  Update the home page formate
938b701 is described below

commit 938b70167cd092fb20ec2343af266bfead6ac74c
Author: Willem Jiang 
AuthorDate: Thu May 24 15:06:13 2018 +0800

Update the home page formate
---
 _pages/cn/home.md | 4 ++--
 _pages/home.md| 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/_pages/cn/home.md b/_pages/cn/home.md
index 3de164e..ae9830c 100644
--- a/_pages/cn/home.md
+++ b/_pages/cn/home.md
@@ -22,8 +22,8 @@ intro:
 
 
   
- 微服务 Meetup：Apache 
ServiceComb (incubating) Day
-  
+ 微服务 Meetup：Apache 
ServiceComb (incubating) Day
+  
   
 ServiceComb 第一个Apache孵化版本发布了！
   
diff --git a/_pages/home.md b/_pages/home.md
index 8220290..115e140 100644
--- a/_pages/home.md
+++ b/_pages/home.md
@@ -21,7 +21,7 @@ intro:
 
 
   
- Microservice Meetup: 
Apache ServiceComb (incubating) Day
+ Microservice Meetup: 
Apache ServiceComb (incubating) Day
   
   
   ServiceComb announces it's first Apache Incubating 
Release to the community.

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] branch master updated: Update the format error of home page

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git


The following commit(s) were added to refs/heads/master by this push:
 new 0708112  Update the format error of home page
0708112 is described below

commit 0708112f6fda63fdcee1f4ae976b62cf37388358
Author: Willem Jiang 
AuthorDate: Thu May 24 14:55:13 2018 +0800

Update the format error of home page
---
 _pages/home.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_pages/home.md b/_pages/home.md
index 0045faf..8220290 100644
--- a/_pages/home.md
+++ b/_pages/home.md
@@ -22,7 +22,7 @@ intro:
 
   
  Microservice Meetup: 
Apache ServiceComb (incubating) Day
-  
+  
   
   ServiceComb announces it's first Apache Incubating 
Release to the community.
   

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] branch asf-site updated (c1356f3 -> 94ddd87)

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a change to branch asf-site
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git.


from c1356f3  publish the website
 add 7582391  add healthcheck
 add 7c5c20f  fix small mistake
 add 2b56cef  Add the information of rc-directory to release guide
 add e951fb0  Update release_guide.md
 add 9131a87  add easy-build-microservice-system-part-II blog
 add 68eabb5  fix style
 add 235b2dd  fix mistake
 add 66c4179  [SCB-606] Add blog about updated Apache ServiceComb 
(incubating) Day on Website
 add 58607f1  add cn version of the blog about apache servicecomb 
(incubating) day
 add c0eaa46  Clean up the demo code of healthcheck
 add 4589a64  [SCB-606] Update the home page of the news
 new 646f045  Merge branch 'master' into asf-site
 new 94ddd87  publish the website

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 _data/navigation.yml   |4 +
 _developers/release_guide.md   |   93 +-
 _pages/cn/home.md  |7 +-
 _pages/home.md |7 +-
 ...2018-05-23-apache-servicecomb-incubating-day.md |  101 ++
 ...2018-05-23-apache-servicecomb-incubating-day.md |   70 ++
 ...05-23-easy-build-microservice-system-part-II.md |  325 ++
 _users/cn/healthcheck.md   |   84 ++
 _users/healthcheck.md  |   84 ++
 assets/images/HealthCheck.png  |  Bin 0 -> 27349 bytes
 assets/images/scaffold/ACL.png |  Bin 0 -> 88182 bytes
 assets/images/scaffold/RBAC.png|  Bin 0 -> 59287 bytes
 assets/images/scaffold/TestLogin.png   |  Bin 0 -> 98681 bytes
 assets/images/scaffold/TestLogon.png   |  Bin 0 -> 88931 bytes
 assets/images/scaffold/UserServiceInit.png |  Bin 0 -> 102862 bytes
 content/assets/images/HealthCheck.png  |  Bin 0 -> 27349 bytes
 content/assets/images/scaffold/ACL.png |  Bin 0 -> 88182 bytes
 content/assets/images/scaffold/RBAC.png|  Bin 0 -> 59287 bytes
 content/assets/images/scaffold/TestLogin.png   |  Bin 0 -> 98681 bytes
 content/assets/images/scaffold/TestLogon.png   |  Bin 0 -> 88931 bytes
 content/assets/images/scaffold/UserServiceInit.png |  Bin 0 -> 102862 bytes
 .../index.html |  171 +--
 content/cn/docs/autoscale-on-company/index.html|   24 +-
 .../index.html |   24 +-
 content/cn/docs/communication-btw-sc-ms/index.html |   24 +-
 content/cn/docs/company-on-kubernetes/index.html   |   24 +-
 .../cn/docs/config_center_integration/index.html   |   24 +-
 .../index.html |   20 +-
 content/cn/docs/distributed_saga_1/index.html  |   24 +-
 content/cn/docs/distributed_saga_2/index.html  |   24 +-
 content/cn/docs/distributed_saga_3/index.html  |   24 +-
 .../index.html |   23 +-
 .../index.html | 1102 
 content/cn/docs/go-to-cloud/index.html |   24 +-
 .../docs/how-to-reform-a-legacy-system/index.html  |   24 +-
 content/cn/docs/jira_beginner_guide/index.html |   24 +-
 content/cn/docs/join_the_community/index.html  |   24 +-
 content/cn/docs/linuxcon-workshop-demo/index.html  |   24 +-
 .../cn/docs/maven_dependency_management/index.html |   24 +-
 content/cn/docs/open-design/index.html |   22 +-
 .../index.html |   24 +-
 content/cn/docs/saga_pack_design/index.html|   24 +-
 content/cn/docs/saga_with_cucumber/index.html  |   18 +-
 .../seckill-development-journey-part-I/index.html  |   24 +-
 .../seckill-development-journey-part-II/index.html |   24 +-
 .../index.html |   24 +-
 .../index.html |   24 +-
 .../cn/docs/tracing-with-servicecomb/index.html|   24 +-
 content/cn/index.html  |3 +-
 .../cn/users/application-boot-process/index.html   |8 +
 content/cn/users/communicate-protocol/index.html   |8 +
 content/cn/users/customized-tracing/index.html |8 +
 content/cn/users/develop-with-jax-rs/index.html|8 +
 .../cn/users/develop-with-rest-template/index.html |8 +
 content/cn/users/develop-with-rpc/index.html   |8 +
 .../develop-with-spring-boot-starter/index.html|8 +
 content/cn/users/develop-with-springmvc/index.html |8 +
 .../users/develop-with-transparent-rpc/index.html  |8 +

[incubator-servicecomb-website] 01/02: Merge branch 'master' into asf-site

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch asf-site
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit 646f045ac24dd8595381d8c2b207f110472b99ac
Merge: c1356f3 4589a64
Author: Willem Jiang 
AuthorDate: Thu May 24 14:49:49 2018 +0800

Merge branch 'master' into asf-site

 _data/navigation.yml   |   4 +
 _developers/release_guide.md   |  93 +++---
 _pages/cn/home.md  |   7 +-
 _pages/home.md |   7 +-
 ...2018-05-23-apache-servicecomb-incubating-day.md | 101 +++
 ...2018-05-23-apache-servicecomb-incubating-day.md |  70 +
 ...05-23-easy-build-microservice-system-part-II.md | 325 +
 _users/cn/healthcheck.md   |  84 ++
 _users/healthcheck.md  |  84 ++
 assets/images/HealthCheck.png  | Bin 0 -> 27349 bytes
 assets/images/scaffold/ACL.png | Bin 0 -> 88182 bytes
 assets/images/scaffold/RBAC.png| Bin 0 -> 59287 bytes
 assets/images/scaffold/TestLogin.png   | Bin 0 -> 98681 bytes
 assets/images/scaffold/TestLogon.png   | Bin 0 -> 88931 bytes
 assets/images/scaffold/UserServiceInit.png | Bin 0 -> 102862 bytes
 15 files changed, 727 insertions(+), 48 deletions(-)

diff --cc _data/navigation.yml
index 8ae6bc5,88c47ee..548179f
--- a/_data/navigation.yml
+++ b/_data/navigation.yml
@@@ -270,8 -272,10 +272,10 @@@ t
  url: /cn/users/metrics-in-1.0.0-m1/
- title: 1.0.0-m1版本写文件扩展和示例
  url: 
/cn/users/metrics-write-file-extension-and-sample-in-1.0.0-m1/
 -  - title: 1.0.0-m1版本中的监控如何集成普罗米修斯
 +  - title: 1.0.0-m1版本中的监控如何集成prometheus
  url: /cn/users/metrics-integration-with-prometheus-in-1.0.0-m1/
+   - title: 健康检查
+ url: /cn/users/healthcheck/
  
- title: 部署
  children:

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[GitHub] WillemJiang commented on issue #89: [SCB-575] Add API documents for Java-Chassis and Saga

2018-05-24 Thread GitBox

WillemJiang commented on issue #89: [SCB-575] Add API documents for 
Java-Chassis and Saga
URL: 
https://github.com/apache/incubator-servicecomb-website/pull/89#issuecomment-391607788
 
 
   The build is ran every time we did some modification, but we just update the 
API document once we release. BTW, you still need to run "bundle exec jekyll 
server" to do some preview locally.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[incubator-servicecomb-website] branch master updated (58607f1 -> 4589a64)

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a change to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git.


from 58607f1  add cn version of the blog about apache servicecomb 
(incubating) day
 new c0eaa46  Clean up the demo code of healthcheck
 new 4589a64  [SCB-606] Update the home page of the news

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 _data/navigation.yml | 4 
 _pages/cn/home.md| 7 +--
 _pages/home.md   | 7 +--
 _users/cn/healthcheck.md | 6 +++---
 _users/healthcheck.md| 8 
 5 files changed, 17 insertions(+), 15 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] 02/02: [SCB-606] Update the home page of the news

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit 4589a642171b1b5d9c9cd5ace16ea229d9009799
Author: Willem Jiang 
AuthorDate: Thu May 24 14:41:30 2018 +0800

[SCB-606] Update the home page of the news
---
 _data/navigation.yml | 4 
 _pages/cn/home.md| 7 +--
 _pages/home.md   | 7 +--
 3 files changed, 10 insertions(+), 8 deletions(-)

diff --git a/_data/navigation.yml b/_data/navigation.yml
index 69b9249..88c47ee 100755
--- a/_data/navigation.yml
+++ b/_data/navigation.yml
@@ -33,8 +33,6 @@ t:
 url: /docs/quick-start-advance/distributed-tracing/
   - title: "Data Consistency Solution"
 url: /docs/quick-start-dataconsistency/
-  - title: "Microservice Meetup: Apache ServiceComb (incubating) Day"
-url: /docs/apache-servicecomb-incubating-day/
 
 users:
   - title: User Guide
@@ -198,8 +196,6 @@ t:
 url: /cn/docs/quick-start-advance/distributed-tracing/
   - title: "数据一致性解决方案"
 url: /cn/docs/quick-start-dataconsistency/
-  - title: "微服务 Meetup：Apache ServiceComb (incubating) Day"
-url: /cn/docs/apache-servicecomb-incubating-day/
 
 users:
   - title: 用户手册
diff --git a/_pages/cn/home.md b/_pages/cn/home.md
index f438bb3..3de164e 100644
--- a/_pages/cn/home.md
+++ b/_pages/cn/home.md
@@ -22,10 +22,13 @@ intro:
 
 
   
-号外： 
现在ServiceComb提供了微服务场景下的数据一致性解决方案Saga！
+ 微服务 Meetup：Apache 
ServiceComb (incubating) Day
+  
+  
+ServiceComb 第一个Apache孵化版本发布了！
   
   
-ServiceComb 第一个Apache孵化版本发布了！
+号外：现在ServiceComb提供了微服务场景下的数据一致性解决方案Saga！
   
 "
 
diff --git a/_pages/home.md b/_pages/home.md
index bcbf68b..0045faf 100644
--- a/_pages/home.md
+++ b/_pages/home.md
@@ -21,11 +21,14 @@ intro:
 
 
   
-ServiceComb now provides data 
consistency solutions(Saga) in microservice application.
-  
+ Microservice Meetup: 
Apache ServiceComb (incubating) Day
+  
   
   ServiceComb announces it's first Apache Incubating 
Release to the community.
   
+  
+ServiceComb now provides data 
consistency solutions(Saga) in microservice application.
+  
 "
 
 feature_row:

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] 01/02: Clean up the demo code of healthcheck

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit c0eaa464dd4456637cdf74741a75d849b8b03aae
Author: Willem Jiang 
AuthorDate: Thu May 24 14:06:56 2018 +0800

Clean up the demo code of healthcheck
---
 _users/cn/healthcheck.md | 6 +++---
 _users/healthcheck.md| 8 
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/_users/cn/healthcheck.md b/_users/cn/healthcheck.md
index 6eab081..1ad322f 100644
--- a/_users/cn/healthcheck.md
+++ b/_users/cn/healthcheck.md
@@ -44,14 +44,14 @@ public class MySqlHealthChecker implements HealthChecker {
   connection = 
DriverManager.getConnection("jdbc:mysql://localhost:3306/test_db?useSSL=false", 
"root", "pwd");
   return new HealthCheckResult(true, "local mysql health check", "");
 } catch (SQLException e) {
-  e.printStackTrace();
+  LOG.error("Cannot connect the localhost mysql. ", e);
   return new HealthCheckResult(false, "local mysql health check", 
e.toString());
 } finally {
   if (connection != null) {
 try {
   connection.close();
 } catch (SQLException e) {
-  e.printStackTrace();
+  LOG.error("Close connect the localhost mysql error. ", e);
 }
   }
 }
@@ -81,4 +81,4 @@ servicecomb:
 >2. 
 >/health为所有HealthCheck的最终结果，true或false，只要有任何一个HealthCheck的healthy结果为false，那么就会是false。
 
 ## 参考示例
-我们已经提供了一个例子作为参考，代码在samples/metrics-extend-healthcheck中。
\ No newline at end of file
+我们已经提供了一个例子作为参考，代码在samples/metrics-extend-healthcheck中。
diff --git a/_users/healthcheck.md b/_users/healthcheck.md
index ae25499..54f8548 100644
--- a/_users/healthcheck.md
+++ b/_users/healthcheck.md
@@ -44,14 +44,14 @@ public class MySqlHealthChecker implements HealthChecker {
   connection = 
DriverManager.getConnection("jdbc:mysql://localhost:3306/test_db?useSSL=false", 
"root", "pwd");
   return new HealthCheckResult(true, "local mysql health check", "");
 } catch (SQLException e) {
-  e.printStackTrace();
+  LOG.error("Cannot connect the localhost mysql. ", e);
   return new HealthCheckResult(false, "local mysql health check", 
e.toString());
 } finally {
   if (connection != null) {
 try {
   connection.close();
 } catch (SQLException e) {
-  e.printStackTrace();
+  LOG.error("Close connect the localhost mysql error. ", e);
 }
   }
 }
@@ -80,5 +80,5 @@ We can get HealthCheck final result by accress 
http://localhost:8080/health , al
 >1. The implementation of Rest publish is in metrics-core, so need import this 
 >dependency;
 >2. The result of /health is the final result of all HealthCheckers, true or 
 >false, if healthy result of any HealthChecker return false, then this value 
 >will false.
 
-## Other Reference 
-We had provided a sample at samples/metrics-extend-healthcheck.
\ No newline at end of file
+## Other Reference
+We had provided a sample at samples/metrics-extend-healthcheck.

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[GitHub] yangbor commented on issue #89: [SCB-575] Add API documents for Java-Chassis and Saga

2018-05-24 Thread GitBox

yangbor commented on issue #89: [SCB-575] Add API documents for Java-Chassis 
and Saga
URL: 
https://github.com/apache/incubator-servicecomb-website/pull/89#issuecomment-391604434
 
 
   Yes we can do this to save a bit of build time of the site. But this will 
cause us to submit 2 PRs every time we add new API documents(new release). And 
we will not be able to preview the site locally.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] zenlinTechnofreak commented on issue #93: [SCB-606] Add blog about updated Apache ServiceComb (incubating) Day on website

2018-05-24 Thread GitBox

zenlinTechnofreak commented on issue #93: [SCB-606] Add blog about updated 
Apache ServiceComb (incubating) Day on website
URL: 
https://github.com/apache/incubator-servicecomb-website/pull/93#issuecomment-391601616
 
 
   OK, thanks to Willem. I am going to pay attention for this next time.
   
   Best Regards,
   ---
   Zen Lin
   zenlintechnofr...@gmail.com
   Focused on Micro Service and Apache ServiceComb
   
   2018-05-24 14:13 GMT+08:00 Willem Jiang :
   
   > Merged #93
   > .
   >
   > —
   > You are receiving this because you authored the thread.
   > Reply to this email directly, view it on GitHub
   > 
,
   > or mute the thread
   > 

   > .
   >
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] WillemJiang commented on a change in pull request #93: [SCB-606] Add blog about updated Apache ServiceComb (incubating) Day on website

2018-05-24 Thread GitBox

WillemJiang commented on a change in pull request #93: [SCB-606] Add blog about 
updated Apache ServiceComb (incubating) Day on website
URL: 
https://github.com/apache/incubator-servicecomb-website/pull/93#discussion_r190474944
 
 

 ##
 File path: _data/navigation.yml
 ##
 @@ -194,6 +196,8 @@ t:
 url: /cn/docs/quick-start-advance/distributed-tracing/
   - title: "数据一致性解决方案"
 url: /cn/docs/quick-start-dataconsistency/
+  - title: "微服务 Meetup：Apache ServiceComb (incubating) Day"
 
 Review comment:
   Don't worry, I can fix it after merged the PR. 
   Just pay attention next time.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[incubator-servicecomb-website] branch master updated (235b2dd -> 58607f1)

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a change to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git.


from 235b2dd  fix mistake
 new 66c4179  [SCB-606] Add blog about updated Apache ServiceComb 
(incubating) Day on Website
 new 58607f1  add cn version of the blog about apache servicecomb 
(incubating) day

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 _data/navigation.yml   |   4 +
 ...2018-05-23-apache-servicecomb-incubating-day.md | 101 +
 ...2018-05-23-apache-servicecomb-incubating-day.md |  70 ++
 3 files changed, 175 insertions(+)
 create mode 100644 _posts/2018-05-23-apache-servicecomb-incubating-day.md
 create mode 100644 _posts/cn/2018-05-23-apache-servicecomb-incubating-day.md

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] 02/02: add cn version of the blog about apache servicecomb (incubating) day

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit 58607f11f54bb8e7df9ec4170d95ddee11230cd3
Author: linzhinan 
AuthorDate: Wed May 23 22:16:38 2018 +0800

add cn version of the blog about apache servicecomb (incubating) day

Signed-off-by: linzhinan 
---
 _data/navigation.yml   |  2 +
 ...2018-05-23-apache-servicecomb-incubating-day.md | 70 ++
 2 files changed, 72 insertions(+)

diff --git a/_data/navigation.yml b/_data/navigation.yml
index 9ffc688..69b9249 100755
--- a/_data/navigation.yml
+++ b/_data/navigation.yml
@@ -198,6 +198,8 @@ t:
 url: /cn/docs/quick-start-advance/distributed-tracing/
   - title: "数据一致性解决方案"
 url: /cn/docs/quick-start-dataconsistency/
+  - title: "微服务 Meetup：Apache ServiceComb (incubating) Day"
+url: /cn/docs/apache-servicecomb-incubating-day/
 
 users:
   - title: 用户手册
diff --git a/_posts/cn/2018-05-23-apache-servicecomb-incubating-day.md 
b/_posts/cn/2018-05-23-apache-servicecomb-incubating-day.md
new file mode 100644
index 000..9cd19b0
--- /dev/null
+++ b/_posts/cn/2018-05-23-apache-servicecomb-incubating-day.md
@@ -0,0 +1,70 @@
+---
+title: "微服务 Meetup：Apache ServiceComb (incubating) Day"
+lang: cn 
+ref: apache-servicecomb-incubating-day
+permalink: /cn/docs/apache-servicecomb-incubating-day/
+excerpt: "Real time updated information of Apache ServiceComb (incubating) Day"
+last_modified_at: 2018-05-23T10:26:28+08:00
+author: Zen Lin
+tags: [微服务, Meetup]
+redirect_from:
+  - /theme-setup/
+---
+
+**Apache ServiceComb (incubating) Day**
+
+
+
+**微服务开源  ServiceComb  
Apache基金会孵化项目将于6月27日（星期三）上午9点30分至下午16点30分在国家会议中心举办为期一天的开放日Meetup活动。**
+
+本次开放日将主要聚焦在以下几个方面，和企业、用户及开发者一同探讨微服务技术及方向。
+-  Apache 社区解读
+-  企业微服务商用案例实践分享
+-  微服务开源领域社区现状及未来
+-  ServiceComb的社区概况和技术分享
+-  微服务领域驱动设计方法
+
+**会议日期/时间**：2018 年 6 月 27 日，星期三，9:30 – 16:30
+**会议地址**：中国国家会议中心，北京
+**会议费用**： 免费
+
+
+
+**关于Apache ServiceComb (incubating) 项目**： 
+
+ServiceComb Apahce 
软件基金会孵化项目的主体代码由华为云捐赠，致力于帮助企业轻松构建云原生应用及传统企业业务快速微服务化，通过系列解决方案帮助用户快速开发微服务的同时实现对这些微服务应用的高效运维管理。它具有完整的微服务生态栈，无厂商锁定，当前遵循Apache
 Way进行孵化，已拥有如消费者云、云EI、云安全、云核等华为业务之外的一批非华为商用用户，且社区和开发者也日趋多样化。
+ 
+这是一个免费的开放日Meetup活动，由Apache ServiceComb 
(incubating)社区组织，华为云赞助主办，我们邀请到了来自商用企业、Apache、ServiceComb社区及华为的多位专家和工程师，与大家进行分享和探讨，部分议题如下：
 
+ 
+
+**《深度解读Apache软件基金会》**
+
+主讲人：Jean-Baptiste Onofré   Apache Member，Talend的Fellow, 
04年开始从事Apache软件基金会相关工作，Karaf、Camel、Carbondata等超过20个Apache项目的PMC member。  
+  
+摘要：深度解读全球最大的开源软件基金会Apache，诠释什么是Apache 
Way，及Apache的吸引开源项目之处，结合实际项目讲述从开源到孵化再到毕业的全过程，介绍当前ServiceComb的Apache孵化状态。 
+ 
+**《软通动力基于ServiceComb的智能城市微服务改造历程》** 
+ 
+主讲人：鲍永伟 软通动力智慧城市业务副总裁，聚焦于云计算与大数据相关的创新技术在智慧城市的应用。 
+
+摘要：软通动力智慧城市业务涉及系统繁多并交互复杂，在进行微服务化时面临微服务粒度设计不合理、代码重复率高、大型应用微服务部署困难等阵痛，本分享介绍软通动力如何使用ServiceComb，特别是ServiceComb的Swagger
 API，解决阵痛的微服务化历程，使能烟囱系统互通、系统松耦合，以应对智慧城市的微服务多样性挑战。 
+
+**《ServiceComb在华为消费者云的亿级用户微服务实践》** 
+
+主讲人：李林锋 
华为消费者云应用市场微服务架构师，多年平台中间件、云平台、微服务框架设计和开发经验。工作之余爱好技术写作，《Netty权威指南》和《分布式服务框架原理与实践》作者

+  
+摘要： 
华为消费者云服务为全球100多个国家数亿华为终端用户提供精品云服务，为了支撑业务的快速发展，需要通过微服务架构驱动价值需求更敏捷和高效的交付。利用ServiceComb对SpringMVC、透明RPC开发模式的支持，业务已有的代码可以低成本的迁移到新的微服务架构，同时利用ServiceComb对Reactive异步编程模型的支持，业务实现了全栈异步化改造，相比于传统的同步阻塞式服务调用，性能提升数倍，但是资源损耗却大幅降低...更多实践案例，尽在ServiceComb在华为消费者云的亿级用户实践分享中。

+  
+**《微服务的领域驱动设计》** 
+
+主讲人： 王磊微服务国内先驱，《微服务架构与实践》作者，华为微服务专家，前ThoughtWorks首席咨询师。 
+
+摘要：微服务作为新时代架构方式被业界广泛采纳，也顺理成章成为DDD领域驱动设计的理念的落地工具。本议题分享DDD领域驱动设计理念是如何与微服务友好结合和实践的。

+
+**更有 华为微服务开源专家、前红帽首席软件工程师、 
ServiceComb项目负责人姜宁携同社区孵化项目PMC们为大家详解ServiceComb社区及技术。** 
+ 
+ 
+**请关注本博客以保持及时获取关于本活动的及时更新信息，或者也可以通过我们的Gitter聊天室更加即时地咨询活动的相关信息：** 
+ 
+**[ServiceComb Gitter 聊天室](https://gitter.im/ServiceCombUsers/Lobby)**
+

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[GitHub] WillemJiang closed pull request #93: [SCB-606] Add blog about updated Apache ServiceComb (incubating) Day on website

2018-05-24 Thread GitBox

WillemJiang closed pull request #93: [SCB-606] Add blog about updated Apache 
ServiceComb (incubating) Day on website
URL: https://github.com/apache/incubator-servicecomb-website/pull/93
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/_data/navigation.yml b/_data/navigation.yml
index 4b5e6d7..3678052 100755
--- a/_data/navigation.yml
+++ b/_data/navigation.yml
@@ -33,6 +33,8 @@ t:
 url: /docs/quick-start-advance/distributed-tracing/
   - title: "Data Consistency Solution"
 url: /docs/quick-start-dataconsistency/
+  - title: "Microservice Meetup: Apache ServiceComb (incubating) Day"
+url: /docs/apache-servicecomb-incubating-day/
 
 users:
   - title: User Guide
@@ -194,6 +196,8 @@ t:
 url: /cn/docs/quick-start-advance/distributed-tracing/
   - title: "数据一致性解决方案"
 url: /cn/docs/quick-start-dataconsistency/
+  - title: "微服务 Meetup：Apache ServiceComb (incubating) Day"
+url: /cn/docs/apache-servicecomb-incubating-day/
 
 users:
   - title: 用户手册
diff --git a/_posts/2018-05-23-apache-servicecomb-incubating-day.md 
b/_posts/2018-05-23-apache-servicecomb-incubating-day.md
new file mode 100644
index 000..9cfa4c0
--- /dev/null
+++ b/_posts/2018-05-23-apache-servicecomb-incubating-day.md
@@ -0,0 +1,101 @@
+---
+title: "Microservice Meetup: Apache ServiceComb (incubating) Day"
+lang: en
+ref: apache-servicecomb-incubating-day
+permalink: /docs/apache-servicecomb-incubating-day/
+excerpt: "Real time updated information of Apache ServiceComb (incubating) Day"
+last_modified_at: 2018-05-23T10:26:28+08:00
+author: Zen Lin
+tags: [microservice, Meetup]
+redirect_from:
+  - /theme-setup/
+---
+
+**Apache ServiceComb (incubating) Day** 
+ 
+
+
+The microservice open source project - Apache ServiceComb (incubating) will 
host a Open Day Meetup at the China National Convention Center (Beijing, China) 
from 9.30am to 16.30pm on Wednesday, June 27th.
+
+The Open Day will focus on the following aspects and discuss the technology 
and direction of microservices with enterprises, users and developers.
+  
+
+
+\- Interpretation of the Apache community
+
+\- Business Microservices Commercial Case Sharing
+
+\- State of affairs and Future of Microservice Open Source Community
+
+\- Overview of ServiceComb Community and Technology Sharing
+
+\- Domain-Driven Design (DDD) in Microservices
+
+
+
+ 
+**Event Date/Time**: Wednesday, June 27, 2018, 9:30 – 16:30
+
+**Event Location**: China National Convention Center, Beijing, China
+
+**Event Cost**: Complimentary
+ 
+
+
+
+***About Apache ServiceComb (incubating) project:***
+
+ *The main code of the Apache ServiceComb (incubating) Project was 
donated by Huawei Cloud. The project is dedicated to help enterprises easily 
build cloud native applications and help build microservices from traditional 
enterprise business. By providing a series of solutions, Apache ServiceComb 
(incubating) helps users to develop microservices quickly and operate 
maintenance efficiently of these microservices applications, with a full 
microservices technology stack, without vendor lock-in. Currently, ServiceComb 
is following the “Apache Way”. It is used in HUAWEI businesses such as Consumer 
Cloud, Cloud EI, Cloud Security, Cloud Core Network, also popular in non-HUAWEI 
users. The developers are also increasingly diversified.*
+
+
+
+This is a free Open Meetup organized by the Apache ServiceComb (incubating) 
community and sponsored by Huawei Cloud. We have invited several experts and 
engineers from commercial enterprises, Apache Foundation, ServiceComb community 
and HUAWEI to share their experiences. Some of the topics as follows:
+ 
+
+
+**How Apache Works**
+
+**Speaker**: Jean-Baptiste Onofré; Apache Member, fellow of Talend, who 
started work on the Apache Software Foundation in 2004, and PMC member of 20+ 
Apache projects such as Karaf, Camel, and Carbondata.
+
+**Abstract:** 
+
+In-depth interpretation of the world's largest open source software foundation 
– Apache Software Foundation. Introduce what is the “Apache Way” and its 
attraction, the whole process from open source to incubation and then graduated 
combined with actual project. Besides, it will introduce the current incubating 
status of ServiceComb.
+
+
+
+**How Smart City Microserviced Based on ServiceComb from iSoftStone**
+
+**Speaker**: Bao Yongwei; VP of iSoftStone Smart City Business, focusing on 
implementation and innovations in smart city related to cloud computing and big 
data.
+
+**Abstract**: 
+
+iSoftStone Smart City Business involves a large number of systems with complex 
interactions. During the process of microservices

[incubator-servicecomb-website] 01/02: [SCB-606] Add blog about updated Apache ServiceComb (incubating) Day on Website

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit 66c41799e4a03c7d8350a0789120f59a813c5dec
Author: linzhinan 
AuthorDate: Wed May 23 21:50:23 2018 +0800

[SCB-606] Add blog about updated Apache ServiceComb (incubating) Day on 
Website

Signed-off-by: linzhinan 
---
 _data/navigation.yml   |   2 +
 ...2018-05-23-apache-servicecomb-incubating-day.md | 101 +
 2 files changed, 103 insertions(+)

diff --git a/_data/navigation.yml b/_data/navigation.yml
index 88c47ee..9ffc688 100755
--- a/_data/navigation.yml
+++ b/_data/navigation.yml
@@ -33,6 +33,8 @@ t:
 url: /docs/quick-start-advance/distributed-tracing/
   - title: "Data Consistency Solution"
 url: /docs/quick-start-dataconsistency/
+  - title: "Microservice Meetup: Apache ServiceComb (incubating) Day"
+url: /docs/apache-servicecomb-incubating-day/
 
 users:
   - title: User Guide
diff --git a/_posts/2018-05-23-apache-servicecomb-incubating-day.md 
b/_posts/2018-05-23-apache-servicecomb-incubating-day.md
new file mode 100644
index 000..9cfa4c0
--- /dev/null
+++ b/_posts/2018-05-23-apache-servicecomb-incubating-day.md
@@ -0,0 +1,101 @@
+---
+title: "Microservice Meetup: Apache ServiceComb (incubating) Day"
+lang: en
+ref: apache-servicecomb-incubating-day
+permalink: /docs/apache-servicecomb-incubating-day/
+excerpt: "Real time updated information of Apache ServiceComb (incubating) Day"
+last_modified_at: 2018-05-23T10:26:28+08:00
+author: Zen Lin
+tags: [microservice, Meetup]
+redirect_from:
+  - /theme-setup/
+---
+
+**Apache ServiceComb (incubating) Day** 
+ 
+
+
+The microservice open source project - Apache ServiceComb (incubating) will 
host a Open Day Meetup at the China National Convention Center (Beijing, China) 
from 9.30am to 16.30pm on Wednesday, June 27th.
+
+The Open Day will focus on the following aspects and discuss the technology 
and direction of microservices with enterprises, users and developers.
+  
+
+
+\- Interpretation of the Apache community
+
+\- Business Microservices Commercial Case Sharing
+
+\- State of affairs and Future of Microservice Open Source Community
+
+\- Overview of ServiceComb Community and Technology Sharing
+
+\- Domain-Driven Design (DDD) in Microservices
+
+
+
+ 
+**Event Date/Time**: Wednesday, June 27, 2018, 9:30 – 16:30
+
+**Event Location**: China National Convention Center, Beijing, China
+
+**Event Cost**: Complimentary
+ 
+
+
+
+***About Apache ServiceComb (incubating) project:***
+
+ *The main code of the Apache ServiceComb (incubating) Project was 
donated by Huawei Cloud. The project is dedicated to help enterprises easily 
build cloud native applications and help build microservices from traditional 
enterprise business. By providing a series of solutions, Apache ServiceComb 
(incubating) helps users to develop microservices quickly and operate 
maintenance efficiently of these microservices applications, with a full 
microservices technology stack, without ve [...]
+
+
+
+This is a free Open Meetup organized by the Apache ServiceComb (incubating) 
community and sponsored by Huawei Cloud. We have invited several experts and 
engineers from commercial enterprises, Apache Foundation, ServiceComb community 
and HUAWEI to share their experiences. Some of the topics as follows:
+ 
+
+
+**How Apache Works**
+
+**Speaker**: Jean-Baptiste Onofré; Apache Member, fellow of Talend, who 
started work on the Apache Software Foundation in 2004, and PMC member of 20+ 
Apache projects such as Karaf, Camel, and Carbondata.
+
+**Abstract:** 
+
+In-depth interpretation of the world's largest open source software foundation 
– Apache Software Foundation. Introduce what is the “Apache Way” and its 
attraction, the whole process from open source to incubation and then graduated 
combined with actual project. Besides, it will introduce the current incubating 
status of ServiceComb.
+
+
+
+**How Smart City Microserviced Based on ServiceComb from iSoftStone**
+
+**Speaker**: Bao Yongwei; VP of iSoftStone Smart City Business, focusing on 
implementation and innovations in smart city related to cloud computing and big 
data.
+
+**Abstract**: 
+
+iSoftStone Smart City Business involves a large number of systems with complex 
interactions. During the process of microservices implementation, it faced 
inappropriate microservices granularity, high code duplication rate, and 
difficulty in deployment of large application microservices. This speech will 
introduce how iSoftStone use ServiceComb, especially ServiceComb’s Swagger API, 
to resolve the pain points of microservices process, enable interoperability 
and decoupled chimney  systems [...]
+
+
+

[incubator-servicecomb-website] 03/03: fix mistake

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit 235b2dde59cb58923f1da45d35aa2ea2624faefd
Author: zhengyangyong 
AuthorDate: Wed May 23 16:43:43 2018 +0800

fix mistake

Signed-off-by: zhengyangyong 
---
 _posts/cn/2018-05-23-easy-build-microservice-system-part-II.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md 
b/_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md
index 5b2b910..ee50278 100644
--- a/_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md
+++ b/_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md
@@ -73,7 +73,7 @@ Token中文翻译为令牌，它将登录认证后的信息签名后返回，服
 
 ### 实现用户微服务
  第一步：创建微服务项目
-还记得前一篇博文[《轻松微服务系列：从一键构建微服务和DDD设计开始》](/cn/docs/easy-build-microservice-system-part-I/)中一键构建微服务的命令行么？使用ServiceComb
 SpringMVC 
Archetypes创建用户微服务，在交互模式下，`groupId`输入org.apache.servicecomb.scaffold，`artifactId`输入user-service，`version`使用默认的1.0-SNAPSHOT，创建完毕后使用IDEA或Eclipse打开项目：
+还记得前一篇博文[《轻松微服务系列：从一键构建微服务和DDD设计开始》](http://servicecomb.incubator.apache.org/cn/docs/easy-build-microservice-system-part-I/)中一键构建微服务的命令行么？使用ServiceComb
 SpringMVC 
Archetypes创建用户微服务，在交互模式下，`groupId`输入org.apache.servicecomb.scaffold，`artifactId`输入user-service，`version`使用默认的1.0-SNAPSHOT，创建完毕后使用IDEA或Eclipse打开项目：
 
 ![UserServiceInit](/assets/images/scaffold/UserServiceInit.png)
 

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] branch master updated (e951fb0 -> 235b2dd)

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a change to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git.


from e951fb0  Update release_guide.md
 new 9131a87  add easy-build-microservice-system-part-II blog
 new 68eabb5  fix style
 new 235b2dd  fix mistake

The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 ...05-23-easy-build-microservice-system-part-II.md | 325 +
 assets/images/scaffold/ACL.png | Bin 0 -> 88182 bytes
 assets/images/scaffold/RBAC.png| Bin 0 -> 59287 bytes
 assets/images/scaffold/TestLogin.png   | Bin 0 -> 98681 bytes
 assets/images/scaffold/TestLogon.png   | Bin 0 -> 88931 bytes
 assets/images/scaffold/UserServiceInit.png | Bin 0 -> 102862 bytes
 6 files changed, 325 insertions(+)
 create mode 100644 
_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md
 create mode 100644 assets/images/scaffold/ACL.png
 create mode 100644 assets/images/scaffold/RBAC.png
 create mode 100644 assets/images/scaffold/TestLogin.png
 create mode 100644 assets/images/scaffold/TestLogon.png
 create mode 100644 assets/images/scaffold/UserServiceInit.png

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] 02/03: fix style

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit 68eabb59c47b889c4c806804839dff0eceb9
Author: zhengyangyong 
AuthorDate: Wed May 23 16:41:18 2018 +0800

fix style

Signed-off-by: zhengyangyong 
---
 ...05-23-easy-build-microservice-system-part-II.md | 24 --
 1 file changed, 13 insertions(+), 11 deletions(-)

diff --git a/_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md 
b/_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md
index 21a8650..5b2b910 100644
--- a/_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md
+++ b/_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md
@@ -12,7 +12,7 @@ redirect_from:
 ---
 
 ## 轻松微服务系列：快速实现客户关系管理系统的用户服务
-在前一篇博文[《轻松微服务系列：从一键构建微服务和DDD设计开始》](/cn/docs/easy-build-microservice-system-part-I/)，我们已经详细介绍了如何快速构建微服务和DDD相关概念，并引入了一个经典场景——地产CRM。通过[Event
 Storming](https://en.wikipedia.org/wiki/Event_storming)实践获得了系统设计：
+在前一篇博文[《轻松微服务系列：从一键构建微服务和DDD设计开始》](http://servicecomb.incubator.apache.org/cn/docs/easy-build-microservice-system-part-I/)，我们已经详细介绍了如何快速构建微服务和DDD相关概念，并引入了一个经典场景——地产CRM。通过[Event
 Storming](https://en.wikipedia.org/wiki/Event_storming)实践获得了系统设计：
 
 ![MicroserviceDesign4](/assets/images/scaffold/MicroserviceDesign4.png)
 
@@ -72,12 +72,14 @@ Token中文翻译为令牌，它将登录认证后的信息签名后返回，服
 由于微服务系统的权限控制主要是接口访问控制上，并且多采用用户组方式组织用户，因此RBAC是比较流行的做法。
 
 ### 实现用户微服务
- 创建微服务项目
+ 第一步：创建微服务项目
 
还记得前一篇博文[《轻松微服务系列：从一键构建微服务和DDD设计开始》](/cn/docs/easy-build-microservice-system-part-I/)中一键构建微服务的命令行么？使用ServiceComb
 SpringMVC 
Archetypes创建用户微服务，在交互模式下，`groupId`输入org.apache.servicecomb.scaffold，`artifactId`输入user-service，`version`使用默认的1.0-SNAPSHOT，创建完毕后使用IDEA或Eclipse打开项目：
 
 ![UserServiceInit](/assets/images/scaffold/UserServiceInit.png)
 
- 使用MySQL持久化用户信息
+我们删掉HelloImpl和HelloConsumer，并添加自己的实现。
+
+ 第二步：使用MySQL持久化用户信息
 用户微服务需要持久化用户信息，我们使用MySQL数据库，ORM使用Spring Data JPA：
 # 引入依赖
 ```xml
@@ -90,7 +92,7 @@ Token中文翻译为令牌，它将登录认证后的信息签名后返回，服
   spring-boot-starter-data-jpa
 
 ```
-# 定义存储User信息的实体UserEntity
+# 定义存储User信息的UserEntity实体
 ```java
 @Entity
 @Table(name = "T_User")
@@ -128,7 +130,7 @@ public class UserEntity {
 
 在CodeFist模式下，Spring Data JPA会在数据库中自动创建T_User表与此实体映射。
 
-# 实现实体UserEntity的Repository
+# 实现UserEntity实体的Repository
 我们继承JPA的PagingAndSortingRepository来实现ORM操作
 
 ```java
@@ -151,7 +153,7 @@ 
spring.jpa.properties.hibernate.dialect=org.hibernate.dialect.MySQL5Dialect
 
 >提示：关于Spring Data 
 >JPA的更多资料请参见[这篇文档](https://projects.spring.io/spring-data-jpa/)，为了能够简化依赖的引入我们实际上使用的是Spring
 > Boot JPA 
 >Starter，详细的例子请参见[这篇文档](https://spring.io/guides/gs/accessing-data-jpa/)。
 
- 实现JWT认证
+ 第三步：实现JWT认证
 # 定义JWT接口
 
 ```java
@@ -207,7 +209,7 @@ public class JwtTokenStore implements TokenStore {
 }
 ```
 
- 实现用户服务
+ 第四步：实现用户服务
 # 定义UserService接口
 
 ```java
@@ -304,10 +306,10 @@ public class UserServiceImpl implements UserService {
 
 登录成功后，会从TokenStore生成Token，并将其写入Key为`AUTHORIZATION`的Header。
 
- 实现授权
+ 第五步：实现授权（可选）
 由于我们允许任何用户注册和登录，所以目前还没有授权的需求，基于RBAC构建授权体系将会在以后的博文中介绍。
 
-至此，具有基本注册和登录功能的用户微服务就构建好了。
+经过上面五步，具有基本注册和登录功能的用户微服务就构建好了。
 
 ### 验证实现的用户服务
 启动用户微服务，我们先注册一个账号：
@@ -318,6 +320,6 @@ public class UserServiceImpl implements UserService {
 
 ![TestLogin](/assets/images/scaffold/TestLogin.png)
 
-返回登录成功，Response中已经包含了`AUTHORIZATION`Header，后继的所有请求都将使用这个Token值认证。
+返回登录成功，Response中已经包含了`AUTHORIZATION`Header，后继的所有请求都需要使用这个Token值进行合法认证。
 
-至此，实现客户关系管理系统的用户服务工作就结束了，下一篇文章我们会将目光转移到Edge服务，通过Edge服务作为微服务调用的统一入口，在它之上构建统一认证，并讲解如何应对海量级调用的挑战！
\ No newline at end of file
+至此，实现客户关系管理系统的用户服务工作就结束了，下一篇文章我们会将目光转移到Edge服务，通过Edge服务作为微服务调用的统一入口，在它之上构建统一认证，并讲解如何应对海量级调用的挑战，敬请期待！
\ No newline at end of file

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] 01/03: add easy-build-microservice-system-part-II blog

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit 9131a87f2724634fe99397227dba4c799a121127
Author: zhengyangyong 
AuthorDate: Wed May 23 16:31:14 2018 +0800

add easy-build-microservice-system-part-II blog

Signed-off-by: zhengyangyong 
---
 ...05-23-easy-build-microservice-system-part-II.md | 323 +
 assets/images/scaffold/ACL.png | Bin 0 -> 88182 bytes
 assets/images/scaffold/RBAC.png| Bin 0 -> 59287 bytes
 assets/images/scaffold/TestLogin.png   | Bin 0 -> 98681 bytes
 assets/images/scaffold/TestLogon.png   | Bin 0 -> 88931 bytes
 assets/images/scaffold/UserServiceInit.png | Bin 0 -> 102862 bytes
 6 files changed, 323 insertions(+)

diff --git a/_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md 
b/_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md
new file mode 100644
index 000..21a8650
--- /dev/null
+++ b/_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md
@@ -0,0 +1,323 @@
+---
+title: "轻松微服务系列：快速实现客户关系管理系统的用户服务"
+lang: cn
+ref: easy-build-microservice-system-part-II
+permalink: /cn/docs/easy-build-microservice-system-part-II/
+excerpt: "轻松微服务系列：快速实现客户关系管理系统的用户服务"
+last_modified_at: 2018-05-23T19:05:00+08:00
+author: Yangyong Zheng
+tags: [Archetypes, Scaffold, Authentication, JWT]
+redirect_from:
+  - /theme-setup/
+---
+
+## 轻松微服务系列：快速实现客户关系管理系统的用户服务
+在前一篇博文[《轻松微服务系列：从一键构建微服务和DDD设计开始》](/cn/docs/easy-build-microservice-system-part-I/)，我们已经详细介绍了如何快速构建微服务和DDD相关概念，并引入了一个经典场景——地产CRM。通过[Event
 Storming](https://en.wikipedia.org/wiki/Event_storming)实践获得了系统设计：
+
+![MicroserviceDesign4](/assets/images/scaffold/MicroserviceDesign4.png)
+
+现在，我们将从“用户微服务”入手，探索微服务实现过程中即将面对的细节，并轻松处理这些难点。
+
+### 用户微服务并不简单
+用户微服务是所有系统中不可或缺的部分，它承载了认证和授权等核心功能——无论是登录一个网站、还是打开一个APP，当涉及到需要身份识别后才能够执行的操作，都需要用户微服务把关。例如观看视频网站上的视频，匿名用户会插播广告，如果希望屏蔽广告，则需要登录并购买VIP会员，登录即是身份认证的过程，而VIP屏蔽广告即是授权的过程。
+
+ 认证
+认证不仅仅是一次性验证用户名和密码的过程，还需要能反复使用认证的结果，确保后继所有操作都是合法的，这就涉及到“有状态”，但HTTP是一个无状态协议，如何能够将登录成功后的认证信息与后继的请求关联起来呢？
+
+我们非常熟悉的做法是使用Session或Cookie：
+- 
Session存储在服务端，因此具备良好的防篡改能力，但弊端是使服务有状态，微服务系统中，同一个微服务会依据系统压力的大小弹性伸缩出多个运行实例负载均衡，跨实例访问会状态丢失。
+- 
Cookie存储在客户端，它正好与Session相反，优势是服务不必保持状态，但弊端是客户比较容易的篡改Cookie信息，例如修改过期时间以逃避验证，而且浏览器对Cookie也有较多限制。
+
+那么，如何兼顾这两方面的需求呢？Token就是一个比较好的解决方案。
+
+Token中文翻译为令牌，它将登录认证后的信息签名后返回，服务端不保存，客户端请求的时候将认证的完整信息附带上提供给服务端验签，签名可以保证信息不被篡改。了解了了解Token的原理，自然要关注Token的格式，JWT就是这样一个基于JSON的开放标准[RFC-7519](https://tools.ietf.org/html/rfc7519)。
+
+# JWT （Java Web Token）规范
+简而言之JWT规范由三部分构成：
+1. Header： 声明Token的类型也就是JWT，以及加密算法，例如：
+
+```json
+{
+  "typ": "JWT",
+  "alg": "HS256"
+}
+```
+
+2. 
Playload：存放有效信息，既包含标准签发者、用户、签发时间、过期时间，唯一标识等信息；也可以存放用户自定义的声明信息，例如权限控制相关的内容，例如：
+
+```json
+{
+  "sub": "1234567890",
+  "name": "YangYong Zheng",
+  "iat": 1516239022
+}
+```
+
+3. Signature：签名信息，包含Header和Playload的原始信息（Base64编码过）以及签名过后的信息。
+
+>提示：JWT IO提供了[在线编码和解码工具](https://jwt.io/)。
+
+ 授权
+授权的本意是指将完成某项工作所必须的权力授给下属人员，在软件系统中往往引申为使人或角色具备访问特定资源或更改行为的许可。例如之前提到的VIP屏蔽广告，即是视频网站允许播放终端在特定的帐号登录后跳过广告播放环节（行为）的许可。
+
+授权系统比较常见的做法有ACL和RBAC：
+- ACL：ACL全称Access Control 
List，它是以受控资源为核心，每一个受控资源，都有一个权限控制列表记录哪些用户或角色对这项资源执行具体操作（也被称为授权点）的权限设置，例如查询（可见）、修改、删除等等。Windows中的文件系统安全即是一个经典的ACL实现案例：
+
+![ACL](/assets/images/scaffold/ACL.png)
+
+- RBAC：RBAC全称Role Based Access 
Control，与ACL相比，它以角色为核心，权限落地在角色上，不为特定用户授权。它的优势是大幅简化了用户与权限的管理，在受控对象不多或控制粒度要求不高（例如接口访问控制）的场景下非常适用。
+
+![RBAC](/assets/images/scaffold/RBAC.png)
+
+由于微服务系统的权限控制主要是接口访问控制上，并且多采用用户组方式组织用户，因此RBAC是比较流行的做法。
+
+### 实现用户微服务
+ 创建微服务项目
+还记得前一篇博文[《轻松微服务系列：从一键构建微服务和DDD设计开始》](/cn/docs/easy-build-microservice-system-part-I/)中一键构建微服务的命令行么？使用ServiceComb
 SpringMVC 
Archetypes创建用户微服务，在交互模式下，`groupId`输入org.apache.servicecomb.scaffold，`artifactId`输入user-service，`version`使用默认的1.0-SNAPSHOT，创建完毕后使用IDEA或Eclipse打开项目：
+
+![UserServiceInit](/assets/images/scaffold/UserServiceInit.png)
+
+ 使用MySQL持久化用户信息
+用户微服务需要持久化用户信息，我们使用MySQL数据库，ORM使用Spring Data JPA：
+# 引入依赖
+```xml
+
+  mysql
+  mysql-connector-java
+
+
+  org.springframework.boot
+  spring-boot-starter-data-jpa
+
+```
+# 定义存储User信息的实体UserEntity
+```java
+@Entity
+@Table(name = "T_User")
+public class UserEntity {
+  @Id
+  private String name;
+
+  private String password;
+
+  public String getName() {
+return name;
+  }
+
+  public void setName(String name) {
+this.name = name;
+  }
+
+  public String getPassword() {
+return password;
+  }
+
+  public void setPassword(String password) {
+this.password = password;
+  }
+
+  public UserEntity() {
+  }
+
+  public UserEntity(String name, String password) {
+this.name = name;
+this.password = password;
+  }
+}
+```
+
+在CodeFist模式下，Spring Data JPA会在数据库中自动创建T_User表与此实体映射。
+
+# 实现实体UserEntity的Repository
+我们继承JPA的PagingAndSortingRepository来实现ORM操作
+
+```java

[GitHub] WillemJiang closed pull request #90: Blog:轻松微服务系列：快速实现客户关系管理系统的用户服务

2018-05-24 Thread GitBox

WillemJiang closed pull request #90: Blog:轻松微服务系列：快速实现客户关系管理系统的用户服务
URL: https://github.com/apache/incubator-servicecomb-website/pull/90
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md 
b/_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md
new file mode 100644
index 000..ee50278
--- /dev/null
+++ b/_posts/cn/2018-05-23-easy-build-microservice-system-part-II.md
@@ -0,0 +1,325 @@
+---
+title: "轻松微服务系列：快速实现客户关系管理系统的用户服务"
+lang: cn
+ref: easy-build-microservice-system-part-II
+permalink: /cn/docs/easy-build-microservice-system-part-II/
+excerpt: "轻松微服务系列：快速实现客户关系管理系统的用户服务"
+last_modified_at: 2018-05-23T19:05:00+08:00
+author: Yangyong Zheng
+tags: [Archetypes, Scaffold, Authentication, JWT]
+redirect_from:
+  - /theme-setup/
+---
+
+## 轻松微服务系列：快速实现客户关系管理系统的用户服务
+在前一篇博文[《轻松微服务系列：从一键构建微服务和DDD设计开始》](http://servicecomb.incubator.apache.org/cn/docs/easy-build-microservice-system-part-I/)，我们已经详细介绍了如何快速构建微服务和DDD相关概念，并引入了一个经典场景——地产CRM。通过[Event
 Storming](https://en.wikipedia.org/wiki/Event_storming)实践获得了系统设计：
+
+![MicroserviceDesign4](/assets/images/scaffold/MicroserviceDesign4.png)
+
+现在，我们将从“用户微服务”入手，探索微服务实现过程中即将面对的细节，并轻松处理这些难点。
+
+### 用户微服务并不简单
+用户微服务是所有系统中不可或缺的部分，它承载了认证和授权等核心功能——无论是登录一个网站、还是打开一个APP，当涉及到需要身份识别后才能够执行的操作，都需要用户微服务把关。例如观看视频网站上的视频，匿名用户会插播广告，如果希望屏蔽广告，则需要登录并购买VIP会员，登录即是身份认证的过程，而VIP屏蔽广告即是授权的过程。
+
+ 认证
+认证不仅仅是一次性验证用户名和密码的过程，还需要能反复使用认证的结果，确保后继所有操作都是合法的，这就涉及到“有状态”，但HTTP是一个无状态协议，如何能够将登录成功后的认证信息与后继的请求关联起来呢？
+
+我们非常熟悉的做法是使用Session或Cookie：
+- 
Session存储在服务端，因此具备良好的防篡改能力，但弊端是使服务有状态，微服务系统中，同一个微服务会依据系统压力的大小弹性伸缩出多个运行实例负载均衡，跨实例访问会状态丢失。
+- 
Cookie存储在客户端，它正好与Session相反，优势是服务不必保持状态，但弊端是客户比较容易的篡改Cookie信息，例如修改过期时间以逃避验证，而且浏览器对Cookie也有较多限制。
+
+那么，如何兼顾这两方面的需求呢？Token就是一个比较好的解决方案。
+
+Token中文翻译为令牌，它将登录认证后的信息签名后返回，服务端不保存，客户端请求的时候将认证的完整信息附带上提供给服务端验签，签名可以保证信息不被篡改。了解了了解Token的原理，自然要关注Token的格式，JWT就是这样一个基于JSON的开放标准[RFC-7519](https://tools.ietf.org/html/rfc7519)。
+
+# JWT （Java Web Token）规范
+简而言之JWT规范由三部分构成：
+1. Header： 声明Token的类型也就是JWT，以及加密算法，例如：
+
+```json
+{
+  "typ": "JWT",
+  "alg": "HS256"
+}
+```
+
+2. 
Playload：存放有效信息，既包含标准签发者、用户、签发时间、过期时间，唯一标识等信息；也可以存放用户自定义的声明信息，例如权限控制相关的内容，例如：
+
+```json
+{
+  "sub": "1234567890",
+  "name": "YangYong Zheng",
+  "iat": 1516239022
+}
+```
+
+3. Signature：签名信息，包含Header和Playload的原始信息（Base64编码过）以及签名过后的信息。
+
+>提示：JWT IO提供了[在线编码和解码工具](https://jwt.io/)。
+
+ 授权
+授权的本意是指将完成某项工作所必须的权力授给下属人员，在软件系统中往往引申为使人或角色具备访问特定资源或更改行为的许可。例如之前提到的VIP屏蔽广告，即是视频网站允许播放终端在特定的帐号登录后跳过广告播放环节（行为）的许可。
+
+授权系统比较常见的做法有ACL和RBAC：
+- ACL：ACL全称Access Control 
List，它是以受控资源为核心，每一个受控资源，都有一个权限控制列表记录哪些用户或角色对这项资源执行具体操作（也被称为授权点）的权限设置，例如查询（可见）、修改、删除等等。Windows中的文件系统安全即是一个经典的ACL实现案例：
+
+![ACL](/assets/images/scaffold/ACL.png)
+
+- RBAC：RBAC全称Role Based Access 
Control，与ACL相比，它以角色为核心，权限落地在角色上，不为特定用户授权。它的优势是大幅简化了用户与权限的管理，在受控对象不多或控制粒度要求不高（例如接口访问控制）的场景下非常适用。
+
+![RBAC](/assets/images/scaffold/RBAC.png)
+
+由于微服务系统的权限控制主要是接口访问控制上，并且多采用用户组方式组织用户，因此RBAC是比较流行的做法。
+
+### 实现用户微服务
+ 第一步：创建微服务项目
+还记得前一篇博文[《轻松微服务系列：从一键构建微服务和DDD设计开始》](http://servicecomb.incubator.apache.org/cn/docs/easy-build-microservice-system-part-I/)中一键构建微服务的命令行么？使用ServiceComb
 SpringMVC 
Archetypes创建用户微服务，在交互模式下，`groupId`输入org.apache.servicecomb.scaffold，`artifactId`输入user-service，`version`使用默认的1.0-SNAPSHOT，创建完毕后使用IDEA或Eclipse打开项目：
+
+![UserServiceInit](/assets/images/scaffold/UserServiceInit.png)
+
+我们删掉HelloImpl和HelloConsumer，并添加自己的实现。
+
+ 第二步：使用MySQL持久化用户信息
+用户微服务需要持久化用户信息，我们使用MySQL数据库，ORM使用Spring Data JPA：
+# 引入依赖
+```xml
+
+  mysql
+  mysql-connector-java
+
+
+  org.springframework.boot
+  spring-boot-starter-data-jpa
+
+```
+# 定义存储User信息的UserEntity实体
+```java
+@Entity
+@Table(name = "T_User")
+public class UserEntity {
+  @Id
+  private String name;
+
+  private String password;
+
+  public String getName() {
+return name;
+  }
+
+  public void setName(String name) {
+this.name = name;
+  }
+
+  public String getPassword() {
+return password;
+  }
+
+  public void setPassword(String password) {
+this.password = password;
+  }
+
+  public UserEntity() {
+  }
+
+  public UserEntity(String name, String password) {
+this.name = name;
+this.password = password;
+  }
+}
+```
+
+在CodeFist模式下，Spring Data JPA会在数据库中自动创建T_User表与此实体映射。
+
+# 实现UserEntity实体的Repository
+我们继承JPA的PagingAndSortingRepository来实现ORM操作
+
+```java
+@Repository
+public interface UserRepository extends PagingAndSortingRepository {
+  UserEntity findByName(String name);
+}
+```
+
+# 配置数据库连接
+在项目的`resources`目录下新增`application.properties`文件，写入数据库连接信息：
+
+```properties
+spring.datasource.url=jdbc:mysql://localhost:3306/user_db?useSSL=false
+spring.datasource.username=root
+spring.datasource.password=pwd

[GitHub] WillemJiang closed pull request #91: Add the information of rc-directory to release guide

2018-05-24 Thread GitBox

WillemJiang closed pull request #91: Add the information of rc-directory to 
release guide
URL: https://github.com/apache/incubator-servicecomb-website/pull/91
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/_developers/release_guide.md b/_developers/release_guide.md
index 50d7b7d..5914646 100644
--- a/_developers/release_guide.md
+++ b/_developers/release_guide.md
@@ -105,39 +105,41 @@ gvt restore
 
 ***Sign the Release***
 
-10. Once the tag is pushed then using the tag download the source code from 
git [tag](https://github.com/apache/incubator-servicecomb-service-center/tags).
+1. Once the tag is pushed then using the tag download the source code from git 
[tag](https://github.com/apache/incubator-servicecomb-service-center/tags). 
 
-11. Sign the 3 releases(linux, windows, src) and checksum.
+2. Sign the 3 releases(linux, windows, src) and checksum.
 
-12. Upload the release to [Apache dev released 
repository](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/).
+3. Create a new directory [Apache dev Release 
SVN](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/)
 with release package name and release candidate number. (for example : if you 
want to release 1.0.0-m2 and this is the second attempt of the release then the 
folder structure will be `1.0.0-m2/rc02`)
 
-13. Download all the releases from SVN and verify the signature and checksum.
+4. Upload the release to the directory created in last step.
+
+5. Download all the releases from SVN and verify the signature and checksum.
 
 ***PPMC Approval***
 
-14. Send the voting mail in ***d...@servicecomb.apache.org*** for PPMC 
approval.
+1. Send the voting mail in ***d...@servicecomb.apache.org*** for PPMC approval.
 
-15. Wait for 72 hours or unless you get 3 +1 binding vote with no -1 vote. If 
you get even one -1 binding vote then fix the issue and start again from 
***Step 1***.
+2. Wait for 72 hours or unless you get 3 +1 binding vote with no -1 vote. If 
you get even one -1 binding vote then fix the issue and start again from 
***Step 1***.
 
-16. Publish the result of the vote in d...@servicecomb.apache.org.
+3. Publish the result of the vote in d...@servicecomb.apache.org.
 
 ***IPMC approval***
 
-17. Send the voting mail in ***gene...@incubator.apache.org*** for IPMC 
approval.
+1. Send the voting mail in ***gene...@incubator.apache.org*** for IPMC 
approval.
 
-18. Wait for 72 hours or unless you get 3 +1 binding vote with no -1 vote.If 
you get even one -1 binding vote then fix the issue and start again from 
***Step 1***
+2. Wait for 72 hours or unless you get 3 +1 binding vote with no -1 vote.If 
you get even one -1 binding vote then fix the issue and start again from 
***Step 1***
 
-19. Publish the result of the vote in gene...@incubator.apache.org.
+3. Publish the result of the vote in gene...@incubator.apache.org.
 
 ***Announcements***
 
-20. Upload the releases to [Apache release 
repository](https://dist.apache.org/repos/dist/release/incubator/servicecomb/incubator-servicecomb-service-center/).
+1. Upload the releases to [Apache release 
repository](https://dist.apache.org/repos/dist/release/incubator/servicecomb/incubator-servicecomb-service-center/).
 
-21. Wait for 24 hours to replicate the release in all the mirrors.
+2. Wait for 24 hours to replicate the release in all the mirrors.
 
-22. Upload the release page of ServiceComb Website.
+3. Upload the release page of ServiceComb Website.
 
-23. Send the announcement mails to d...@servicecomb.apache.org, 
gene...@incubator.apache.org, annou...@apache.org
+4. Send the announcement mails to d...@servicecomb.apache.org, 
gene...@incubator.apache.org, annou...@apache.org
 
 
 
@@ -181,40 +183,41 @@ mvn deploy -DskipTests -Prelease -Pdistribution 
-Ppassphrase
 
 ***Sign the Releases***
 
-13. Download the source code and distribution from the staging repo.
+1. Download the source code and distribution from the staging repo.
+
+2. Sign the 2 releases(distribution, src) and checksum.
 
-14. Sign the 2 releases(distribution, src) and checksum.
+3. Create a new directory [Apache dev Release 
SVN](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-java-chassis/)
 with release package name and release candidate number. (for example : if you 
want to release 1.0.0-m2 and this is the first attempt of the release then the 
folder structure will be `1.0.0-m2/rc01`)
 
-15. Upload the release to [Apache dev released 
repository](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-java-chassis/).
-.
+4. Upload the release to  directory created in last step.
 
-16. Download all the releases from

[incubator-servicecomb-website] 01/02: Add the information of rc-directory to release guide

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit 2b56ceff7f20874d1219d4600ce022fb00d61534
Author: asifdxtreme 
AuthorDate: Wed May 23 17:29:51 2018 +0530

Add the information of rc-directory to release guide
---
 _developers/release_guide.md | 95 
 1 file changed, 51 insertions(+), 44 deletions(-)

diff --git a/_developers/release_guide.md b/_developers/release_guide.md
index 50d7b7d..87aee65 100644
--- a/_developers/release_guide.md
+++ b/_developers/release_guide.md
@@ -105,39 +105,41 @@ gvt restore
 
 ***Sign the Release***
 
-10. Once the tag is pushed then using the tag download the source code from 
git [tag](https://github.com/apache/incubator-servicecomb-service-center/tags).
+1. Once the tag is pushed then using the tag download the source code from git 
[tag](https://github.com/apache/incubator-servicecomb-service-center/tags). 
 
-11. Sign the 3 releases(linux, windows, src) and checksum.
+2. Sign the 3 releases(linux, windows, src) and checksum.
 
-12. Upload the release to [Apache dev released 
repository](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/).
+3. Create a new directory [Apache dev Release 
SVN](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/)
 with release package name and release candidate number. (for example : if you 
want to release 1.0.0-m2 and this is the second attempt of the release then the 
folder structure will be `1.0.0-m2/rc02`)
 
-13. Download all the releases from SVN and verify the signature and checksum.
+4. Upload the release to the directory created in last step.
+
+5. Download all the releases from SVN and verify the signature and checksum.
 
 ***PPMC Approval***
 
-14. Send the voting mail in ***d...@servicecomb.apache.org*** for PPMC 
approval.
+1. Send the voting mail in ***d...@servicecomb.apache.org*** for PPMC approval.
 
-15. Wait for 72 hours or unless you get 3 +1 binding vote with no -1 vote. If 
you get even one -1 binding vote then fix the issue and start again from 
***Step 1***.
+2. Wait for 72 hours or unless you get 3 +1 binding vote with no -1 vote. If 
you get even one -1 binding vote then fix the issue and start again from 
***Step 1***.
 
-16. Publish the result of the vote in d...@servicecomb.apache.org.
+3. Publish the result of the vote in d...@servicecomb.apache.org.
 
 ***IPMC approval***
 
-17. Send the voting mail in ***gene...@incubator.apache.org*** for IPMC 
approval.
+1. Send the voting mail in ***gene...@incubator.apache.org*** for IPMC 
approval.
 
-18. Wait for 72 hours or unless you get 3 +1 binding vote with no -1 vote.If 
you get even one -1 binding vote then fix the issue and start again from 
***Step 1***
+2. Wait for 72 hours or unless you get 3 +1 binding vote with no -1 vote.If 
you get even one -1 binding vote then fix the issue and start again from 
***Step 1***
 
-19. Publish the result of the vote in gene...@incubator.apache.org.
+3. Publish the result of the vote in gene...@incubator.apache.org.
 
 ***Announcements***
 
-20. Upload the releases to [Apache release 
repository](https://dist.apache.org/repos/dist/release/incubator/servicecomb/incubator-servicecomb-service-center/).
+1. Upload the releases to [Apache release 
repository](https://dist.apache.org/repos/dist/release/incubator/servicecomb/incubator-servicecomb-service-center/).
 
-21. Wait for 24 hours to replicate the release in all the mirrors.
+2. Wait for 24 hours to replicate the release in all the mirrors.
 
-22. Upload the release page of ServiceComb Website.
+3. Upload the release page of ServiceComb Website.
 
-23. Send the announcement mails to d...@servicecomb.apache.org, 
gene...@incubator.apache.org, annou...@apache.org
+4. Send the announcement mails to d...@servicecomb.apache.org, 
gene...@incubator.apache.org, annou...@apache.org
 
 
 
@@ -181,40 +183,41 @@ mvn deploy -DskipTests -Prelease -Pdistribution 
-Ppassphrase
 
 ***Sign the Releases***
 
-13. Download the source code and distribution from the staging repo.
+1. Download the source code and distribution from the staging repo.
+
+2. Sign the 2 releases(distribution, src) and checksum.
 
-14. Sign the 2 releases(distribution, src) and checksum.
+3. Create a new directory [Apache dev Release 
SVN](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-java-chassis/)
 with release package name and release candidate number. (for example : if you 
want to release 1.0.0-m2 and this is the first attempt of the release then the 
folder structure will be `1.0.0-m2/rc01`)
 
-15. Upload the release to [Apache dev released 
repository](https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-java-chassis/).

[incubator-servicecomb-website] 02/02: Update release_guide.md

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit e951fb0c8ed5aee262f43d9693ea398dc98ca0b4
Author: Mohammad Asif Siddiqui 
AuthorDate: Thu May 24 09:30:11 2018 +0530

Update release_guide.md
---
 _developers/release_guide.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/_developers/release_guide.md b/_developers/release_guide.md
index 87aee65..5914646 100644
--- a/_developers/release_guide.md
+++ b/_developers/release_guide.md
@@ -300,5 +300,3 @@ mvn deploy -DskipTests -Ppassphrase -Prelease
 
 **NOTE**
  - The whole process generally takes 2 weeks to complete assuming you don't 
get any -1 from PPMC and IMPC, so please plan the release activity before hand.
- - Make sure to clear all the release candidates from the dev-svn after the 
publishing the releases.
- 

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[incubator-servicecomb-website] branch master updated (7c5c20f -> e951fb0)

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a change to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git.


from 7c5c20f  fix small mistake
 new 2b56cef  Add the information of rc-directory to release guide
 new e951fb0  Update release_guide.md

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 _developers/release_guide.md | 93 +++-
 1 file changed, 49 insertions(+), 44 deletions(-)

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[GitHub] WillemJiang commented on issue #88: add healthcheck doc

2018-05-24 Thread GitBox

WillemJiang commented on issue #88: add healthcheck doc
URL: 
https://github.com/apache/incubator-servicecomb-website/pull/88#issuecomment-391599360
 
 
   Just changed e.printStackTrace() to LOG.error(xxx).


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[incubator-servicecomb-website] branch master updated (02fcf80 -> 7c5c20f)

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a change to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git.


from 02fcf80  Fixed the mailing list link
 new 7582391  add healthcheck
 new 7c5c20f  fix small mistake

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 _data/navigation.yml  |   4 ++
 _users/cn/healthcheck.md  |  84 ++
 _users/healthcheck.md |  84 ++
 assets/images/HealthCheck.png | Bin 0 -> 27349 bytes
 4 files changed, 172 insertions(+)
 create mode 100644 _users/cn/healthcheck.md
 create mode 100644 _users/healthcheck.md
 create mode 100644 assets/images/HealthCheck.png

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[GitHub] WillemJiang closed pull request #88: add healthcheck doc

2018-05-24 Thread GitBox

WillemJiang closed pull request #88: add healthcheck doc
URL: https://github.com/apache/incubator-servicecomb-website/pull/88
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/_data/navigation.yml b/_data/navigation.yml
index d4b9b41..80abed9 100755
--- a/_data/navigation.yml
+++ b/_data/navigation.yml
@@ -107,6 +107,8 @@ t:
 url: /users/metrics-in-1.0.0-m1/
   - title: Metrics-integration-with-prometheus-in-1.0.0-m1
 url: /users/metrics-integration-with-prometheus-in-1.0.0-m1/
+  - title: HealthCheck
+url: /users/healthcheck/
 
   - title: Deployment
 children:
@@ -270,6 +272,8 @@ t:
 url: /cn/users/metrics-write-file-extension-and-sample-in-1.0.0-m1/
   - title: 1.0.0-m1版本中的监控如何集成普罗米修斯
 url: /cn/users/metrics-integration-with-prometheus-in-1.0.0-m1/
+  - title: 健康检查
+url: /cn/users/healthcheck/
 
   - title: 部署
 children:
diff --git a/_users/cn/healthcheck.md b/_users/cn/healthcheck.md
new file mode 100644
index 000..6eab081
--- /dev/null
+++ b/_users/cn/healthcheck.md
@@ -0,0 +1,84 @@
+---
+title: "健康检查"
+lang: cn
+ref: healthcheck
+permalink: /cn/users/healthcheck/
+excerpt: "健康检查"
+last_modified_at: 2017-12-30T10:01:43-04:00
+redirect_from:
+  - /theme-setup/
+---
+
+{% include toc %}
+微服务框架从1.0.0-m1版本开始支持健康检查。
+
+## 介绍
+微服务往往依赖诸多中间件例如数据库、消息队列等，也依赖其他微服务。当微服务不可用时，例如是由于数据库不可用引起的，我们需要通过日志系统或监控面板将不可用的详细原因记录下或展示出来：磁盘空间满报错？数据库访问用户名密码变更？数据库访问权限变化？而不仅仅是一个报错不可用的状态，这会对快速定位问题和解决故障大有裨益。
+
+健康检查（HealthCheck）提供了一套扩展机制，用户可以自定义检查点，探测微服务内部核心依赖是否可用，如果不可用，将详细信息暴露出来：
+
+![HealthCheck](/assets/images/HealthCheck.png)
+
+## 如何使用
+### 实现自定义HealthCheck
+Java Chassis 
HealthCheck使用起来非常简单，只需要继承`org.apache.servicecomb.foundation.metrics.health.HealthChecker`接口，并实现方法：
+
+| 方法名   | 描述 |
+| :-- | :-- |
+| getName | 返回此健康检查的名称，请确保名称不要重复，否则从发布获取数据的时候合并覆盖 |
+| check | 具体的检查逻辑实现 |
+
+例如：
+```java
+public class MySqlHealthChecker implements HealthChecker {
+  @Override
+  public String getName() {
+return "mysql";
+  }
+
+  @Override
+  public HealthCheckResult check() {
+//add your health check code here
+Connection connection = null;
+try {
+  connection = 
DriverManager.getConnection("jdbc:mysql://localhost:3306/test_db?useSSL=false", 
"root", "pwd");
+  return new HealthCheckResult(true, "local mysql health check", "");
+} catch (SQLException e) {
+  e.printStackTrace();
+  return new HealthCheckResult(false, "local mysql health check", 
e.toString());
+} finally {
+  if (connection != null) {
+try {
+  connection.close();
+} catch (SQLException e) {
+  e.printStackTrace();
+}
+  }
+}
+  }
+}
+```
+
+然后使用SPI的方式加载它，具体为在`resource/META-INF/services`下创建`org.apache.servicecomb.foundation.metrics.health.HealthChecker`文件，然后写入实现的HealthCheck类名即可，例如：
+
+```text
+org.apache.servicecomb.samples.metrics.extendhealthcheck.MySqlHealthChecker
+```
+
+### 验证实现的HealthCheck
+启动微服务后，HealthCheck默认以Rest方式发布，发布地址与`servicecomb.rest.address`一致，如果在`microservice.yaml`中设置的配置为：
+
+```yaml
+servicecomb:
+  rest:
+address: 0.0.0.0:8080
+```
+
+那么就可以通过访问http://localhost:8080/health 
获取检查结果，以及访问http://localhost:8080/health/detail 获取所有的检查项结果明细。
+
+>说明：
+>1. HealthCheck的默认Rest发布实现在metrics-core中，因此需要增加此依赖；
+>2. 
/health为所有HealthCheck的最终结果，true或false，只要有任何一个HealthCheck的healthy结果为false，那么就会是false。
+
+## 参考示例
+我们已经提供了一个例子作为参考，代码在samples/metrics-extend-healthcheck中。
\ No newline at end of file
diff --git a/_users/healthcheck.md b/_users/healthcheck.md
new file mode 100644
index 000..ae25499
--- /dev/null
+++ b/_users/healthcheck.md
@@ -0,0 +1,84 @@
+---
+title: "HealthCheck"
+lang: en
+ref: healthcheck
+permalink: /users/healthcheck/
+excerpt: "HealthCheck"
+last_modified_at: 2017-12-30T10:01:43-04:00
+redirect_from:
+  - /theme-setup/
+---
+
+{% include toc %}
+Java Chassis had support HealthCheck since 1.0.0-m1.
+
+## Introduction
+Microservice always depend on many middlewares like database, message queue 
etc. Also depend on other microservices. When microservice is unavailable, may 
caused by database, we need record details into log file or show details on 
dashboard: database disk had full? database accress right had invalid? or 
database accress user and password had changed? not only a DOWN state, details 
can help dev ops find where is the problem and solve it faster.
+
+HealthCheck provide an extensible mechanism, user can create custom check 
point in order to probe whether the core dependencies are available, if any one 
is unavailable, report the details:
+
+![HealthCheck](/assets/images/HealthCheck.png)
+
+## How to use
+### Implement custom HealthCheck
+It is easy

[incubator-servicecomb-website] 02/02: fix small mistake

2018-05-24 Thread ningjiang

This is an automated email from the ASF dual-hosted git repository.

ningjiang pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/incubator-servicecomb-website.git

commit 7c5c20ff854768fd447578d01750d09f8ded47b5
Author: zhengyangyong 
AuthorDate: Tue May 22 08:55:39 2018 +0800

fix small mistake

Signed-off-by: zhengyangyong 
---
 _users/healthcheck.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/_users/healthcheck.md b/_users/healthcheck.md
index a83d7b5..ae25499 100644
--- a/_users/healthcheck.md
+++ b/_users/healthcheck.md
@@ -1,9 +1,9 @@
 ---
 title: "HealthCheck"
-lang: cn
+lang: en
 ref: healthcheck
 permalink: /users/healthcheck/
-excerpt: "健康检查"
+excerpt: "HealthCheck"
 last_modified_at: 2017-12-30T10:01:43-04:00
 redirect_from:
   - /theme-setup/

-- 
To stop receiving notification emails like this one, please contact
ningji...@apache.org.

[GitHub] WillemJiang commented on a change in pull request #88: add healthcheck doc

2018-05-24 Thread GitBox

WillemJiang commented on a change in pull request #88: add healthcheck doc
URL: 
https://github.com/apache/incubator-servicecomb-website/pull/88#discussion_r190473337
 
 

 ##
 File path: _users/cn/healthcheck.md
 ##
 @@ -0,0 +1,84 @@
+---
+title: "健康检查"
+lang: cn
+ref: healthcheck
+permalink: /cn/users/healthcheck/
+excerpt: "健康检查"
+last_modified_at: 2017-12-30T10:01:43-04:00
+redirect_from:
+  - /theme-setup/
+---
+
+{% include toc %}
+微服务框架从1.0.0-m1版本开始支持健康检查。
+
+## 介绍
+微服务往往依赖诸多中间件例如数据库、消息队列等，也依赖其他微服务。当微服务不可用时，例如是由于数据库不可用引起的，我们需要通过日志系统或监控面板将不可用的详细原因记录下或展示出来：磁盘空间满报错？数据库访问用户名密码变更？数据库访问权限变化？而不仅仅是一个报错不可用的状态，这会对快速定位问题和解决故障大有裨益。
+
+健康检查（HealthCheck）提供了一套扩展机制，用户可以自定义检查点，探测微服务内部核心依赖是否可用，如果不可用，将详细信息暴露出来：
+
+![HealthCheck](/assets/images/HealthCheck.png)
+
+## 如何使用
+### 实现自定义HealthCheck
+Java Chassis 
HealthCheck使用起来非常简单，只需要继承`org.apache.servicecomb.foundation.metrics.health.HealthChecker`接口，并实现方法：
+
+| 方法名   | 描述 |
+| :-- | :-- |
+| getName | 返回此健康检查的名称，请确保名称不要重复，否则从发布获取数据的时候合并覆盖 |
+| check | 具体的检查逻辑实现 |
+
+例如：
+```java
+public class MySqlHealthChecker implements HealthChecker {
+  @Override
+  public String getName() {
+return "mysql";
+  }
+
+  @Override
+  public HealthCheckResult check() {
+//add your health check code here
+Connection connection = null;
+try {
+  connection = 
DriverManager.getConnection("jdbc:mysql://localhost:3306/test_db?useSSL=false", 
"root", "pwd");
+  return new HealthCheckResult(true, "local mysql health check", "");
+} catch (SQLException e) {
+  e.printStackTrace();
 
 Review comment:
   It's not a good way to printStackTrace out directly.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

47 matches

Mail list logo