federatedai / fate-cloud

Infrastructure for building and managing Federated Data Collaboration Network

The project is not maintained since 2022

DOC|中文

Overview

As an infrastructure for building and managing Federated Data Collaboration Network, FATE Cloud is the first industrial-grade Federated Learning Cloud Service.

FATE Cloud enables FATE to be managed in multi-cloud, forming a secure federated data network, designed to provide a secure and compliant data cooperation solutions across or within organizations, and provide an enterprise-level federated learning productivity application solution.

FATE-Cloud provides standard federated infrastructure implementation capabilities, technical support capabilities, a unified federated site management mode and the whole process service, and addresses the problems of management collaboration, data processing and authentication, low cooperation efficiency, and poor interaction among different organizations.

Major features

FATE Cloud is composed of Cloud Manager, which is responsible for federated site management, and FATE Manager, a site client management terminal. It provides registration and management of federated sites, automated cluster deployment and upgrades, cluster monitoring, and permission control and other core functions.

Federated Cloud（Cloud Manager）

Cloud Manager is the management center of the federated network, which is responsible for the unified operation and management of FATE Manager and each site, monitors the services of the site and Federated cooperation modeling, performs the federated permission control, and ensures the normal operation of federated data cooperation network.

Federated Site（FATE Manager）

FATE Manager is responsible for the management and maintenance of their respective federated sites, providing services such as a site joining the Federation Organization, automatic deployment and upgrade of a site, monitor of the federated cooperation modeling and cluster services of a site, and management of user roles and application permissions of a site, etc.

Deploy

FATE Cloud Deployment:

• Method 1(ansible): FATE-Cloud
• Method 2(separate deployment): Cloud-Manager and FATE-Manager

Other related module Deployment:

• Exchange

Usage

After deployment，please prefer to "FATE Cloud product manual" for detailed usage of FATE Cloud.

FAQ

Cloud Manager failed to deploy.

• Confirm that the server used for deployment has a maven environment. It's used to build the jar package of Cloud Manager.
• Confirm that SSH password-free login is configured between the deployment server and the target server.

Cloud Manager failed to start.

• Cloud Manager is a java service. Please confirm that the target machine has a jdk8 environment.
• Cloud Manager depends upon MySQL. Please confirm that the configurations of MySQL is correct.
• Provide enough memory for the service.
• Confirm that the port number is not occupied.

Cloud Manager access failed.

• Confirm that the port can be accessed. The port needs to be opened by the firewall.

FATE Manager failed to start.

• Check whether kubectl has the permission of sudo. If so, modify the configuration file sudotag=true.
• Check whether the link configuration of MySQL if normal.

Failed to connect deployment.

• Check whether the url of KubeFATE carries port number.
• Check whether KubeFATE’s service is normal.

FATE deployment failed.

• Check the log for analysis to ensure that the mode machine has access to dockerhub, or the docker image has been loaded in advance.

Autotest failed in deployment.

• Check whether the routing table of the rollsite is configured correctly.

fate-cloud's Issues

frontend dependencies update

update axios from 0.18.0 to 0.19.2
update webpack-bundle-analyzer from 2.13.1 to 3.4.0

update route table error by grpc

When I configure the fate-exchange component deployed by k8s in fate-cloud, I trace the code according to the abnormal information. What is going on?

FATE-Cloud/cloud-manager/src/main/java/com/webank/ai/fatecloud/system/service/impl/FederatedExchangeService.java

Line 257 in 57ebb8e

log.info("query response from exchange : {}", routerTableString);

2022-03-01 15:04:28 INFO [http-nio-8998-exec-6] (FederatedExchangeService.java:257) - query response from exchange : getRouteTable failed. Token verification failed.

2022-03-01 15:04:28 ERROR [http-nio-8998-exec-5] (FederatedExchangeService.java:260) - update route table error by grpc 
com.alibaba.fastjson.JSONException: syntax error, pos 1, line 1, column 2getRouteTable failed. Token verification failed.
        at com.alibaba.fastjson.parser.DefaultJSONParser.parse(DefaultJSONParser.java:1481)
        at com.alibaba.fastjson.parser.DefaultJSONParser.parse(DefaultJSONParser.java:1367)
        at com.alibaba.fastjson.JSON.parse(JSON.java:183)
        at com.alibaba.fastjson.JSON.parse(JSON.java:193)
        at com.alibaba.fastjson.JSON.parse(JSON.java:149)
        at com.alibaba.fastjson.JSON.parseObject(JSON.java:254)
        at com.webank.ai.fatecloud.system.service.impl.FederatedExchangeService.buildPartyList(FederatedExchangeService.java:196)
        at com.webank.ai.fatecloud.system.service.impl.FederatedExchangeService.queryExchange(FederatedExchangeService.java:258)
        at com.webank.ai.fatecloud.system.service.impl.FederatedExchangeService$$FastClassBySpringCGLIB$$c1d26398.invoke(<generated>)
        at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)

exchange and fate-cloud are deployed on the same machine.
@
thanks!

The routing table not have current party=exchange and default party

hi bro, when I added the exchange route, the log information prompted me to encounter the following problems.

[ERROR][13327122][2022-02-14 13:54:38,802][grpc-server-9370-12,pid:28998,tid:41][c.w.e.r.EggSiteServicer:144] - [UNARYCALL][SERVER] onError. rsKey=__rsk#######, metadata={"dst":{"name":"","partyId":"exchange","role":""},"operator":"get_route_table","seq":"0","ack":"0","ext":"","version":""}
io.grpc.StatusRuntimeException: UNKNOWN:
[Roll Site Error TransInfo]
location msg=The routing table not have current party=exchange and default party
stack info=java.lang.Exception: The routing table not have current party=exchange and default party
at com.webank.eggroll.rollsite.Router$.query(Router.scala:41)
at com.webank.eggroll.rollsite.EggSiteServicer.unaryCall(EggSiteServicer.scala:80)
at com.webank.ai.eggroll.api.networking.proxy.DataTransferServiceGrpc$MethodHandlers.invoke(DataTransferServiceGrpc.java:406)
at io.grpc.stub.ServerCalls$UnaryServerCallHandler$UnaryServerCallListener.onHalfClose(ServerCalls.java:172)
at io.grpc.PartialForwardingServerCallListener.onHalfClose(PartialForwardingServerCallListener.java:35)
at io.grpc.ForwardingServerCallListener.onHalfClose(ForwardingServerCallListener.java:23)
at io.grpc.ForwardingServerCallListener$SimpleForwardingServerCallListener.onHalfClose(ForwardingServerCallListener.java:40)
at io.grpc.Contexts$ContextualizedServerCallListener.onHalfClose(Contexts.java:86)
at io.grpc.internal.ServerCallImpl$ServerStreamListenerImpl.halfClosed(ServerCallImpl.java:331)
at io.grpc.internal.ServerImpl$JumpToApplicationThreadServerStreamListener$1HalfClosed.runInContext(ServerImpl.java:817)
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

exception trans path: 192.168.0.3(exchange)
at io.grpc.Status.asRuntimeException(Status.java:524) ~[grpc-api-1.27.2.jar:1.27.2]
at com.webank.eggroll.rollsite.TransferExceptionUtils$.throwableToException(TransferExceptionUtils.scala:43) ~[eggroll-roll-site-2.4.2.jar:?]
at com.webank.eggroll.rollsite.EggSiteServicer.unaryCall(EggSiteServicer.scala:154) [eggroll-roll-site-2.4.2.jar:?]
at com.webank.ai.eggroll.api.networking.proxy.DataTransferServiceGrpc$MethodHandlers.invoke(DataTransferServiceGrpc.java:406) [eggroll-core-2.2.2.jar:?]
at io.grpc.stub.ServerCalls$UnaryServerCallHandler$UnaryServerCallListener.onHalfClose(ServerCalls.java:172) [grpc-stub-1.27.2.jar:1.27.2]
at io.grpc.PartialForwardingServerCallListener.onHalfClose(PartialForwardingServerCallListener.java:35) [grpc-api-1.27.2.jar:1.27.2]
at io.grpc.ForwardingServerCallListener.onHalfClose(ForwardingServerCallListener.java:23) [grpc-api-1.27.2.jar:1.27.2]
at io.grpc.ForwardingServerCallListener$SimpleForwardingServerCallListener.onHalfClose(ForwardingServerCallListener.java:40) [grpc-api-1.27.2.jar:1.27.2]
at io.grpc.Contexts$ContextualizedServerCallListener.onHalfClose(Contexts.java:86) [grpc-api-1.27.2.jar:1.27.2]
at io.grpc.internal.ServerCallImpl$ServerStreamListenerImpl.halfClosed(ServerCallImpl.java:331) [grpc-core-1.27.2.jar:1.27.2]
at io.grpc.internal.ServerImpl$JumpToApplicationThreadServerStreamListener$1HalfClosed.runInContext(ServerImpl.java:817) [grpc-core-1.27.2.jar:1.27.2]
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) [grpc-core-1.27.2.jar:1.27.2]
at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123) [grpc-core-1.27.2.jar:1.27.2]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_171]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_171]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
Caused by: java.lang.Exception: The routing table not have current party=exchange and default party
at com.webank.eggroll.rollsite.Router$.query(Router.scala:41) ~[eggroll-roll-site-2.4.2.jar:?]
at com.webank.eggroll.rollsite.EggSiteServicer.unaryCall(EggSiteServicer.scala:80) [eggroll-roll-site-2.4.2.jar:?]
... 13 more

please how can i solve it, thanks!

fate-cloud有没有docker或者k8s的部署方式

fata manager 1.3.0

adjust fate manager directory stucture

fate-cloud 透過 ansible 部署模式中下載檔案出錯

fate-cloud 版本: 1.4.1
在透过 asnsible 部署 fate-cloud 模式下执行 sh build/build.sh do 做下载所需 pkg 时动作时出现以下错误:


看似 https://webank-ai-1251170195.cos.ap-guangzhou.myqcloud.com/fate_cloud_python-1.4.1.tar.gz, https://webank-ai-1251170195.cos.ap-guangzhou.myqcloud.com/jdk-8u192.tar url 是有问题的？再麻烦解惑一下～感谢!

Issue with fields

Is there any documentation regarding Network Access Entrances and Network Access Exits, What would be example values for deployment

连接rollsite错误：ROLLSITE_GRPC_ERROR(137, "Connect this rollsite error!") when adding an exchange

版本 1.4

使用KubeFate以docker-compose方式配置好FATE，并分别部署Fate-manager, cloud-manager, 按照使用手册运行，在添加Exchange时出现 “连接此Rollsite错误！" 报错。

FATE可成功运行双边测试，以及执行其他任务。

logs: /data/projects/cloud-manager/logs/2021-09-21/info.2021-09-21.log in cloud-manager

2021-09-21 13:22:00 �[34mINFO �[0;39m [pool-2-thread-1] (FederatedModelService.java:158) - start detective
2021-09-21 13:23:14 �[34mINFO �[0;39m [http-nio-9999-exec-8] (FederatedExchangeController.java:50) - url:find paged exchange, requestBody:ExchangeQueryQo(networkAccess=47.100.xx.xx:9370)
2021-09-21 13:23:14 �[34mINFO �[0;39m [http-nio-9999-exec-8] (FederatedExchangeService.java:250) - query request to exchange, ip:47.100.xx.xx,port:9370, key:exchange, partyId:admin, operator:get_route_table
2021-09-21 13:24:00 �[34mINFO �[0;39m [pool-2-thread-1] (FederatedModelService.java:158) - start detective

logs: /data/projects/fate/eggroll/logs/eggroll/eggroll.jvm.log in rollsite

[INFO ][54572][2021-09-21 13:23:14,502][grpc-server-9370-0,pid:7,tid:17][audit:87] - dst={partyId=admin}|operator=get_route_table
[ERROR][54696][2021-09-21 13:23:14,626][grpc-server-9370-0,pid:7,tid:17][c.w.e.r.EggSiteServicer:144] - [UNARYCALL][SERVER] onError. rsKey=__rsk#######, metadata={"dst":{"name":"","partyId":"admin","role":""},"operator":"get_route_table","seq":"0","ack":"0","ext":"","version":""}
io.grpc.StatusRuntimeException: UNKNOWN: UNKNOWN: 
[Roll Site Error TransInfo] 
 location msg=JSONObject["ip"] not found. 
 stack info=org.json.JSONException: JSONObject["ip"] not found.
	at org.json.JSONObject.get(JSONObject.java:471)
	at com.webank.eggroll.rollsite.Router$.query(Router.scala:79)
	at com.webank.eggroll.rollsite.EggSiteServicer.unaryCall(EggSiteServicer.scala:80)
	at com.webank.ai.eggroll.api.networking.proxy.DataTransferServiceGrpc$MethodHandlers.invoke(DataTransferServiceGrpc.java:406)
	at io.grpc.stub.ServerCalls$UnaryServerCallHandler$UnaryServerCallListener.onHalfClose(ServerCalls.java:172)
	at io.grpc.PartialForwardingServerCallListener.onHalfClose(PartialForwardingServerCallListener.java:35)
	at io.grpc.ForwardingServerCallListener.onHalfClose(ForwardingServerCallListener.java:23)
	at io.grpc.ForwardingServerCallListener$SimpleForwardingServerCallListener.onHalfClose(ForwardingServerCallListener.java:40)
	at io.grpc.Contexts$ContextualizedServerCallListener.onHalfClose(Contexts.java:86)
	at io.grpc.internal.ServerCallImpl$ServerStreamListenerImpl.halfClosed(ServerCallImpl.java:331)
	at io.grpc.internal.ServerImpl$JumpToApplicationThreadServerStreamListener$1HalfClosed.runInContext(ServerImpl.java:817)
	at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
	at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
 

exception trans path: rollsite(exchange) --> rollsite(9998)
	at io.grpc.Status.asRuntimeException(Status.java:524) ~[grpc-api-1.27.2.jar:1.27.2]
	at com.webank.eggroll.rollsite.TransferExceptionUtils$.throwableToException(TransferExceptionUtils.scala:43) ~[eggroll-roll-site-2.2.1.jar:?]
	at com.webank.eggroll.rollsite.EggSiteServicer.unaryCall(EggSiteServicer.scala:152) [eggroll-roll-site-2.2.1.jar:?]
	at com.webank.ai.eggroll.api.networking.proxy.DataTransferServiceGrpc$MethodHandlers.invoke(DataTransferServiceGrpc.java:406) [eggroll-core-2.2.1.jar:?]
	at io.grpc.stub.ServerCalls$UnaryServerCallHandler$UnaryServerCallListener.onHalfClose(ServerCalls.java:172) [grpc-stub-1.27.2.jar:1.27.2]
	at io.grpc.PartialForwardingServerCallListener.onHalfClose(PartialForwardingServerCallListener.java:35) [grpc-api-1.27.2.jar:1.27.2]
	at io.grpc.ForwardingServerCallListener.onHalfClose(ForwardingServerCallListener.java:23) [grpc-api-1.27.2.jar:1.27.2]
	at io.grpc.ForwardingServerCallListener$SimpleForwardingServerCallListener.onHalfClose(ForwardingServerCallListener.java:40) [grpc-api-1.27.2.jar:1.27.2]
	at io.grpc.Contexts$ContextualizedServerCallListener.onHalfClose(Contexts.java:86) [grpc-api-1.27.2.jar:1.27.2]
	at io.grpc.internal.ServerCallImpl$ServerStreamListenerImpl.halfClosed(ServerCallImpl.java:331) [grpc-core-1.27.2.jar:1.27.2]
	at io.grpc.internal.ServerImpl$JumpToApplicationThreadServerStreamListener$1HalfClosed.runInContext(ServerImpl.java:817) [grpc-core-1.27.2.jar:1.27.2]
	at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) [grpc-core-1.27.2.jar:1.27.2]
	at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123) [grpc-core-1.27.2.jar:1.27.2]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_282]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_282]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_282]

请问fate-manager中如何将站点连接到已经用kubeFATE部署好的fate1.5 cluster上？

请问fate-manager中如何将站点连接到已经用kubeFATE部署好的fate cluster上？

cloud-manager-1.1.1 enhancement

1.add polling field for exchange function

cloud-manager-1.1.0 cancel the check of ip

cancel the check of ip of exchange

update cm to 1.3.0

support new feature for cm 1.3.0

update cloud-manager

add new functions about instituion activate
update signature

./fate_manager 运行报错

[2021-01-25 21:09:59] [info] replacing callback gorm:update_time_stamp from D:/webank/Federated/FATE-Cloud/fate-manager/src/models/models.go:53

[2021-01-25 21:09:59] [info] replacing callback gorm:update_time_stamp from D:/webank/Federated/FATE-Cloud/fate-manager/src/models/models.go:54

[2021-01-25 21:09:59] [info] replacing callback gorm:delete from D:/webank/Federated/FATE-Cloud/fate-manager/src/models/models.go:55
/data/logs/fate-cloud/fate-manager/2021-01-25/ fate-manager.debug.log
/data/logs/fate-cloud/fate-manager/2021-01-25/ fate-manager.info.log
/data/logs/fate-cloud/fate-manager/2021-01-25/ fate-manager.warn.log
/data/logs/fate-cloud/fate-manager/2021-01-25/ fate-manager.error.log
/data/logs/fate-cloud/fate-manager/2021-01-25/ fate-manager.fatal.log

(D:/webank/Federated/FATE-Cloud/fate-manager/src/models/accountInfo.go:77)
[2021-01-25 21:09:59] [0.93ms] SELECT * FROM t_fate_account_info WHERE (status = 1) AND (role = 1) AND (cloud_user_id is not null)
[0 rows affected or returned ]
panic: open ./fate-manager/static//: no such file or directory

goroutine 1 [running]:
html/template.Must(...)
D:/Go/src/html/template/template.go:372
github.com/gin-gonic/gin.(*Engine).LoadHTMLFiles(0xb4f4840, 0xbb0eed0, 0x1, 0x1)
D:/webankGo/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:204 +0x281
fate.manager/routers.InitRouter(0x0)
D:/webank/Federated/FATE-Cloud/fate-manager/src/routers/router.go:133 +0x1da0
main.main()
D:/webank/Federated/FATE-Cloud/fate-manager/src/fate_manager.go:48 +0x71

Fate-exchange_deployment_guide_zh.md could not find the file

When building the exchange, I found that the file Fate-exchange_deployment_guide_zh.md does not exist

fatemanager激活站点失败: failed to add routing table

fatemanager激活站点失败: failed to add routing table

---

[INFO] [2021-12-13 21:34:19,102] [47059:140168874948352] - db_operator.py[line:134]: update filters: [<peewee.Expression object at 0x7f7ba81a0160>, <peewee.Expression object at 0x7f7ba81a02b0>]
[INFO] [2021-12-13 21:34:21,909] [47059:140168874948352] - site_service.py[line:27]: site registrationLink decode info:http://10.45.47.142:9000--9999--kevhhnJb
[INFO] [2021-12-13 21:34:21,910] [47059:140168874948352] - site_service.py[line:37]: start save exchange info to rollsite
[INFO] [2021-12-13 21:34:21,910] [47059:140168874948352] - site_service.py[line:748]: write rollsite info:ip 10.10.178.147, port 9370,key fate, route: {'default': {'default': [{'port': 9370, 'ip': '10.45.47.142', 'is_secure': False, 'is_polling': False}]}}
[INFO] [2021-12-13 21:34:21,910] [47059:140168874948352] - roll_site.py[line:15]: get route table
[INFO] [2021-12-13 21:34:23,942] [47059:140168843478784] - apply.py[line:72]: start request cloud AuthorityApplied
[INFO] [2021-12-13 21:34:23,947] [47059:140168843478784] - request_cloud_utils.py[line:141]: start request uri:http://10.45.47.142:9000/cloud-manager/api/authority/applied, body:{'institutions': 'goods1'}, head:{'VERSION': 'v2', 'TIMESTAMP': '1639402463943', 'FATE_MANAGER_USER_ID': 'ec5e40d4275b4dbcaea07164500bd8d6', 'NONCE': '6293cb4e5c1911ecb3d7005056affcc1', 'FATE_MANAGER_APP_KEY': '1J4sxHiX', 'SIGNATURE': 'getpLsaYhKopG0nMyC2K7zzYSek='}
[INFO] [2021-12-13 21:34:24,073] [47059:140168843478784] - request_cloud_utils.py[line:159]: response:{"code":0,"msg":"Success!","data":{"scenarioType":"3","guestList":[],"hostList":[],"all":null,"total":0}}
[INFO] [2021-12-13 21:34:24,074] [47059:140168843478784] - apply.py[line:80]: request cloud success, return {'scenarioType': '3', 'guestList': [], 'hostList': [], 'all': None, 'total': 0}
[INFO] [2021-12-13 21:34:24,083] [47059:140168843478784] - db_operator.py[line:133]: update fields: {<ListField: AccountInfo.allow_instituions>: {'scenarioType': '3', 'guestList': [], 'hostList': [], 'all': None, 'total': 0}, <IntegerField: AccountInfo.role>: 1, <SmallIntegerField: AccountInfo.status>: 1, <BigIntegerField: AccountInfo.update_time>: 1639402464083, <DateTimeField: AccountInfo.update_date>: '2021-12-13 21:34:24'}
[INFO] [2021-12-13 21:34:24,084] [47059:140168843478784] - db_operator.py[line:134]: update filters: [<peewee.Expression object at 0x7f7ba8195e10>, <peewee.Expression object at 0x7f7ba81955c0>]
[INFO] [2021-12-13 21:34:24,914] [47059:140168874948352] - site_service.py[line:753]: write rollsite data failed
[ERROR] [2021-12-13 21:34:24,916] [47059:140168874948352] - api_utils.py[line:18]: (30001, 'failed to add routing table')
Traceback (most recent call last):
File "/fatemanager/projects/FATE-Cloud/fate_manager/service/site_service.py", line 750, in update_all_rollsite_info
write_site_route(rollsite_ip, rollsite_port, ROLL_SITE_KEY, site_route, str(party_id))
File "/fatemanager/projects/FATE-Cloud/fate_manager/controller/roll_site.py", line 17, in write_site_route
operator="get_route_table", overall_timeout=overall_timeout)
File "/fatemanager/projects/FATE-Cloud/fate_manager/controller/roll_site.py", line 29, in roll_site_actuator
_return, _call = stub.unaryCall.with_call(_packet, timeout=(overall_timeout/1000))
File "/fatemanager/myenv/venv/lib/python3.6/site-packages/grpc/_channel.py", line 957, in with_call
return _end_unary_response_blocking(state, call, True, None)
File "/fatemanager/myenv/venv/lib/python3.6/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.DEADLINE_EXCEEDED
details = "Deadline Exceeded"
debug_error_string = "{"created":"@1639402464.913262196","description":"Deadline Exceeded","file":"src/core/ext/filters/deadline/deadline_filter.cc","file_line":81,"grpc_status":4}"

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/fatemanager/myenv/venv/lib/python3.6/site-packages/flask/app.py", line 2292, in wsgi_app
response = self.full_dispatch_request()
File "/fatemanager/myenv/venv/lib/python3.6/site-packages/flask/app.py", line 1815, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/fatemanager/myenv/venv/lib/python3.6/site-packages/flask_cors/extension.py", line 165, in wrapped_function
return cors_after_request(app.make_response(f(*args, **kwargs)))
File "/fatemanager/myenv/venv/lib/python3.6/site-packages/flask/app.py", line 1718, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/fatemanager/myenv/venv/lib/python3.6/site-packages/flask/_compat.py", line 35, in reraise
raise value
File "/fatemanager/myenv/venv/lib/python3.6/site-packages/flask/app.py", line 1813, in full_dispatch_request
rv = self.dispatch_request()
File "/fatemanager/myenv/venv/lib/python3.6/site-packages/flask/app.py", line 1799, in dispatch_request
return self.view_functionsrule.endpoint
File "/fatemanager/projects/FATE-Cloud/fate_manager/apps/site_app.py", line 32, in register_site
data = site_service.register_fate_site(request_data)
File "/fatemanager/projects/FATE-Cloud/fate_manager/service/site_service.py", line 40, in register_fate_site
is_polling=request_data.get("pollingStatus"))
File "/fatemanager/projects/FATE-Cloud/fate_manager/service/site_service.py", line 755, in update_all_rollsite_info
raise Exception(RollsiteInfoStatusCode.Write_RollSite_Fail,f"failed to add routing table")
Exception: (30001, 'failed to add routing table')

fate-cloud v1.3

fate manager :

1. rebuild code by python;
2. add job monitor module

The username or password error!

when i try to add user in cloud-manager, it doesn't ask me for a password, but it prompts me that the username or password error, what's going on?

add secure field for cloud-manager 1.1.1

1. allow update secure field in rollsite of exchange

Missing fate-manager-1.1.0.tar.gz

部署fate-manager, 缺失https://github.com/FederatedAI/FATE-Cloud/releases/download/v1.1.0/fate-manager-1.1.0.tar.gz安装包，是否能更新一下，谢谢
或者能给一下相关的编译说明，谢谢

bugs fix for the display of site pages

1.fix the bugs of the site page (front end)
2.fix the bugs of the institutions page(front end)
3.update the authority interface for fate manager
4.fix the bugs of authority page (front end)

cloud-manager安装报错

将所有maven包下载到本地仓库后执行安装报错

app@exchange:/data/projects/FATE-Cloud/cloud-manager/deploy/scripts$ sh deploy.sh all install

[INFO] Installing cloud-manager start-------
/data/projects/FATE-Cloud/cloud-manager/deploy/scripts/cloud-manager
/data/projects/FATE-Cloud/cloud-manager/deploy/scripts/packages
/data/projects/FATE-Cloud
start packaging
start execute mvn build
[INFO] Scanning for projects...
[INFO] Artifact org.apache.maven:maven-artifact:jar:3.5.3 is present in the local repository, but cached from a remote repository ID that is unavailable in current build context, verifying that is downloadable from [central (https://repo.maven.apache.org/maven2, default, releases), sonatype-nexus-snapshots (https://oss.sonatype.org/content/repositories/snapshots, default, snapshots), apache.snapshots (https://repository.apache.org/snapshots, default, snapshots)]
Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-artifact/3.5.3/maven-artifact-3.5.3.jar
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Unresolveable build extension: Plugin kr.motd.maven:os-maven-plugin:1.6.1 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven:maven-artifact:jar:3.5.3 (present, but unavailable): Could not transfer artifact org.apache.maven:maven-artifact:jar:3.5.3 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org: Temporary failure in name resolution @
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project com.webank.ai:cloud-manager:1.4.1 (/data/projects/FATE-Cloud/cloud-manager/pom.xml) has 1 error
[ERROR] Unresolveable build extension: Plugin kr.motd.maven:os-maven-plugin:1.6.1 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven:maven-artifact:jar:3.5.3 (present, but unavailable): Could not transfer artifact org.apache.maven:maven-artifact:jar:3.5.3 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org: Temporary failure in name resolution: Unknown host repo.maven.apache.org: Temporary failure in name resolution -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/PluginManagerException

fate-manager部署问题

下载 fate_manager_1.4.1_release-1.0.0.tar.gz 包报错404
wget https://webank-ai-1251170195.cos.ap-guangzhou.myqcloud.com/fate-cloud/1.4.1/fate_manager_1.4.1_release-1.0.0.tar.gz

找不到 配置文件 fate_manager-install/common-deploy/conf/setup.conf