Investigate deploying the application with Solo

[SimiHunjan]

Problem

The application is not currently deployed with Solo.

Solution

Review Solo and identify how the Transaction Tool can be deployed with it.

• Add support for consuming internal and external IPs from Solo for mirror node and consensus nodes #1454
• Solo to provide way to get internal and external IPs
• Define Helm chart

Alternatives

No response

[RAMTO]

@SimiHunjan Please provide more details regarding this issue.

[SimiHunjan]

Yes, this is the Solo project: https://github.com/hashgraph/solo. We want to spin up the backend of the Transaction Tool when a new Solo network is created just like the services are automatically deployed like consensus node, mirror node, etc. This way the backend of the Transaction Tool can automatically be setup for use. The expectation is that our team would contribute a PR to Solo that adds this functionality, I believe this will entail creating a helm chart etc.

[SimiHunjan]

A helm chart or something similar needs to be done first. IPs from inside the cluster needs be to pulled into the frontend. If Solo can export the files of IPs for consensus nodes and mirror nodes and front end can ingest the file to communicate the local IPS and external mirror node IPs.

Requires:

• Helm chart (DevOps)
• How the frontend and backend will communicate with the external and internal IPs for Solo