Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Container images release #109

Closed
2 of 3 tasks
Tracked by #33 ...
mudler opened this issue Jun 24, 2024 · 5 comments · Fixed by #150 or #160 · May be fixed by #161
Closed
2 of 3 tasks
Tracked by #33 ...

ci: Container images release #109

mudler opened this issue Jun 24, 2024 · 5 comments · Fixed by #150 or #160 · May be fixed by #161
Assignees
Labels
enhancement New feature or request

Comments

@mudler
Copy link
Contributor

mudler commented Jun 24, 2024

As part of the release process there should be some consumable artifacts.

Can we have for instance a container image that users can pull?

Have a github action that deploys the opentensor subtensor and runs the initial create subnet:

This could replace the running "devnet" that have deployed based on / triggered by updates to the main branch of our fork of opentensor/subtensor, so that we control when we redeploy updates to main on our own public devnet / testnet chain
This should optionally allow for updates to our private devnet code without necessarily starting with a fresh chain.
This may involve a more volatile private devnet where we run branches other than main when testing changes to the subtensor codebase, and should also optionally allow retaining or starting from a fresh chain database.
Github action could also provision required infra to run subtensor / devnet on, or that could be handled separately (as with oracle nodes vs. oracle app currently).

Acceptance criteria

  • we have a GHA workflow that publishes container images when the bittensor repository is tagged
  • the images are public and can be pulled by everyone
  • the images don't have sensitive configurations, but can be used with specific network configurations (E.g. testnet, devnet, ecc)
@5u6r054
Copy link
Contributor

5u6r054 commented Jul 2, 2024

Now there is a GHA workflow that creates 5 public images under docker compose that anyone can pull. There is a Makefile, and a readme.md has been updated, so now you can clone the repo and do make up and it will pull the latest 5 images (subtensor, subnet, validator, miner, protocol) and start them all. make logs will show the output. The result is you can go to localhost:8000/docs and see docs of the validator API, you can call them on port 8080. A masa protocol node is up on port 8081 and connected to masa testnet, and responds to requests from the miner via the validator.

@mudler
Copy link
Contributor Author

mudler commented Jul 8, 2024

Screenshot from 2024-07-08 15-02-59

Seems it doesn't work for tagged releases and we got no images published for 0.5 ( https://github.com/orgs/masa-finance/projects/12/views/1?layout=board&filterQuery=-status%3ADone&pane=issue&itemId=66218527 ) - reopening

@Luka-Loncar
Copy link

Has this been attended maybe @5u6r054 and just hasn't been moved?

@mudler do you know maybe if anything has changed about this issue?

@obasilakis obasilakis self-assigned this Jul 9, 2024
@mudler
Copy link
Contributor Author

mudler commented Jul 9, 2024

I think @5u6r054 is busy with the testnet launch setup, this isn't yet delivered

@Luka-Loncar
Copy link

Tagging is not implemented here with GHA - it is covered with other tasks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
4 participants