Post-deployment verification and management-Ant Privacy-Preserving Computation Platform-阿里云帮助中心

This topic describes how to verify a node after deployment and provides information about ongoing node maintenance.

Verify the results

Log on to the Ant Privacy-Preserving Computation Platform.
In the navigation pane on the left, choose My Subscriptions > Privacy-Preserving Computation Nodes.
On the Privacy-Preserving Computation Nodes page, confirm that the node status is Active. This status indicates that the node is deployed.

Note
If the node status is Inactive, see Install and deploy a node to configure the node network.

Node O&M

This section describes common commands for node maintenance, the data upload path, log descriptions, temporary file cleanup rules, and how to enable ShangMi (SM) cryptographic algorithms. SM algorithms are commercial cryptographic algorithms certified by the China State Cryptography Administration.

Common commands

The following are common commands for node maintenance:

Start or update a service
```
docker-compose up -d
```

Stop a service
```
docker-compose down
```

Restart a service
```
docker-compose restart
```

View containers
```
docker ps
```

View the logs of a specific container
```
docker logs -f ${CONTAINER}
```
Note
${CONTAINER} is the container name.

Data upload path

You can upload the project samples to the ${WORKING_DIR} path. This path is defined in the .env file and represents the current directory.

${WORKING_DIR}/agent/data/dataset

Log descriptions

The following are descriptions of the relevant logs.

nueva
├── agent
│   ├── data                 --Data files
│   ├── images               --Application images
│   ├── lib
│   ├── logs                 --Application process log output
│   └── stdout               --Application process standard output
└── gateway
    ├── conf
    │   └── server.key       --Organization private key
    └── logs
        ├── access-in.log     --Ingress log
        ├── error.log         --Error log
        ├── informer.log     
        ├── internal.log      --Internal/Egress log
        ├── prometheus.log
        └── zipkin.log

Temporary file cleanup rules

The following table describes the cleanup rules for temporary files.

Type	Directory	Cleanup cycle	Notes
Agent logs	In container: `/home/admin/logs/agent` Outside container: `~/nueva/agent/logs`	Files are scrolled every 512 MB. Each file is retained for a maximum of 15 days.	-
Gateway logs	In container: `/home/admin/gateway/logs` Outside container: `~/nueva/gateway/logs`	Logs are scrolled daily. Logs older than two days are compressed using Gzip. The logs from the last 30 days are retained.	-
App logs	In container: `/home/admin/logs/agent` Outside container: `~/nueva/agent/logs`	The app is responsible for deleting itself during runtime. After the app exits, log files that meet one of the following conditions are deleted. The check is performed hourly. The file has existed for more than 30 days. The disk usage exceeds 85%. In this case, the logs of exited apps are deleted until the disk usage is less than 85%.	The file permissions for all app logs are set to allow deletion by the others user group. You can run the `rm` command on the host to delete files in advance. If you encounter a permission issue, contact technical support.
App stdout and App stderr redirection files	In container: `/home/admin/agent/stdout` Outside container: `~/nueva/agent/stdout`	During app runtime: Files are scrolled every 512 MB. Each file is retained for a maximum of 15 days. A maximum of 10 files are retained. When the app exits: All files are deleted immediately.	-
App input files, output files, training data, and more	In container: `/home/admin/agent/data` Outside container: `~/nueva/agent/data`	The framework and app are not responsible for deletion. You must delete these files manually.	-
App core dump files	In container: The path is not fixed and is determined by the host kernel parameters. Outside container: None	Determined by the host configuration: If the core dump is saved to the current path, such as `./core_dump.file`, the `core` file is deleted when the pod is deleted. If the core dump is saved to an absolute path, such as `/root/core_dump.file`, the framework cannot automatically clean it up. You must delete the file manually.	The path for core dump files is `/proc/sys/kernel/core_pattern`. Modify this configuration on the host.

Set SM algorithms

In the .env file, you can manually enable or disable SM algorithms by modifying the TLS_PROTOCOLS configuration.