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

soroban-rpc: deploy public instance on futurenet #418

Closed
mollykarcher opened this issue Feb 14, 2023 · 9 comments
Closed

soroban-rpc: deploy public instance on futurenet #418

mollykarcher opened this issue Feb 14, 2023 · 9 comments
Assignees

Comments

@mollykarcher
Copy link
Contributor

mollykarcher commented Feb 14, 2023

What problem does your feature solve?

We'd like to facilitate more engagement/usage of RPC in the ecosystem prior to launching on testnet. We eventually plan to host a public instance on testnet as well, but not pubnet.

What would you like to see?

A deployed public instance of soroban-rpc on futurenet on stellar domain,rpc-futurenet.stellar.org. Deployment should be integrated into the soroban release process so that it receives updates appropriately.

Initial deployment to use k8s and the quickstart soroban-dev image for soroban rpc, and ingress route for dns.

This initial deployment will later be refactored to use new rpc service deployment image from #382 and updated helm chart to use/config that image.

What alternatives are there?

@mollykarcher mollykarcher moved this from Backlog to Next Sprint Proposal in Platform Scrum Feb 14, 2023
@Shaptic
Copy link
Contributor

Shaptic commented Feb 15, 2023

We eventually plan to host a public instance on testnet as well, but not pubnet.

Are we sure this is a good precedent to set? I'd rather see deployments be as simple and streamlined as possible.

@mollykarcher mollykarcher moved this from Next Sprint Proposal to Current Sprint in Platform Scrum Feb 21, 2023
@sreuland
Copy link
Contributor

for stop gap, @leighmcculloch helped out, and did a short term deployment of quickstart(soroban-rpc enabled) on Digital Ocean:

https://stellar-futurenet.4d63.com/

@sreuland sreuland moved this from Current Sprint to In Progress in Platform Scrum Feb 23, 2023
@sreuland sreuland self-assigned this Feb 23, 2023
@jcx120
Copy link

jcx120 commented Mar 1, 2023

Ops ticket for reference:
https://github.com/stellar/ops/issues/2165

sreuland added a commit to sreuland/soroban-tools that referenced this issue Mar 3, 2023
sreuland added a commit to sreuland/soroban-tools that referenced this issue Mar 3, 2023
@sreuland
Copy link
Contributor

sreuland commented Mar 3, 2023

k8s manifest for the deployment is up for review.

#470

coordinating with ops for next steps on stellar/ops#2165 discussion

sreuland added a commit to sreuland/soroban-tools that referenced this issue Mar 6, 2023
@sreuland sreuland moved this from In Progress to Needs Review in Platform Scrum Mar 6, 2023
@sreuland sreuland moved this from Needs Review to In Progress in Platform Scrum Mar 8, 2023
@sreuland sreuland moved this from In Progress to Needs Review in Platform Scrum Mar 9, 2023
@sreuland
Copy link
Contributor

sreuland commented Mar 9, 2023

the manfiests for prd deployment up for review - https://github.com/stellar/kube/pull/1337

@mollykarcher mollykarcher moved this from Needs Review to Done in Platform Scrum Mar 13, 2023
@leighmcculloch
Copy link
Member

@sreuland @tomerweller Do we need stellar-futurenet.4d63.com/ anymore?

@tomerweller
Copy link

no. we have rpc-futurenet.stellar.org

@willemneal
Copy link
Member

@tomerweller Should we add this to CLI? Have a special futurenet network so you can do --network futurenet or SOROBAN_NETWORK=futurenet without having to manually add it?

@tomerweller
Copy link

@willemneal yes I like that idea!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

7 participants