Re: [Discussion] Create a new project servicecomb-service-center-istio

[Willem Ning Jiang]

Just create a page with the desgin document.

https://cwiki.apache.org/confluence/display/SERVICECOMB/servicecomb-service-center+istio+module

On 2022/06/17 02:20:02 Willem Ning Jiang wrote:
> Current mailing list doesn't support attachements.
> You can upload the image to other place and share the links in the email  or  
> you can put the design document in the wiki[1] of ServiceComb. 
> 
>  https://cwiki.apache.org/confluence/display/SERVICECOMB/Design+documents
> 
> Please ping me if you have any issue to access the wiki page.
> 
> 
> On 2022/06/16 20:00:53 Frenqucy Hz wrote:
> > Hi All,
> > 
> > 
> > Please ignore the previous email, the picture got broken.
> > 
> > 
> 

Re: [Discussion] Create a new project servicecomb-service-center-istio

[Willem Ning Jiang]

Current mailing list doesn't support attachements.
You can upload the image to other place and share the links in the email  or  
you can put the design document in the wiki[1] of ServiceComb. 

 https://cwiki.apache.org/confluence/display/SERVICECOMB/Design+documents

Please ping me if you have any issue to access the wiki page.


On 2022/06/16 20:00:53 Frenqucy Hz wrote:
> Hi All,
> 
> 
> Please ignore the previous email, the picture got broken.
> 
> 

Re: [Discussion] Create a new project servicecomb-service-center-istio

[Frenqucy Hz]

Hi All,


Please ignore the previous email, the picture got broken.


# 1. Problem statement and context



[image: image.png]

*Figure 1. The barrier between the two technology stacks*



In the process of application modernization, it is common for users to use
multiple microservice technology stacks (servicecomb-service-center and
istio) at the same time. So, they have a high demand to break the
communication barrier between two heterogeneous tech stacks which is caused
by the different Registration and Discovery mechanisms.



# 2. Our solution



[image: image.png]

*Figure 2. Our solution*



We propose a tool that can synchronize microservices from
servicecomb-service-center to Istio system which makes istio-based services
able to discover servicecomb-service-center-based services, refer to Figure
2.



## 2.1 Design


[image: image.png]

*Figure 3. Servicecomb-service-center structure*



As we can see from this Figure 3, servicecomb-service-center-istio
synchronizes service register information from servicecomb-service-center
side to istio side. It mainly does three steps:

· It watches servicecomb-service-center updates (microservice
instance status changes event: add, delete, update) via a WebSocket
connection.

· It converts servicecomb-service-center data model (microservice
and microservice instance) to Istio data model (ServiceEntry and
WorkloadEntry)

· It pushed the converted data model to the K8S api server through
REST api.



After doing all these steps, Istio automatically captures these converted
ServiceEntry and WorkloadEntry and dispatches them to each Envoy sidecar,
so that each sidecar can discover those servicecomb-service-center services.



If you have any questions please let me know.


Thank you,

Shiqi

>

Re: [Discussion] Create a new project servicecomb-service-center-istio

[Frenqucy Hz]

Hi All,

Here is our design proposal:

# 1. Problem statement and context



Figure 1. The barrier between the two technology stacks



In the process of application modernization, it is common for users to use
multiple microservice technology stacks (servicecomb-service-center and
istio) at the same time. So, they have a high demand to break the
communication barrier between two heterogeneous tech stacks which is caused
by the different Registration and Discovery mechanisms.



# 2. Our solution



Figure 2. Our solution



We propose a tool that can synchronizes microservices from
servicecomb-service-center to Istio system which makes istio-based services
are able to discover servicecomb-service-center-based services, refer to
Figure 2.



## 2.1 Design



Figure 3. Servicecomb-service-center structure



As we can see from this Figure 3, servicecomb-service-center-istio
synchronizes service register information from servicecomb-service-center
side to istio side. It mainly does three steps:

   - It watches servicecomb-service-center updates (microservice instance
   status changes event: add, delete, update) via a WebSocket connection.
   - It converts servicecomb-service-center data model (microservice and
   microservice instance) to Istio data model (ServiceEntry and WorkloadEntry)
   - It pushed converted data model to K8S api server through REST api.



After doing all these steps, Istio automatically captures these converted
ServiceEntry and WorkloadEntry and dispatches them to each Envoy sidecar,
so that each sidecar can discover those servicecomb-service-center services.


If you have any questions please let me know.


Thank you,

Shiqi

Re: [Discussion] Create a new project servicecomb-service-center-istio

[Frenqucy Hz]

Hi Willem,

Thanks for your reply.

I will go through those documents and sign SGA (I already implemented it).

I will write a detailed design proposal and share it here.

Thank you,
Shiqi

On Thu, Jun 16, 2022 at 9:29 AM Willem Jiang  wrote:

> Hi Shiqi
>
> Can you explain more detail about this project?
> It could be better if you can provide a design proposal for us to review.
> I think you can find a  the committer to help you review and merge the
> code.
>
> BTW, I’m not sure if you already wrote the code, if you do that you may
> need to sign a SGA first[1].
> If you do it from scratch, you may need to fill a iCLA[2] before submit
> any code to repo first.
> Anyway, please check out the contributor agreement[3] for more information.
>
> [1]https://www.apache.org/licenses/software-grant-template.pdf <
> https://www.apache.org/licenses/software-grant-template.pdf>
> [2]https://www.apache.org/licenses/icla.pdf <
> https://www.apache.org/licenses/icla.pdf>
> [3]https://www.apache.org/licenses/contributor-agreements.html <
> https://www.apache.org/licenses/contributor-agreements.html>
>
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> > On Jun 16, 2022, at 11:06, Frenqucy Hz  wrote:
> >
> > Hello all,
> >
> > I suggest creating a new project servicecomb-service-center-istio to
> > integrate servicecomb-service-center with istio, I will briefly introduce
> > why we are doing this project.
> >
> > *1. What is servicecomb-service-center-istio?*
> >
> >   - It's a tool that synchronizes servicecomb-service-center microservice
> >   registration information to Istio.
> >   - It enables the Istio service to discover microservices registered to
> >   servicecomb-service-center.
> >
> >
> > *2. Motivation?*
> >
> >
> >
> >   - Application Modernization customers who are migrating Microservices
> >   from the traditional Registry (servicecomb-service-center) to the
> Service
> >   Mesh (istio) have a high demand for this tool to break the
> communication
> >   barrier between two heterogeneous tech stacks which is caused by the
> >   different Registration and Discovery mechanisms.
> >   - Other communities (Nacos
> >    and consul
> >   ) already have this
> >   capability.
> >
> > Any ideas?
> >
> > Regards,
> > Shiqi
>
>

Re: [Discussion] Create a new project servicecomb-service-center-istio

[Willem Jiang]

Hi Shiqi

Can you explain more detail about this project?
It could be better if you can provide a design proposal for us to review.
I think you can find a  the committer to help you review and merge the code. 

BTW, I’m not sure if you already wrote the code, if you do that you may need to 
sign a SGA first[1].
If you do it from scratch, you may need to fill a iCLA[2] before submit any 
code to repo first.
Anyway, please check out the contributor agreement[3] for more information.

[1]https://www.apache.org/licenses/software-grant-template.pdf 

[2]https://www.apache.org/licenses/icla.pdf 

[3]https://www.apache.org/licenses/contributor-agreements.html 




Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

> On Jun 16, 2022, at 11:06, Frenqucy Hz  wrote:
> 
> Hello all,
> 
> I suggest creating a new project servicecomb-service-center-istio to
> integrate servicecomb-service-center with istio, I will briefly introduce
> why we are doing this project.
> 
> *1. What is servicecomb-service-center-istio?*
> 
>   - It's a tool that synchronizes servicecomb-service-center microservice
>   registration information to Istio.
>   - It enables the Istio service to discover microservices registered to
>   servicecomb-service-center.
> 
> 
> *2. Motivation?*
> 
> 
> 
>   - Application Modernization customers who are migrating Microservices
>   from the traditional Registry (servicecomb-service-center) to the Service
>   Mesh (istio) have a high demand for this tool to break the communication
>   barrier between two heterogeneous tech stacks which is caused by the
>   different Registration and Discovery mechanisms.
>   - Other communities (Nacos
>    and consul
>   ) already have this
>   capability.
> 
> Any ideas?
> 
> Regards,
> Shiqi

Re: [Discussion] Create a new project servicecomb-service-center-istio

[Jianwen Luo]

+1 

On 2022/06/16 03:06:08 Frenqucy Hz wrote:
> Hello all,
> 
> I suggest creating a new project servicecomb-service-center-istio to
> integrate servicecomb-service-center with istio, I will briefly introduce
> why we are doing this project.
> 
> *1. What is servicecomb-service-center-istio?*
> 
>- It's a tool that synchronizes servicecomb-service-center microservice
>registration information to Istio.
>- It enables the Istio service to discover microservices registered to
>servicecomb-service-center.
> 
> 
> *2. Motivation?*
> 
> 
> 
>- Application Modernization customers who are migrating Microservices
>from the traditional Registry (servicecomb-service-center) to the Service
>Mesh (istio) have a high demand for this tool to break the communication
>barrier between two heterogeneous tech stacks which is caused by the
>different Registration and Discovery mechanisms.
>- Other communities (Nacos
> and consul
>) already have this
>capability.
> 
> Any ideas?
> 
> Regards,
> Shiqi
> 

RE: 回复：[Discussion] Create a new project servicecomb-service-center-istio

[Jun Gan]

+1

Motivation is strong... we need to bridge this gap for Servicecomb community 


-Original Message-
From: bismy [mailto:bi...@qq.com.INVALID] 
Sent: Thursday, June 16, 2022 2:54 AM
To: dev 
Subject: 回复：[Discussion] Create a new project servicecomb-service-center-istio

+1
Sounds a good idea. 

-- 原始邮件 --
发件人: "dev" ;
发送时间: 2022年6月16日(星期四) 中午11:06
收件人: "dev";
主题: [Discussion] Create a new project servicecomb-service-center-istio

Hello all,

I suggest creating a new project servicecomb-service-center-istio to integrate 
servicecomb-service-center with istio, I will briefly introduce why we are 
doing this project.

*1. What is servicecomb-service-center-istio?*

   - It's a tool that synchronizes servicecomb-service-center microservice
   registration information to Istio.
   - It enables the Istio service to discover microservices registered to
   servicecomb-service-center.


*2. Motivation?*



   - Application Modernization customers who are migrating Microservices
   from the traditional Registry (servicecomb-service-center) to the Service
   Mesh (istio) have a high demand for this tool to break the communication
   barrier between two heterogeneous tech stacks which is caused by the
   different Registration and Discovery mechanisms.
   - Other communities (Nacos
and 
consul
   ) already have this
   capability.

Any ideas?

Regards,
Shiqi

??????[Discussion] Create a new project servicecomb-service-center-istio

[bismy]

+1
Sounds a good idea. 

--  --
??: "dev" ;
: 2022??6??16??(??) 11:06
??: "dev";
: [Discussion] Create a new project servicecomb-service-center-istio

Hello all,

I suggest creating a new project servicecomb-service-center-istio to
integrate servicecomb-service-center with istio, I will briefly introduce
why we are doing this project.

*1. What is servicecomb-service-center-istio?*

   - It's a tool that synchronizes servicecomb-service-center microservice
   registration information to Istio.
   - It enables the Istio service to discover microservices registered to
   servicecomb-service-center.


*2. Motivation?*



   - Application Modernization customers who are migrating Microservices
   from the traditional Registry (servicecomb-service-center) to the Service
   Mesh (istio) have a high demand for this tool to break the communication
   barrier between two heterogeneous tech stacks which is caused by the
   different Registration and Discovery mechanisms.
   - Other communities (Nacos
and 
consul
   ) already have this
   capability.

Any ideas?

Regards,
Shiqi