fate_serving: get serviceRoleName from configuration

pangzx1 · Sep 3, 2019 · eadac23 · eadac23
1 parent cdcc908
commit eadac23
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 2 deletions.
diff --git a/cluster-deploy/example-dir-tree/serving-server/conf/serving-server.properties b/cluster-deploy/example-dir-tree/serving-server/conf/serving-server.properties
@@ -17,6 +17,7 @@ coordinator=webank
 ip=127.0.0.1
 port=8000
 workMode=0
+serviceRoleName=serving
 inferenceWorkerThreadNum=10
 #storage
 # maybe python/data/

diff --git a/...ing/federatedml/src/main/java/com/webank/ai/fate/serving/federatedml/model/BaseModel.java b/...ing/federatedml/src/main/java/com/webank/ai/fate/serving/federatedml/model/BaseModel.java
@@ -101,12 +101,12 @@ protected ReturnResult getFederatedPredictFromRemote(Context  context,FederatedP
 
             metaDataBuilder.setSrc(
                     topicBuilder.setPartyId(String.valueOf(srcParty.getPartyId())).
-                            setRole("serving")
+                            setRole(Configuration.getProperty("serviceRoleName", "serving"))
                             .setName("partnerPartyName")
                             .build());
             metaDataBuilder.setDst(
                     topicBuilder.setPartyId(String.valueOf(dstParty.getPartyId()))
-                            .setRole("serving")
+                            .setRole(Configuration.getProperty("serviceRoleName", "serving"))
                             .setName("partyName")
                             .build());
             metaDataBuilder.setCommand(Proxy.Command.newBuilder().setName("federatedInference").build());

diff --git a/fate-serving/serving-server/src/main/resources/serving-server.properties b/fate-serving/serving-server/src/main/resources/serving-server.properties
@@ -17,6 +17,7 @@ coordinator=webank
 ip=127.0.0.1
 port=8000
 workMode=0
+serviceRoleName=serving
 inferenceWorkerThreadNum=10
 #storage
 # maybe python/data/