环境字典 env 运行环境即设置 环境即状态共享 其他考虑 环境变量完整列表 Execution model Execution strategy Defining tasks Defining host lists Intelligently executing tasks with execute Failure handling Connections Password management contrib.console import confirm 改好之后，我们重新部署： $ fab deploy No hosts found. Please specify (single) host string for connection: my_server [my_server] run: git pull [my_server] out: Already up-to-date. [my_server] fabfile 中指定任何连接信息，所以 Fabric 依旧不知道该在哪里运 行这些远程命令。遇到这种情况时，Fabric 会在运行时提示我们。连接的定义 使用 SSH 风格的“主机串”（例如： user@host:port ），默认使用你的本地用户 名——所以在这个例子中，我们只需要指定主机名 my_server 。 与远程交互 如果你已经得到了代码，说明 git pull 执行非常顺利——但如果这是第一次

环境字典 env 运行环境即设置 环境即状态共享 其他考虑 环境变量完整列表 Execution model Execution strategy Defining tasks Defining host lists Intelligently executing tasks with execute Failure handling Connections Password management contrib.console import confirm 改好之后，我们重新部署： $ fab deploy No hosts found. Please specify (single) host string for connection: my_server [my_server] run: git pull [my_server] out: Already up-to-date. [my_server] fabfile 中指定任何连接信息，所以 Fabric 依旧不知道该在哪里运 行这些远程命令。遇到这种情况时，Fabric 会在运行时提示我们。连接的定义 使用 SSH 风格的“主机串”（例如： user@host:port ），默认使用你的本地用户 名——所以在这个例子中，我们只需要指定主机名 my_server 。 与远程交互 如果你已经得到了代码，说明 git pull 执行非常顺利——但如果这是第一次

keyPath参数为节点的身份，不同keyPath即对应了不同的身份。 3. 查看服务状态 使用 xdb-cli 客户端执行如下命令，请求数据持有节点查看存储节点 的在线状态： $ ./xdb-cli nodes list --host http://127.0.0.1:8121 3. 部署Distributed AI 一般多方安全计算至少由两个任务执行节点，所以这里部署两个任务执行 节点。 每一个 任务执行节点 都有一对公私钥，用来标识节点的账户，公 储，则需提前生成数据持有节点客户端./ukeys并授权，同时创建预测结果存储的命 名空间 type = 'Local' [executor.storage.XuperDB] host = "http://127.0.0.1:8121" keyPath = "./ukeys" namespace = "mpc" [executor.storage 储，则需提前生成数据持有节点客户端./ukeys并授权，同时创建预测结果存储的命 名空间 type = 'Local' [executor.storage.XuperDB] host = "http://127.0.0.1:8121" keyPath = "./ukeys" namespace = "mpc" [executor.storage

keyPath 即对应了不同的身份。 3. 查看服务状态 使用 xdb-cli 客户端执行如下命令，请求数据持有节点查看存储节点的在线状态： $ ./xdb-cli nodes list --host http://127.0.0.1:8121 3. 部署 Distributed AI 一般多方安全计算至少由两个任务执行节点，所以这里部署两个任务执行节点。每一个任务执行节点 都有一对公私 type = 'Local' [executor.storage.XuperDB] (下页继续) 5.1. 源码编译和安装 15 PaddleDTX Documentation (续上页) host = "http://127.0.0.1:8121" keyPath = "./ukeys" namespace = "mpc" [executor.storage.Local] localPredictStoragePath 客 户 端. �→/ukeys并 授 权 ， 同 时 创 建 预 测 结 果 存 储 的 命 名 空 间 type = 'Local' [executor.storage.XuperDB] host = "http://127.0.0.1:8121" keyPath = "./ukeys" namespace = "mpc" [executor.storage.Local] localPredictStoragePath

keyPath参数为节点的身份，不同keyPath即对应了不同的身份。 3. 查看服务状态 使用 xdb-cli 客户端执行如下命令，请求数据持有节点查看存储节点 的在线状态： $ ./xdb-cli nodes list --host http://127.0.0.1:8121 3. 部署Distributed AI 一般多方安全计算至少由两个任务执行节点，所以这里部署两个任务执行 节点。 每一个 任务执行节点 都有一对公私钥，用来标识节点的账户，公 储，则需提前生成数据持有节点客户端./ukeys并授权，同时创建预测结果存储的命 名空间 type = 'Local' [executor.storage.XuperDB] host = "http://127.0.0.1:8121" keyPath = "./ukeys" namespace = "mpc" [executor.storage 储，则需提前生成数据持有节点客户端./ukeys并授权，同时创建预测结果存储的命 名空间 type = 'Local' [executor.storage.XuperDB] host = "http://127.0.0.1:8121" keyPath = "./ukeys" namespace = "mpc" [executor.storage

keyPath 即对应了不同的身份。 3. 查看服务状态 使用 xdb-cli 客户端执行如下命令，请求数据持有节点查看存储节点的在线状态： $ ./xdb-cli nodes list --host http://127.0.0.1:8121 3. 部署 Distributed AI 一般多方安全计算至少由两个任务执行节点，所以这里部署两个任务执行节点。每一个任务执行节点 都有一对公私 (下页继续) 5.1. 源码编译和安装 17 PaddleDTX Documentation (续上页) type = 'Local' [executor.storage.XuperDB] host = "http://127.0.0.1:8121" keyPath = "./ukeys" namespace = "mpc" [executor.storage.Local] localPredictStoragePath 客 户 端. �→/ukeys并 授 权 ， 同 时 创 建 预 测 结 果 存 储 的 命 名 空 间 type = 'Local' [executor.storage.XuperDB] host = "http://127.0.0.1:8121" keyPath = "./ukeys" namespace = "mpc" [executor.storage.Local] localPredictStoragePath

of proof. Smart Contracts To support the consistent update of information — and to enable a whole host of ledger functions (transacting, query- ing, etc) — a blockchain network uses smart contracts to into roles in a Fabric network. • Peers (conceptual documentation) Peers — owned by organizations — host the ledger and smart contracts and make up the physical structure of a Fabric network. • Building contract trans- action responses to digitally sign transactions. Subsequently the network nodes who host copies of the ledger verify that transaction signatures are valid before accepting transactions onto

of proof. Smart Contracts To support the consistent update of information — and to enable a whole host of ledger functions (transacting, query- ing, etc) — a blockchain network uses smart contracts to into roles in a Fabric network. • Peers (conceptual documentation) Peers — owned by organizations — host the ledger and smart contracts and make up the physical structure of a Fabric network. • Building contract trans- action responses to digitally sign transactions. Subsequently the network nodes who host copies of the ledger verify that transaction signatures are valid before accepting transactions onto

of proof. Smart Contracts To support the consistent update of information — and to enable a whole host of ledger functions (transacting, query- ing, etc) — a blockchain network uses smart contracts to into roles in a Fabric network. • Peers (conceptual documentation) Peers — owned by organizations — host the ledger and smart contracts and make up the physical structure of a Fabric network. • Building contract trans- action responses to digitally sign transactions. Subsequently the network nodes who host copies of the ledger verify that transaction signatures are valid before accepting transactions onto

of proof. Smart Contracts To support the consistent update of information — and to enable a whole host of ledger functions (transacting, query- ing, etc) — a blockchain network uses smart contracts to into roles in a Fabric network. • Peers (conceptual documentation) Peers — owned by organizations — host the ledger and smart contracts and make up the physical structure of a Fabric network. • Building contract trans- action responses to digitally sign transactions. Subsequently the network nodes who host copies of the ledger verify that transaction signatures are valid before accepting transactions onto