[jira] [Resolved] (SCB-438) As SC model is changing, we should keep SC proto spec in isolated project, so that go sdk can import same model as SC does
[ https://issues.apache.org/jira/browse/SCB-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui resolved SCB-438. Fix Version/s: service-center-2.0.0 Resolution: Fixed > As SC model is changing, we should keep SC proto spec in isolated project, so > that go sdk can import same model as SC does > -- > > Key: SCB-438 > URL: https://issues.apache.org/jira/browse/SCB-438 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Service-Center >Reporter: little-cui >Assignee: little-cui >Priority: Major > Fix For: service-center-2.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-624) Abstract service layer between api and cache
[ https://issues.apache.org/jira/browse/SCB-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui resolved SCB-624. Fix Version/s: service-center-2.0.0 Resolution: Fixed > Abstract service layer between api and cache > > > Key: SCB-624 > URL: https://issues.apache.org/jira/browse/SCB-624 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Service-Center >Reporter: little-cui >Assignee: little-cui >Priority: Major > Fix For: service-center-2.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2259) gopool can not reuse worker with certainty
[ https://issues.apache.org/jira/browse/SCB-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui resolved SCB-2259. - Fix Version/s: service-center-2.0.0 Resolution: Fixed > gopool can not reuse worker with certainty > -- > > Key: SCB-2259 > URL: https://issues.apache.org/jira/browse/SCB-2259 > Project: Apache ServiceComb > Issue Type: Bug > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: szt-sketch >Priority: Minor > Fix For: service-center-1.5.0, service-center-2.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2176) Fix: SD Cache is not consistency
[ https://issues.apache.org/jira/browse/SCB-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui resolved SCB-2176. - Fix Version/s: service-center-2.0.0 Resolution: Fixed > Fix: SD Cache is not consistency > > > Key: SCB-2176 > URL: https://issues.apache.org/jira/browse/SCB-2176 > Project: Apache ServiceComb > Issue Type: Bug > Components: Service-Center >Affects Versions: service-center-1.0.0, service-center-1.1.0, > service-center-1.2.0, service-center-1.3.0 >Reporter: Yihua Cui >Priority: Major > Fix For: service-center-1.5.0, service-center-2.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2133) governance northbound Interface / abstract access layer
[ https://issues.apache.org/jira/browse/SCB-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui resolved SCB-2133. - Fix Version/s: service-center-2.0.0 Resolution: Fixed > governance northbound Interface / abstract access layer > --- > > Key: SCB-2133 > URL: https://issues.apache.org/jira/browse/SCB-2133 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Reporter: YongLiang Guo >Assignee: YongLiang Guo >Priority: Major > Fix For: service-center-2.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2093) Supplement the role module of rbac
[
https://issues.apache.org/jira/browse/SCB-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
little-cui resolved SCB-2093.
-
Fix Version/s: service-center-2.0.0
Resolution: Fixed
> Supplement the role module of rbac
> --
>
> Key: SCB-2093
> URL: https://issues.apache.org/jira/browse/SCB-2093
> Project: Apache ServiceComb
> Issue Type: New Feature
> Components: Service-Center
>Reporter: Smart Yang
>Priority: Major
> Fix For: service-center-2.0.0
>
>
>
> *RBAC数据结构*
> *账户信息*
> ||accout||password||role||createTime||...||
> |{color:#4c9aff}root{color}| |{color:#4c9aff}admin{color}| | |
> | | |developer| | |
> | | |null| | |
> 1. 创建用户时，{color:#4c9aff}用户名和密码{color}是必须项
> 2. 账户可以{color:#4c9aff}新增和删除{color}，root用户不能删除，账户名不可以修改，账户均支持修改密码
> 3. 创建账号时若未添加角色信息，则默认为空角色，{color:#4c9aff}空角色不分配任何资源和权限{color}
> 4. 删除普通用户时， 若用户存在active token，有两种方案：
> a) 直接删除，包括该用户的角色（用户与角色为多对一关系）
> b) 使token失效，然后再删除
> 选用a方案，删除用户账号会删除用户所有信息
>
> *角色权限*
> *角色以及对应的权限*
> ||role||privilege||
> |admin| 允许超级用户在平台上的任何资源的所有操作。|
> |developer| 允许对除account资源等的所有操作|
> | | |
>
> 资源以及对应的操作：
> {code:json}
> {
> "account": {Verbs: ["get", "create", "update", "delete"]},
> "role":{Verbs: ["get", "create", "update", "delete"]},
> "service": {Verbs: ["get", "create", "update", "delete"]},
> "edit":{Verbs: ["create", "update"]},
> "view":{Verbs: ["get"]},
> .
> }}
> {code}
> 角色对应的资源（列表仅展示部分资源及api）以及相应的操作
>
> || role ||resource|| api
> || verbs
> ||
> |admin|account|/v4/token、/v4/account、/v4/account/\{name}|["get",
> "create", "update", "delete"]|
> | |role|/v4/role、/v4/role/\{roleName}|["get", "create", "update",
> "delete"]|
> |
> |service|/v4/\{project}/registry/microservices、/v4/\{project}/registry/microservices/\{serviceId}|["get",
> "create", "update", "delete"]|
> | |instance| |["get", "create", "update", "delete"]|
> |developer|role|/v4/role、/v4/role/\{roleName}|["get", "create", "update",
> "delete"]|
> |
> |service|/v4/\{project}/registry/microservices、/v4/\{project}/registry/microservices/\{serviceId}|["get",
> "create", "update", "delete"]|
> | |instance| |["get", "create", "update", "delete"]|
> |edit|service|/v4/\{project}/registry/microservices/\{serviceId}|["create",
> "update"]|
> | |instance| |["create", "update"]|
> |view|service|/v4/\{project}/registry/microservices|["get", "list"]|
> | |instance| |["get", "list"]|
> |null| | | |
>
>
> {color:#4c9aff}1. admin角色{color}拥有最高权限，允许超级用户在平台上的任何资源的所有操作，该角色不可修改删除；
> developer角色拥有除account资源的所有权限，且该角色不可修改删除；
> edit角色对部分资源拥有编辑权限，但没有查看和删除权限；
> view角色对部分资源只拥有查看权限
> 2. admin和developer角色所对应用户可以新增、删除角色
> 3.
> 添加的新角色后，需要对角色进行{color:#4c9aff}资源的分配{color}，以及资源对应的{color:#4c9aff}api列表和操作{color}，支持修改角色可访问的服务资源列表
> 4. 删除角色时会删除该角色所对应的权限列表，账户对应的角色会变成空角色，空角色的账户没有任何权限
>
> *REST API*
> *账户管理(已有API）*
>
> ||Method||Request URI ||Parameter ||Request Body||Description ||
> |POST|/v4/token|null|{ "id": "string", "{color:#0747a6}name{color}":
> "string", "{color:#0747a6}password{color}": "string", "role": "string",
> "tokenExprirationTime": "string", "currentPassword": "string", " status":
> "string" }|token is the only credential to access rest API, before you access
> any API, you need to get a token|
> |GET|/v4/account|token|null|list all user accounts|
> |POST|/v4/account|token|{ "id": "string", "{color:#4c9aff}name{color}":
> "string", "{color:#4c9aff}password{color}": "string", "role": "string",
> "tokenExprirationTime": "string", "currentPassword": "string", "status":
> "string" }|create user account|
> |GET|/v4/account/ \{name}|token、name|null| |
> |DELETE|v4/account/\{name}|token、name|null| |
> |POST|/v4/account/ \{name}/password|token、name| {
> "{color:#4c9aff}currentPassword{color}":"string",
> "{color:#4c9aff}password{color}":"string" }| |
>
> *角色权限管理*
> ||Method ||Request URI ||Parameter || Request Body || Description
> ||
> |GET|{color:#403294}/v4/role{color}|token|null|{color:#0747a6}查询{color}系统的role以及role对应的资源|
> |POST|{color:#403294}/v4/role{color}|token|{code:java}
> {
> roleId: "string"
> privilege：{
>id:
>resource:
>apiList:
>verbs:
> }
> }{code}|添加新角色并为新角色{color:#0747a6}添加API资源列表{color}|
> |PUT|{color:#403294}/v4/role/\{roleName}{color}|token|{code:java}
> {
> roleId: "string" privilege：{
> id:
> resource:
> apiList:
> verbs:
> } }{code}|修改角色可访问的{color:#0747a6}API资源列表{color}|
> |GET|{color:#403294}/v4/role/\{roleName}{color}|
> roleId、token|null|查询相应角色可访问的{color:#0747a6}API资源列表{color}，admin角色还将返回{color:#0747a6}account资源{color}|
> |DELETE |{color:#403294}/v4/role/\{roleName}{color}|roleId、token |null |
> 删除角色，但ad
[jira] [Resolved] (SCB-2022) Migrate service-center documents to sphinx
[ https://issues.apache.org/jira/browse/SCB-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui resolved SCB-2022. - Fix Version/s: service-center-2.0.0 Resolution: Fixed > Migrate service-center documents to sphinx > -- > > Key: SCB-2022 > URL: https://issues.apache.org/jira/browse/SCB-2022 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Service-Center >Affects Versions: service-center-1.3.0 >Reporter: Smart Yang >Priority: Major > Labels: documentation, pull-request-available > Fix For: service-center-2.0.0 > > > Use sphinx to manage documents -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SCB-1445) SC heartbeat failed suggest to multiplexing old instance， reduce sdk to update operation
[ https://issues.apache.org/jira/browse/SCB-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui closed SCB-1445. --- Resolution: Fixed sc will not register a new instance, just retry heartbeat until the kv expire in etcd > SC heartbeat failed suggest to multiplexing old instance， reduce sdk to > update operation > > > Key: SCB-1445 > URL: https://issues.apache.org/jira/browse/SCB-1445 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Service-Center >Affects Versions: service-center-1.2.0 >Reporter: JunhuiShen >Priority: Major > > SC sending itself heartbeat to etcd failed，sc will register new instance and > delete old instance, the sdk will gei the event and update the date, it will > adding useless operations can lead to unpredictable problems -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-1720) Service-center consumes huge CPU when it is disconnected from etcd
[ https://issues.apache.org/jira/browse/SCB-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui resolved SCB-1720. - Fix Version/s: service-center-2.0.0 Resolution: Fixed > Service-center consumes huge CPU when it is disconnected from etcd > -- > > Key: SCB-1720 > URL: https://issues.apache.org/jira/browse/SCB-1720 > Project: Apache ServiceComb > Issue Type: Bug > Components: Service-Center >Affects Versions: service-center-1.2.0 >Reporter: Mingcheng Hu >Priority: Major > Fix For: service-center-1.5.0, service-center-2.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-1712) Reset the etcd cache periodically
[ https://issues.apache.org/jira/browse/SCB-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui resolved SCB-1712. - Fix Version/s: service-center-2.0.0 service-center-1.5.0 Resolution: Fixed > Reset the etcd cache periodically > - > > Key: SCB-1712 > URL: https://issues.apache.org/jira/browse/SCB-1712 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Service-Center >Affects Versions: service-center-1.2.0 >Reporter: Yihua Cui >Priority: Major > Fix For: service-center-1.5.0, service-center-2.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-1545) add support env config for logfilepath and logfile level
[ https://issues.apache.org/jira/browse/SCB-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui resolved SCB-1545. - Fix Version/s: service-center-2.0.0 Resolution: Fixed > add support env config for logfilepath and logfile level > > > Key: SCB-1545 > URL: https://issues.apache.org/jira/browse/SCB-1545 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Service-Center >Reporter: lan.liang >Priority: Minor > Fix For: service-center-2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-952) Support sync ServiceComb service to Kubernetes
[ https://issues.apache.org/jira/browse/SCB-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui resolved SCB-952. Fix Version/s: service-center-2.0.0 Resolution: Fixed > Support sync ServiceComb service to Kubernetes > -- > > Key: SCB-952 > URL: https://issues.apache.org/jira/browse/SCB-952 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Reporter: little-cui >Assignee: little-cui >Priority: Major > Fix For: service-center-2.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-1042) Support upload SC schemas
[ https://issues.apache.org/jira/browse/SCB-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui resolved SCB-1042. - Fix Version/s: service-center-2.0.0 Resolution: Fixed > Support upload SC schemas > - > > Key: SCB-1042 > URL: https://issues.apache.org/jira/browse/SCB-1042 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Service-Center >Reporter: little-cui >Assignee: little-cui >Priority: Major > Fix For: service-center-2.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SCB-872) Push the vendors to git repository
[ https://issues.apache.org/jira/browse/SCB-872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui closed SCB-872. -- Resolution: Fixed Use go 1.14 instead > Push the vendors to git repository > -- > > Key: SCB-872 > URL: https://issues.apache.org/jira/browse/SCB-872 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Service-Center >Reporter: little-cui >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-1069) Wrong response of batch delete microservices API
[ https://issues.apache.org/jira/browse/SCB-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui resolved SCB-1069. - Fix Version/s: service-center-2.0.0 Resolution: Fixed > Wrong response of batch delete microservices API > > > Key: SCB-1069 > URL: https://issues.apache.org/jira/browse/SCB-1069 > Project: Apache ServiceComb > Issue Type: Bug > Components: Service-Center >Reporter: little-cui >Assignee: little-cui >Priority: Major > Fix For: service-center-1.5.0, service-center-2.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-489) Suggest to add Service Center user guide and development guide to the ServiceComb official website
[ https://issues.apache.org/jira/browse/SCB-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] little-cui resolved SCB-489. Fix Version/s: service-center-2.0.0 Resolution: Fixed > Suggest to add Service Center user guide and development guide to the > ServiceComb official website > -- > > Key: SCB-489 > URL: https://issues.apache.org/jira/browse/SCB-489 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Service-Center, website >Reporter: mabin >Priority: Major > Fix For: service-center-2.0.0 > > > Suggest to add Service Center user guide to the ServiceComb official > website,so that users can look up it more quickly. > Reference documents: > https://github.com/apache/incubator-servicecomb-service-center/tree/master/docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2094) New datasource architecture
[ https://issues.apache.org/jira/browse/SCB-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yihua Cui resolved SCB-2094. Fix Version/s: service-center-2.0.0 Resolution: Fixed > New datasource architecture > --- > > Key: SCB-2094 > URL: https://issues.apache.org/jira/browse/SCB-2094 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Service-Center >Reporter: Yihua Cui >Priority: Blocker > Fix For: service-center-2.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2273) support kie latest layered configurations
[ https://issues.apache.org/jira/browse/SCB-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-2273: Description: # support application, service, comstom 3 layered configurations # refactor kie client to use the same code in clients folder. > support kie latest layered configurations > - > > Key: SCB-2273 > URL: https://issues.apache.org/jira/browse/SCB-2273 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: liubao >Assignee: liubao >Priority: Major > Fix For: java-chassis-2.3.0 > > > # support application, service, comstom 3 layered configurations > # refactor kie client to use the same code in clients folder. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2273) support kie latest layered configurations
[ https://issues.apache.org/jira/browse/SCB-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-2273: Summary: support kie latest layered configurations (was: support kie lastest layered configurations) > support kie latest layered configurations > - > > Key: SCB-2273 > URL: https://issues.apache.org/jira/browse/SCB-2273 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: liubao >Assignee: liubao >Priority: Major > Fix For: java-chassis-2.3.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2273) support kie lastest layered configurations
liubao created SCB-2273: --- Summary: support kie lastest layered configurations Key: SCB-2273 URL: https://issues.apache.org/jira/browse/SCB-2273 Project: Apache ServiceComb Issue Type: New Feature Components: Java-Chassis Reporter: liubao Assignee: liubao Fix For: java-chassis-2.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
