* Rename `pallet-finality-verifier` to `pallet-bridge-grandpa`
* Missed some CamelCase ones
* Update logging target in GRANDPA pallet
* Rename `pallet-bridge-call-dispatch` to `pallet-bridge-dispatch`
* Rename the dispatch pallet folder
* Update logging target in Dispatch pallet
* Missed a couple
* Format the repo
* Stop listing individual pallets in Compose logs
* Use correct pallet name in module doc comments
* Add `pallet-bridge-dispatch` to README project layout
* Sort crate names in TOML files
* Rename `pallet-bridge-grandpa` runtime Call alias
* use runtime:: prefix for message-lane pallet traces
* renamed message-lane (module and primitives) folder into messages
* replace "message lane" with "messages" where appropriate
* High level docs - start.
* Clean up README
* Start adding details to high level docs
* More docs on the header sync pallet
* Testing scenarios document.
* Add some scenarios.
* Add multi-sig scenario.
* Start writing about message dispatch pallet
* Move content from old README into PoA specific doc
* Apply suggestions from code review
Co-authored-by: Andreas Doerr <adoerr@users.noreply.github.com>
* GRANDPA for consistency.
* Describe scenario steps.
* WiP
* Add notes about block production and forks
* Update.
* Add sequence diagram for Millau to Rialto transfer
* Clean up header sync pallet overview
* Remove leftover example code
* Clean up testing scenarios and amend sequence diagram.
* Linking docs.
* Add some more docs.
* Do a bit of cleanup on the high-level docs
* Clean up the testing scenario
* Fix typos in flow charts
* Fix small typo
* Fix indentation of Rust block
* Another attempt at rendering block correctly
* TIL about lazy list numbering in Markdown
* Add list numbers across sections
* Start counting from correct number
* Update README to use correct path to local scripts
* Wrap ASCII art in code block
Co-authored-by: Tomasz Drwięga <tomasz@parity.io>
Co-authored-by: Tomasz Drwięga <tomusdrw@users.noreply.github.com>
Co-authored-by: Andreas Doerr <adoerr@users.noreply.github.com>
* Rename `rialto` deployment to `eth-sub-bridge`
* Add base Compose configs for Rialto and Eth-PoA nodes
* Add new compose file for eth-sub deployment
* Rename bridge-nodes to rialto-nodes
* Update bootnode entries for Rialto nodes
* Remove new compose file since it was used for quick test
* Rename bridge nodes in entrypoint scripts
* Remove all nodes from Eth-Sub Compose file
The nodes should be getting pulled in from the new compose files.
* Remove TODO comment
* Rename nodes to networks
Reflects the fact that a set of nodes makes up a network.
* Add Compose file for Millau network nodes
* Enable logging for all Millau nodes
* Delete Rialto reserved peers file
* Rename `bridge-config` to `scripts`
* Add Compose file for Rialto-Millau bridge
* Move bridge deployments into `bridges` folder
* Drop `bridges` prefix from bridge deployments
* Rename folder that had scripts for working with binaries
* Move proxy configuration to common top level folder
* Make a top level `monitoring` folder
* Start updating deployment README
* More updates in the README
* Remove usage of Git overrides
* Remove scripts to run Eth<->Sub
I don't think these are used anymore
* Remove Github Docker build instructions from main README
* Add note about monitoring
* Update Millau state root
* Add script for running and updating Compose deployments
* Remove old update script
* Explain usage of `run` script
* Update Millau state_root again
* Remove repeated Prom image from Rialto-Millau bridge
* Quick fix to stop containers in `run` script
* Pin GrafanaMatrix Dockerfile to old commit
The latest master has some changes in how the application is run. We don't
want to update just yet so we're pinning to an old commit.
* Make Compose files use a project directory
The main consequence of this change is that all paths have to be specified
from the root of the `deployments` folder. However, this makes it so that
we can reuse components in different deployments, like the GranfaMatrix
Dockerfile which is shared by all bridges.
* Use `project-directory` when stopping and updating network
If we don't use the full Compose command which includes `project-directory`
not all the containers get cleaned up correctly.
* Update path in Bridge Dockerfile
* Correctly ignore `target` folders in Docker builds
* Wait for Rialto nodes before running relay
* Make `run` script a little less sketchy
* Clean up deployment README
* Remove stray line
* Have run script automatically change into correct directory
* Use PoA-to-Rialto instead of Eth-to-Sub in names
* Rename `eth-poa-sub` bridge deployment to `poa-rialto`
* Use /entrypoints volume for entrypoint scripts
* Be more consistent with relay service names
* Remove `docker-compose` prefix from network Compose files
* Add comment explaning Grafana Matrix commit
* Fix wording in README
Co-authored-by: Tomasz Drwięga <tomusdrw@users.noreply.github.com>
* Cleanup unused line in README
* Add link to Slava's test scripts
* Remove uneccessary piping when `cd`-ing in `run.sh`
Co-authored-by: Tomasz Drwięga <tomusdrw@users.noreply.github.com>
* Add dev deployment profile with Ethereum PoA config
* Add scripts for running local components
* Use `openethereum` folder
* Add local development instructions in README
* Add note about clone location
* Point to right folder for scripts
* Add some missing back-ticks
* Remove Bertha and Carlos as authorities
* Fix a line length issue
* Add Prometheus and Grafana to Docker Compose
* Expose relay's Prometheus metrics port
* Use Docker network references intead of localhost
When you have containers on the same network they don't communicate
over localhost, they instead refer to their container names
* Move dashboard components into deployment folder
* Update folder structure for Grafana and Prometheus config files
The new folder structure more closely matches the expected defaults
by Grafana and Prometheus, which allows us to clean up the paths
in our docker-compose file a bit.
* Add documentation about Prometheus and Grafana
* Refer to Prometheus server instead of node
Nikos Kontakis