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: restore preview <-> testnet relaying #3623

Open
1 of 4 tasks
conorsch opened this issue Jan 17, 2024 · 3 comments
Open
1 of 4 tasks

ci: restore preview <-> testnet relaying #3623

conorsch opened this issue Jan 17, 2024 · 3 comments
Assignees
Labels
A-CI/CD Relates to continuous integration & deployment of Penumbra A-IBC Area: IBC integration with Penumbra _P-high High priority

Comments

@conorsch
Copy link
Contributor

conorsch commented Jan 17, 2024

As the IBC implementation comes together, we'd like to have automatic relaying between preview and testnet. We used to have this, based on the go-relayer #2308, but compatibility broke and we never restored it. Today, it'd be useful to have automatic client creation between preview and testnet, for cuiloa development: testnet contains ibc client info, but preview doesn't.

For the relayer software, use hermes. Importantly, we want to use the last-known working version of our Hermes fork: https://github.com/penumbra-zone/hermes . We plan to work on upstreaming Penumbra support to Hermes, but that work isn't done yet (#3477).

Subtasks

  • Create and publish container image for hermes fork, as ghcr.io/penumbra-zone/hermes - ci: add container build workflow for fork hermes#24
  • Write startup scripts to handle new-channel creation for a new preview/testnet connection
  • Clear out old rly build scripts (optional)
  • Deploy
@conorsch conorsch self-assigned this Jan 17, 2024
@conorsch conorsch added on hold A-IBC Area: IBC integration with Penumbra A-CI/CD Relates to continuous integration & deployment of Penumbra _P-high High priority and removed on hold labels Feb 13, 2024
@conorsch
Copy link
Contributor Author

We need to land #3477 first, then this is unblocked.

@aubrika aubrika added this to the Sprint 0 milestone Feb 13, 2024
@avahowell
Copy link
Contributor

#3477 is done now, we should try re-enabling relaying using penumbra-zone/hermes main once the new testnet + testnet preview is launched.

@aubrika aubrika modified the milestones: Sprint 0, Sprint 1 Mar 4, 2024
@cratelyn cratelyn modified the milestones: Sprint 1, Sprint 3, Sprint 2 Mar 18, 2024
@aubrika aubrika modified the milestones: Sprint 2, Sprint 3 Mar 25, 2024
@cratelyn cratelyn modified the milestones: Sprint 3, Sprint 4 Apr 8, 2024
@cratelyn cratelyn modified the milestones: Sprint 4, Sprint 5 Apr 22, 2024
@aubrika aubrika modified the milestones: Sprint 5, Sprint 6 May 6, 2024
@aubrika aubrika added the friction something made this fall into the following milestone & the reason should be noted in a comment label May 6, 2024
@conorsch
Copy link
Contributor Author

conorsch commented May 6, 2024

This work didn't get far: I was sidetracked debugging ICT test failures, and hunting down a regression in the Hermes timeout behavior: #4310 While 4310 is higher priority, this work technically isn't blocked on 4310: we can still try to wire up the testnet/preview channels, even if they close early.

@aubrika aubrika removed this from the Sprint 6 milestone May 6, 2024
@cratelyn cratelyn removed the friction something made this fall into the following milestone & the reason should be noted in a comment label May 6, 2024
@aubrika aubrika modified the milestone: Sprint 8 May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-CI/CD Relates to continuous integration & deployment of Penumbra A-IBC Area: IBC integration with Penumbra _P-high High priority
Projects
Status: Backlog
Status: No status
Development

No branches or pull requests

4 participants