You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2021/12/05 15:09:39 UTC
[GitHub] [apisix] alex8224 opened a new issue #5706: request help: How to route according to the configuration of nacos metadata?
alex8224 opened a new issue #5706:
URL: https://github.com/apache/apisix/issues/5706
### Issue description
I use nacos discovery, and for each microservice I register some additional metadata for finer-grained control
I know that the traffic-split plugin can match routes at a certain level of granularity
As far as I know, this plugin can't match upstreams based on metadata level
So, I would like to ask how to do this
Tks
### Environment
- apisix 2.10.2
- Centos7
- openresty/1.19.3.2
- etcd 3.5.0
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] xuminwlt commented on issue #5706: request help: How to route according to the configuration of nacos metadata?
Posted by GitBox <gi...@apache.org>.
xuminwlt commented on issue #5706:
URL: https://github.com/apache/apisix/issues/5706#issuecomment-987902430
+1
need too.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] alex8224 commented on issue #5706: request help: How to route according to the configuration of nacos metadata?
Posted by GitBox <gi...@apache.org>.
alex8224 commented on issue #5706:
URL: https://github.com/apache/apisix/issues/5706#issuecomment-988023902
@tzssangglass
**If so, that's pretty good**
Generally use the 127.0.0.1:8848/nacos/v1/ns/instance/list?serviceName=xxx&namespaceId=dev interface to get all service instances under a namespaceId, The output of the interface call is as follows
`{
"allIPs": false,
"cacheMillis": 10000,
"checksum": "",
"clusters": "",
"groupName": "DEFAULT_GROUP",
"hosts": [
{
"clusterName": "DEFAULT",
"enabled": true,
"ephemeral": true,
"healthy": true,
"instanceHeartBeatInterval": 5000,
"instanceHeartBeatTimeOut": 15000,
"instanceId": "192.26.0.7#9088#DEFAULT#DEFAULT_GROUP@@xxx",
"ip": "192.26.0.7",
"ipDeleteTimeout": 30000,
"metadata": {
"app.name": "xxxr",
"preserved.register.source": "SPRING_CLOUD",
"startup.time": "1638849194096",
"tag": "gray-feature-v1"
},
"port": 9088,
"serviceName": "DEFAULT_GROUP@@bcs-server",
"weight": 1.0
}
],
"lastRefTime": 1638890095796,
"name": "DEFAULT_GROUP@@bcs-server",
"reachProtectionThreshold": false,
"valid": true } `
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] tzssangglass commented on issue #5706: request help: How to route according to the configuration of nacos metadata?
Posted by GitBox <gi...@apache.org>.
tzssangglass commented on issue #5706:
URL: https://github.com/apache/apisix/issues/5706#issuecomment-986265060
> I know that the traffic-split plugin can match routes at a certain level of granularity
the ` traffic-split` plugin is not involved in route matching.
Are you trying to select upstream based on the additional information obtained in nacos?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] tokers commented on issue #5706: request help: How to route according to the configuration of nacos metadata?
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #5706:
URL: https://github.com/apache/apisix/issues/5706#issuecomment-986342395
@alex8224 You may implement your own balancer and use it in `Upstream` objects.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] alex8224 edited a comment on issue #5706: request help: How to route according to the configuration of nacos metadata?
Posted by GitBox <gi...@apache.org>.
alex8224 edited a comment on issue #5706:
URL: https://github.com/apache/apisix/issues/5706#issuecomment-986914757
> > @alex8224 You may implement your own balancer and use it in `Upstream` objects.
>
> See https://apisix.apache.org/blog/2021/07/28/release-apache-apisix-2.8/#new-way-to-develop-support-for-custom-balancer .
I can only find very little about how to implement a balancer from the url you gave, are there other more detailed guides on how to easily add a balancer type?
For example.
1. at what stage does the nacos metadata information get and where is it placed?
2. where to add require("apisix.balancer.your_balancer")?
3. what functions should I implement in my custom balancer?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] tzssangglass commented on issue #5706: request help: How to route according to the configuration of nacos metadata?
Posted by GitBox <gi...@apache.org>.
tzssangglass commented on issue #5706:
URL: https://github.com/apache/apisix/issues/5706#issuecomment-987464045
> 1. at what stage does the nacos metadata information get and where is it placed?
You can see how the service registration information for nacos is obtained and how it is stored in nacos.lua. e.g. https://github.com/apache/apisix/blob/master/apisix/discovery/nacos/init.lua#L216-L230
> 2. where to add require("apisix.balancer.your_balancer")?
your_balancer is placed in the apisix/balancer folder
> 3. what functions should I implement in my custom balancer?
take a look at: https://github.com/apache/apisix/blob/master/apisix/balancer/roundrobin.lua
BTW, I think this is a bit difficult, if you haven't had experience developing plugins before.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] tzssangglass commented on issue #5706: request help: How to route according to the configuration of nacos metadata?
Posted by GitBox <gi...@apache.org>.
tzssangglass commented on issue #5706:
URL: https://github.com/apache/apisix/issues/5706#issuecomment-987915215
Maybe we can enhance nacos discovery to make it work. Would anyone like to give a detailed example? For example, from which interface of nacos do we get information? What information is being fetched?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] alex8224 edited a comment on issue #5706: request help: How to route according to the configuration of nacos metadata?
Posted by GitBox <gi...@apache.org>.
alex8224 edited a comment on issue #5706:
URL: https://github.com/apache/apisix/issues/5706#issuecomment-988023902
@tzssangglass
**If so, that's pretty good**
Generally use the 127.0.0.1:8848/nacos/v1/ns/instance/list?serviceName=xxx&namespaceId=dev interface to get all service instances under a namespaceId, The output of the interface call is as follows
```json
{
"allIPs":false,
"cacheMillis":10000,
"checksum":"",
"clusters":"",
"groupName":"DEFAULT_GROUP",
"hosts":[
{
"clusterName":"DEFAULT",
"enabled":true,
"ephemeral":true,
"healthy":true,
"instanceHeartBeatInterval":5000,
"instanceHeartBeatTimeOut":15000,
"instanceId":"192.26.0.7#9088#DEFAULT#DEFAULT_GROUP@@xxx",
"ip":"192.26.0.7",
"ipDeleteTimeout":30000,
"metadata":{
"app.name":"xxx",
"preserved.register.source":"SPRING_CLOUD",
"startup.time":"1638849194096",
"dept":"HR"
},
"port":9088,
"serviceName":"DEFAULT_GROUP@@xxx",
"weight":1.0
},
{
"clusterName":"DEFAULT",
"enabled":true,
"ephemeral":true,
"healthy":true,
"instanceHeartBeatInterval":5000,
"instanceHeartBeatTimeOut":15000,
"instanceId":"192.26.0.6#9088#DEFAULT#DEFAULT_GROUP@@xxx",
"ip":"192.26.0.6",
"ipDeleteTimeout":30000,
"metadata":{
"app.name":"xxx",
"preserved.register.source":"SPRING_CLOUD",
"startup.time":"1638849194096",
"dept":"IT"
},
"port":9088,
"serviceName":"DEFAULT_GROUP@@xxx",
"weight":1.0
},
{
"clusterName":"DEFAULT",
"enabled":true,
"ephemeral":true,
"healthy":true,
"instanceHeartBeatInterval":5000,
"instanceHeartBeatTimeOut":15000,
"instanceId":"192.26.0.9#9088#DEFAULT#DEFAULT_GROUP@@xxx",
"ip":"192.26.0.9",
"ipDeleteTimeout":30000,
"metadata":{
"app.name":"xxx",
"preserved.register.source":"SPRING_CLOUD",
"startup.time":"1638849194096",
"dept":"HRP"
},
"port":9088,
"serviceName":"DEFAULT_GROUP@@xxx",
"weight":1.0
}
],
"lastRefTime":1638890095796,
"name":"DEFAULT_GROUP@@bcs-server",
"reachProtectionThreshold":false,
"valid":true
}```
There are several scenarios as follows
route url = /xxx/*
When the client requests /xxx/*
When header ["X-Real-Ip"] between ["192.168.1-192.168.1.10"], the request is routed to the instance node with metadata field dept == HR, in this case node 192.26.0.7
Other requests that do not match are routed to nodes that do not match, in this case to 192.26.0.6 and 192.26.0.9
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] alex8224 commented on issue #5706: request help: How to route according to the configuration of nacos metadata?
Posted by GitBox <gi...@apache.org>.
alex8224 commented on issue #5706:
URL: https://github.com/apache/apisix/issues/5706#issuecomment-986364982
@tzssangglass yes, I want to select upstream based on metadata obtained in nacos.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] alex8224 edited a comment on issue #5706: request help: How to route according to the configuration of nacos metadata?
Posted by GitBox <gi...@apache.org>.
alex8224 edited a comment on issue #5706:
URL: https://github.com/apache/apisix/issues/5706#issuecomment-986914757
> > @alex8224 You may implement your own balancer and use it in `Upstream` objects.
>
> See https://apisix.apache.org/blog/2021/07/28/release-apache-apisix-2.8/#new-way-to-develop-support-for-custom-balancer .
@tokers
I can only find very little about how to implement a balancer from the url you gave, are there other more detailed guides on how to easily add a balancer type?
For example.
1. at what stage does the nacos metadata information get and where is it placed?
2. where to add require("apisix.balancer.your_balancer")?
3. what functions should I implement in my custom balancer?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] tokers commented on issue #5706: request help: How to route according to the configuration of nacos metadata?
Posted by GitBox <gi...@apache.org>.
tokers commented on issue #5706:
URL: https://github.com/apache/apisix/issues/5706#issuecomment-986342755
> @alex8224 You may implement your own balancer and use it in `Upstream` objects.
See https://apisix.apache.org/blog/2021/07/28/release-apache-apisix-2.8/#new-way-to-develop-support-for-custom-balancer .
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] alex8224 commented on issue #5706: request help: How to route according to the configuration of nacos metadata?
Posted by GitBox <gi...@apache.org>.
alex8224 commented on issue #5706:
URL: https://github.com/apache/apisix/issues/5706#issuecomment-986914757
> > @alex8224 You may implement your own balancer and use it in `Upstream` objects.
>
> See https://apisix.apache.org/blog/2021/07/28/release-apache-apisix-2.8/#new-way-to-develop-support-for-custom-balancer .
I can only find very little about how to implement a balancer from the url you gave, are there other more detailed guides on how to easily add a balancer type?
Similar to implementing a new discovery type.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org