The smoke tests can run on mainnet

[v0d1ch]

Why

We want to be able to run our smoke tests on mainnet in order to assure ourselves everything runs smoothly.

What

We would use the same mechanism as currently for preview and preprod but be executable on mainnet. Noticeable differences:

• It would use real assets
• lot bigger resources required (100G storage instead of 1 for instance)

How

Manage funds

Implement descent protection of our Hydra faucet funds. We plan to always keep the funds under 100Ada so that it's not a big deal.

Some process let us move funds from somewhere to the faucet so that these smoke tests could run.

We can run the smoke tests on mainnet the same way as we run them on preview and preprod today, manually with GitHub C.I.

• Return faucet funds #773 Improve asset management: remaining funds are always sent back to the faucet at the end of the tests.
• Can override faucet key from github secrets #765
• Integrate mainnet in the release process:
  • run the smoke test on mainnet
  • grab the txid of the published scripts
  • ...

Out of scope: Not directly related but we should probably run the smoke tests on preview and preprod nightly.

Manage cardano node

• Play with runners #775 Use a dedicated instance as a github runner

  • Create a dedicated VPC instance which holds the cardano-node mainnet state persistently somewhere, e.g. /data/smoke-test-mainnet/
    • declaratively managed
    • access is shared in the team
  • Install github self-hosted runner daemon on it
  • Register this daemon instance with our repository
  • Make sure the smoke test for mainnet is only deployed to this/these dedicated runner(s)
  • Invoke the smoke test with --state-directory /data/smoke-test-mainnet and mainnet config

---

Discussed options:

How to actually manage Cardano-node synchronization requirements?

• use mithril (not yet mainnet ready)
• use and manage a persistent Cardano-node
• use a managed, as a service, Cardano-node instance (Demeter)
• dedicated GitHub runner

How can we connect the CI hydra-node with the persistent Cardano-node? No unix socket possibility.

[ghost]

We might want to tweak the scripts to consume less ADAs, in the spirit of limiting the amount of exposed ADAs.