Separate configurations for implementation and ecosystem teams.

[parthshah1]

Current docker compose is a comprehensive yaml file defining:
3 drand nodes
2 lotus + miner nodes
1 forest node
1 curio node
1 yugabyte node

Issues
We're catering to two audience with different takeaways from the tool.

Implementation teams focusing on L1 network and protocol level assertions and workload don't really care much on FOC smart contract deployments as they take a long time to deploy and setup synapse, which is not something important for protocol testing.

Ecosystem teams focusing on building dapps/contract and L2 part of the chain don't care about the nodes, they just require RPC and deployed contracts to talk to so they can run their tools.

Solution

Create 2 configuration files and 2 endpoints.
What does it solve??
It enables teams to run quick tests without waiting for 5-10 minutes to startup and load contracts.
It provides separate playgrounds for the teams to play with without interfering each other's work.

[parthshah1]

@ryao-01 Does having 2 endpoints mean we'll have 2 different dashboard for both reports???

[ryao-01]

@ryao-01 Does having 2 endpoints mean we'll have 2 different dashboard for both reports???

No, reports from both endpoints will show up in https://cobalt-bunny.antithesis.com/runs.

[parthshah1]

@ryao-01 Hmm, then what are benefits of 2 endpoints now that I think of.

[ryao-01]

The main benefits (aside from keeping things orderly and separate) are that we will be able to set different fault injection settings and custom properties for each endpoint. This could also help reduce noise, for example there may be certain property failures that an implementer person would care about - but would just be noise to an ecosystem person (and vice versa).

[parthshah1]

@ryao-01 Shared this in slack:

To make it easier to make changes that won't effect the other team, we will go forward with running 2 endpoints.
We will keep the filecoin endpoint for the Implementors team, and create a new filecoin-foc endpoint for the FOC folks.
Let me know if you are good with these names.

On the GH actions side of things, it would be ideal to switch one of the 12 hr nightly runs to hit the filecoin-foc endpoint.