Add ai subnet orch docs #2982
Merged
Add ai subnet orch docs #2982
Conversation
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
|
@yondonfu, to ensure the Docker container operates successfully, please rebase your branch onto the master branch. Once completed, I'll rebase my branch onto yours again. I've marked this as a draft as I still need to add additional information for putting it on-chain, such as |
5 tasks
56d4439 to
101b3bb
Compare
This is done. |
101b3bb to
2654ed7
Compare
This commit adds detailed instructions for setting up an orchestrator on the AI Subnet.
This commit adds detailed instructions for setting up an broadcaster on the AI Subnet.
2654ed7 to
b3fdf31
Compare
|
Now that the CI build the container I will update the documentation. I will also try to include a section that explains how to use the pre-build binaries 👍🏻. |
This commit refines the AI Subnet documentation and introduces instructions for utilizing the prebuilt AI Subnet binaries.
This commit improves the AI subnet documentation by adding some missing steps and improved unclear steps. Special thanks to @Pon-node for walking through the documentation as I could code along and improve it. Co-authored-by: Pon <94224680+Pon-node@users.noreply.github.com>
This commit fixes a broken huggingface documentation link. Co-authored-by: papabear99 <89408276+papabear99@users.noreply.github.com>
This commit fixes the broken `dl_checkpoints.sh` run command found in the documentation. Co-authored-by: papabear99 <89408276+papabear99@users.noreply.github.com>
This commit refines the AI subnet documentation to address ambiguities and inaccuracies identified during our initial pilot with **pre-alpha** participants. The improvements aim to provide clearer instructions and correct information for a smoother user experience.
This commit explaines the parameters found in the `aiModels.json` file.
…chestrator This commit introduces comprehensive instructions for setting up the AI Subnet Orchestrator for on-chain operation. It includes both binary and Docker setup methods.
This commit restructures the AI on-chain instructions to make them easier to follow.
This commit applies some small syntax changes to the ai documentation to improve readability.
docs(ai): improve ai docs syntax
This commit adds some documentation on how people can **opt-in** to send us data about their AI Subnet Orchestrator.
This update modifies the volume mount for the promptail docker container to remove the ai_subnet_promtail.yml file, addressing issues reported by several users with the previous promtail docker configuration.
This commit ensures that people use named docker containers. This will help us monitor their metrics when they decide to share them.
a4ce20c to
5e26f41
Compare
This commit improves the description of the `warm` configuration value and add the `ticketEV` flag to the Livepeer command line arguments to prevent the `too many values` error from occuring. This error is thrown because the current software does not allow sending more than 150 tickets in one batch.
This commit ensures it is clear that the redeemer is not recommended when setting up a AI subnet orchestrator. It also explains that the `pricePerUnit` flag is not needed for the AI subnet orchestrator.
10ec559 to
aa706dc
Compare
This commit ensures that users know which output to expect when they run the commands in the documentation:
JJassonn69
reviewed
Apr 6, 2024
| 1. Create a new Ethereum account for your _Mainnet AI Subnet_ Orchestrator. It is recommended that you use a separate account from your _Mainnet Transcoding Network_ Orchestrator for security reasons. | ||
| 2. Fund the Ethereum account with enough ETH to cover the gas costs of redeeming the AI tickets **on-chain**. | ||
| 3. Open port `8936` on your machine and set up port forwarding on your router to make the _Mainnet AI Subnet_ Orchestrator accessible from the internet. | ||
|
|
There was a problem hiding this comment.
Orchestrator running in WSL: If you cannot access your orchestrator in port 8936 even after forwarding port in router and setting up firewall, use the Netsh interface portproxy guide from Accessing a WSL 2 distribution from your local area network (LAN).
There was a problem hiding this comment.
@JJassonn69 thanks for the update. I will implement your changes in a subsequent pull request.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this pull request do? Explain your changes. (required)
This commit adds detailed instructions for setting up an orchestrator on the AI Subnet.
Specific updates (required)
ai-subnet.mdmarkdown file to thedocsfolder.ai-videobranch onto the master branch to include Add ai subnet orch docs #2982 and Update CUDA build version from 11.7.1 to 12.0.0 #2978 so that the docker image uses CUDA 12.How did you test each of these updates (required)
Does this pull request close any open issues?
Checklist:
makeruns successfully./test.shpass