Background
In order for Solo to start/spin up networks with a saved state generated from a different network it will need to support placing the correct files on disk in the correct location.
An override-network.json file will be looked for by the consensus node in NetworkAdminConfig::upgradeSysFilesLoc (default of data/config).
If the above file is not found, then the consensus node will look for a scoped override network file from a subdirectory named after the round number (for example <NetworkAdminConfig::upgradeSysFilesLoc>/123/override-network.json).
The V057RosterSchema.java in hedera-services provides a restart-only schema which sets the appropriate active roster for genesis, override, or upgrade). It may look for the override file for the round number specified in the migration context
See this PR in hedera-services for more implementation details if necessary.
Acceptance Criteria
Solo has been updated to support putting the override-network.json file(s) in the correct location for networks it spins up.
Test to verify this process is sucessful.
Dependencies
None
Business Need
For Solo to support the network transplant process, which has been recently updated on the consensus node.
Requested Feature
Background In order for Solo to start/spin up networks with a saved state generated from a different network it will need to support placing the correct files on disk in the correct location.
override-network.jsonfile will be looked for by the consensus node inNetworkAdminConfig::upgradeSysFilesLoc(default ofdata/config).<NetworkAdminConfig::upgradeSysFilesLoc>/123/override-network.json).See this PR in hedera-services for more implementation details if necessary.
Acceptance Criteria
override-network.jsonfile(s) in the correct location for networks it spins up.Dependencies
Business Need
For Solo to support the network transplant process, which has been recently updated on the consensus node.
Additional Context
No response