-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: archive v2.2.0 and add v2.3.0 roadmap and v2.4.0 roadmap (#205)
Signed-off-by: Gaius <[email protected]>
- Loading branch information
Showing
180 changed files
with
10,934 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
--- | ||
id: roadmap-v2.3 | ||
title: v2.3 | ||
slug: /roadmap-v2.3/ | ||
--- | ||
|
||
Manager: | ||
|
||
- Configure scheduling weights. | ||
- Support scopes for Personal Access Tokens (PATs). | ||
- Regularly clean up inactive schedulers and seed peers. | ||
- Display more Peer information in the console, such as CPU and memory usage. | ||
- Display persistent cache information of peers in the console. | ||
- Add management of sync peers in the console. | ||
|
||
Scheduler: | ||
|
||
- Optimize the scheduling algorithm to improve bandwidth utilization in the P2P network. | ||
|
||
Client: | ||
|
||
- Support RDMA/QUIC for faster network transmission in the P2P network, enhancing the loading of | ||
AI inference models into memory. | ||
- Define a codable protocol for data transmission, providing faster encoding/decoding. | ||
- Support persistent cache, allowing access within the P2P cluster without uploading to other storage, | ||
facilitating faster read/write of AI models and datasets. | ||
- Allow peers to get the QoS of parents and select the optimal parents for downloading. | ||
- Preheat files in the memory cache to improve download speed. | ||
|
||
Others: | ||
|
||
- Add more performance tests in the dfbench command. | ||
- Add more E2E tests and unit tests. | ||
|
||
Documentation: | ||
|
||
- Restructure the documentation to make it easier for users to navigate. | ||
- Enhance the landing page UI. | ||
|
||
AI Infrastructure: | ||
|
||
- Optimize large file distribution within the infrastructure. | ||
- Optimize handling of a large number of small I/Os for Nydus. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
--- | ||
id: roadmap-v2.4 | ||
title: v2.4 | ||
slug: /roadmap-v2.4/ | ||
--- | ||
|
||
Manager | ||
|
||
- Optimize memory and CPU usage. | ||
- Add more features to the console. | ||
- Provide more open APIs for the console. | ||
|
||
Scheduler | ||
|
||
- Optimize the scheduling algorithm to improve bandwidth utilization in the P2P network. | ||
|
||
Client | ||
|
||
- Support P2P for RDMA-based memory storage. | ||
- Add distributed addressing, allowing deployment without relying on the manager and scheduler. | ||
- Optimize file transfer speed in the P2P network. | ||
|
||
Others | ||
|
||
- Add more performance tests in the `dfbench` command. | ||
- Add more E2E tests and unit tests. | ||
|
||
Documentation | ||
|
||
- Restructure the documentation to make it easier for users to navigate. | ||
- Enhance the landing page UI. | ||
|
||
AI Infrastructure | ||
|
||
- Optimize large file distribution within the infrastructure. | ||
- Optimize handling of a large number of small I/Os for Nydus. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
--- | ||
id: faq | ||
title: FAQ | ||
slug: /faq/ | ||
--- | ||
|
||
## Change log level {#change-log-level} | ||
|
||
Send `SIGUSR1` signal to dragonfly process to change log level | ||
|
||
```shell | ||
kill -s SIGUSR1 <pid of dfdaemon, scheduler or manager> | ||
``` | ||
|
||
stdout: | ||
|
||
```text | ||
change log level to debug | ||
change log level to fatal | ||
change log level to panic | ||
change log level to dpanic | ||
change log level to error | ||
change log level to warn | ||
change log level to info | ||
``` | ||
|
||
> The change log level event will print in stdout and `core.log` file, but if the level is greater than `info`, stdout only. | ||
## 500 Internal Server Error {#500-internal-server-error} | ||
|
||
**1.** Check error logs in /var/log/dragonfly/dfdaemon/ | ||
|
||
**2.** Check source connectivity(dns error or certificate error) | ||
|
||
Example: | ||
|
||
```shell | ||
curl https://example.harbor.local/ | ||
``` | ||
|
||
When curl says error, please check the details in output. |
65 changes: 65 additions & 0 deletions
65
versioned_docs/version-v2.2.0/advanced-guides/personal-access-tokens.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,65 @@ | ||
--- | ||
id: personal-access-tokens | ||
title: Personal Access Tokens | ||
slug: /advanced-guides/personal-access-tokens/ | ||
--- | ||
|
||
You can use a personal access token to call open API. | ||
|
||
In this article, you will learn how to create, use, modify and delete personal access token. | ||
|
||
## About personal access tokens | ||
|
||
Only users with `root` role can list all personal access tokens. | ||
|
||
![tokens](../resource/advanced-guides/personal-access-tokens/tokens.png) | ||
|
||
## Create personal access token | ||
|
||
Click the `ADD PERSONAL ACCESS TOKENS` button to create personal access token. | ||
|
||
**Name**: Set your token a descriptive name. | ||
|
||
**Description**: Set a description. | ||
|
||
**Expiration**: Set your token an expiration. | ||
|
||
**Scopes**: Select the access permissions for the token. | ||
|
||
![create-token](../resource/advanced-guides/personal-access-tokens/create-token.png) | ||
|
||
Click `SAVE` and copy the token and store it. For your security, it doesn't display again. | ||
|
||
![copy-token](../resource/advanced-guides/personal-access-tokens/copy-token.png) | ||
|
||
## Update personal access token | ||
|
||
Click `personal access token name` and update your personal access token. | ||
|
||
![update-token](../resource/advanced-guides/personal-access-tokens/update-token.png) | ||
|
||
## Delete personal access token | ||
|
||
Click `DELETE` and delete your personal access token. | ||
|
||
![delete-token](../resource/advanced-guides/personal-access-tokens/delete-token.png) | ||
|
||
## Use personal access token | ||
|
||
**Step 1:** Open Postman, and import [postman_collection.json](https://github.com/gaius-qi/dragonfly-docs/blob/main/manager/postman/Dragonfly.postman_collection.json). | ||
|
||
**Step 2:** Click **Open API** in the sidebar. | ||
|
||
**Step 3:** Click **Authorization** and select **Bearer Token**, paste `personal access token` in `Token`. | ||
|
||
![add-token-to-open-api](../resource/advanced-guides/personal-access-tokens/add-token-to-open-api.png) | ||
|
||
**Step 4:** Click **Headers**, check whether `Authorization` is added to Headers. | ||
|
||
![verify-headers](../resource/advanced-guides/personal-access-tokens/verify-headers.png) | ||
|
||
**Step 5:** Click **Send** button to initiate a request. | ||
|
||
**Step 6:** If successful, it means that the call to the open API is completed through the personal access token. | ||
|
||
![verify-open-api](../resource/advanced-guides/personal-access-tokens/verify-request.png) |
Oops, something went wrong.