Janus with Scylla(Cassandra) backend. ConfiguredGraphFactory vs JanusGraphFactory vs JanusGraphManager+static graphs?

[melgenek]

Hello, Janus community!

I'm preparing the Janus setup with Scylla as a backend. I made the ConfiguredGraphFactory with it, but I have a couple of points that are not 100% clear to me.

1. Each graph has to be created via ConfiguredGraphFactory.open. This action leads to the creation of a new keyspace in Scylla.
   For example, the graph mycoolgraph would create the mycoolgraph keyspace.
   Let's say I created the ConfigurationManagementGraph in the keyspace management.
   So I have two keyspaces management and mycoolgraph.
   Do I understand correctly that the management keyspace is used solely for keeping metadata regarding the newly created graphs and the mycoolgraph is keeping the actual data?

2. The ConfiguredGraphFactory.createConfiguration is creating a config for the new graph. There are some configuration options like storage.cql.local-core-connections-per-host. According to this issue these options cannot be overridden, because they have the FIXED mutability level.
   Is it true that I need to properly choose these options before creating the new graph and there are no ways to update the options other than creating a new graph?

3. I would really love to create a database on startup, rather than asking users of Janus to connect and use the management api to create the new graph.
   My setup is going to have multiple Janusgraph-docker pods running in k8s with the same configuration.
   As I understand JanusGraphFactory is not storing the metadata in any backend and is designed for a single node setup.
   Am I supposed to use the JanusGraphManager to create a graph on startup?

In general, it's not very clear which option to choose for the non-embedded setup JanusGraphManager, ConfiguredGraphFactory or ConfigurationManagementGraph.

Thank you in advance for helping me!