Hi Bruno,

1 – Yes they created more keyspaces for the tables, this is to have more freedom to configure what replication strategy/factor you want to apply for every set of data. We did get complaints about the amount of keyspaces to manage, so we are looking to combine again a couple of tables into a known set of keyspaces. This will make it easier to manage the user permissions on the keyspaces if you do this.

2 – Yes, Alarms have been migrated towards Elastic. The reason for this is that we have to retrieve alarms in many different ways (e.g. based on view level, element level, service level, …) in order to do this efficiently we stored the alarms multiple times in Cassandra with different keys for retrieval. This was causing some overhead and for systems with a lot of alarms (and big alarms), we saw a heavy load on Cassandra because of this. So the decision was made to move it to Elastic which allows us to use the indexing capabilities from Elastic instead of storing it multiple times.

3 – Once your data is migrated from the local DB to the central DB, the local DB is no longer needed. And as you probably know already the centralized DB has many benefits scaling independently, swarming capabilities in upcoming releases, …