Internal Data Model

Backwards compatibility, during minor version upgrades, can be broken due to changes in the relations data.

This document is intended only for charm developers.

We aim to document the internal data models currently used in order to carefully assess any breaking changes in future releases of the OpenSearch charm.

We distinguish between the different types of relations.

1. Peer relation:

a. Application data:

• security_index_initialised: bool: whether the security index has been initialized through the opensearch securityadmin script.
• admin_user_initialized: bool: indicates that the admin user has been created and set.
• bootstrap_contributors_count: int:
• nodes_config: List[Node]: full list of current nodes configured by the charm.
• deployment_description: DeploymentDescription: description of the current deployment.

b. Unit data:

• started: bool: whether this unit has fully started and the node is up.
• tls_configured: bool: flag set when TLS is fully configured in a unit (the TLS secrets / certificates and keys have been set and stored on disk)
• bootstrap_contributor: bool: whether a cluster_manager eligible node has been part of the bootstrapping process (initial_cluster_managerin opensearch.yml)
• certs_exp_checked_at: str: expiration date of the certificates (date_format %Y-%m-%d %H:%M:%S)