System Configuration¶
FATE Flow uses YAML to define system configurations, and the configuration file is located at: conf/service_conf.yaml
. The specific configuration contents and their meanings are as follows:
Configuration Item | Description | Values |
---|---|---|
party_id | Local site ID | For example, "9999", "10000" |
log_level | Log level | DEBUG:10, INFO:20, DEBUG:30, ERROR: 40 |
use_registry | Whether to use a registry center; currently, only ZooKeeper mode is supported, and it requires correct ZooKeeper configuration. Note: If using high availability mode, ensure this configuration is set to true. | true/false |
encrypt | Encryption module | See Encryption Module |
fateflow | Configuration for the FATE Flow service, including ports, command channel service, and proxy | See FateFlow Configuration |
database | Configuration information for the database service | See Database Configuration |
default_engines | System's engine services, including computing, storage, and communication engines | See Engine Configuration |
default_provider | Component source information, including provider name, component version, and execution mode | See Default Registered Algorithm Configuration |
federation | Communication service pool | See Communication Engine Pool |
computing | Computing service pool | See Computing Engine Pool |
storage | Storage service pool | See Storage Engine Pool |
hook_module | Hook configuration, currently supports client authentication, site authentication, and authorization hooks | See Hook Module Configuration |
authentication | Authentication and authorization switches | See Authentication Switch |
model_store | Model storage configuration | See Model Storage |
zookeeper | ZooKeeper service configuration | See ZooKeeper Configuration |
Encryption Module¶
key_0:
module: fate_flow.hub.encrypt.password_encrypt#pwdecrypt
private_path: private_key.pem
fate_flow/conf/
.
FateFlow Configuration¶
host: 127.0.0.1
http_port: 9380
grpc_port: 9360
proxy_name: osx
nginx:
host:
http_port:
grpc_port:
Database Configuration¶
engine: sqlite
decrypt_key:
mysql:
name: fate_flow
user: fate
passwd: fate
host: 127.0.0.1
port: 3306
max_connections: 100
stale_timeout: 30
sqlite:
path:
fate_flow/fate_flow_sqlite.db
.
Engine Configuration¶
default_engines:
computing: standalone
federation: standalone
storage: standalone
- computing: Computing engine, supports "standalone", "eggroll", "spark".
- federation: Communication engine, supports "standalone", "osx", "rabbitmq", "pulsar".
- storage: Storage engine, supports "standalone," "eggroll," "hdfs."
Default Registered Algorithm Configuration¶
- name: Algorithm name.
- version: Algorithm version. If not configured, it uses the configuration in
fateflow.env
. - device: Algorithm launch mode, local/docker/k8s, etc.
Communication Engine Pool¶
OSx¶
host: 127.0.0.1
port: 9370
mode: stream
Computing Engine Pool¶
Standalone¶
cores: 32
Eggroll¶
eggroll:
cores: 32
nodes: 1
host: 127.0.0.1
port: 4670
Spark¶
spark:
home:
cores: 32
Storage Engine Pool¶
hdfs:
name_node: hdfs://fate-cluster
Hook Module Configuration¶
hook_module:
client_authentication: fate_flow.hook.flow.client_authentication
site_authentication: fate_flow.hook.flow.site_authentication
permission: fate_flow.hook.flow.permission
Authentication Switch¶
authentication:
client: false
site: false
permission: false
Model Storage¶
model_store:
engine: file
decrypt_key:
file:
path:
mysql:
name: fate_flow
user: fate
passwd: fate
host: 127.0.0.1
port: 3306
max_connections: 100
stale_timeout: 30
tencent_cos:
Region:
SecretId:
SecretKey:
Bucket:
fate_flow/model
.
- mysql: MySQL service configuration; if using password encryption functionality, you need to set the "passwd" in this configuration to ciphertext and configure the key path in Encryption Module.
- tencent_cos: Tencent Cloud key configuration.
ZooKeeper Configuration¶
zookeeper:
hosts:
- 127.0.0.1:2181
use_acl: true
user: fate
password: fate