[Feature(server/v2 & storev2)]: Configs and Clis

[tac0turtle]

Summary

With server/v2, server modules need to define their own config variable and cli commands. We already migrated some of the legacy config values to store/v2 but its unclear how it all works.

snapshot manager also needs to house its own config and cli commands for snapshotting.

Problem Definition

No response

Proposed Feature

• Sync with storage team on configs, APIs and cli commands needed for store.
• Implement configs for snapshot manager
  • add snapshotting cli commands to snapshot directory.

[cool-develope]

also needs to add pruning cli commands

[alexanderbez]

I can't really speak for CLI commands -- I haven't really spent much time thinking about that. Probably something along the lines of:

• Migration
• Pruning
• State sync management?

As for configurations, things that come to mind:

• SS backend type
• SS specific variables (dataDir, sync, RocksDB opts, etc...)
• SC backend type (i.e. IAVL v1 or v2)
• SS pruning
• SC pruning
• Legacy Store v1 IAVL DB type (for migration, e.g. golevelDB)

[tac0turtle]

• SS specific variables (dataDir, sync, RocksDB opts, etc...)

look into how this could work, also if the app dev should be the one setting it not the node operator

• SC backend type (i.e. IAVL v1 or v2)

if iavl v1, only create SS
if iavl v2 we still need iavl v1 config

• SS pruning

keep recent
keep interval

• SC pruning

keep recent
keep interval

• Legacy Store v1 IAVL DB type (for migration, e.g. golevelDB)

appdb backend type

snapshot manager has its own config
TBD or same as now

[julitabarelkowska]

👍