Before GA we want to review our CRD definitions as after GA it will be a lot more expensive to change them as we will need to care about compatibility and upgrade of the data.

nova-operator

• DefaultConfigOverwrite: We either need to support it for policy.yaml and api-paste.ini (and providers.yaml for ironic compute) or need to be removed. See OSPRH-2503 
• Debug (StopService, StopJob, PreserveJob): We need to decide if we want to keep this and support this or remove it from the CRD. Or if we can support these with ENV variables instead.
  • Handled in OSPRH-4290
• PasswordSelector.*Database + *DatabaseUser can be replaced with the new field referencing a MariaDBAccount by name once the mariadb password rotation feature is landed.
• PasswordSelector.Service + ServiceUser: Can be deleted if we follow the pattern of password rotation from MariaDBAccount and create a KeystoneAccount CR. At the moment we have no stories to do this globally. This is not is scope for OSPRH-92.
• PasswordSelector.MetadataSecret: Depends on if we want to support password rotation and use the MariaDBAccount pattern for it or not.
• Nova.Spec.Secret (osp-secret): If mariadb, keystone, and metadata passwords are all moved to *Account CRs like MariaDBAccount then we can remove this field.
• Nova.Status.Hash can be removed as it is unused. The rest of the CRs using the Hash field so keep it there.
• DefaultConfigOverwrite to be removed from NovaScheduler, NovaConductor, NovaNoVncProxy as it will be unused as part of OSPRH-2503

placement-operator

• DefaultConfigOverwrite: We either need to support it for policy.yaml and api-paste.ini or need to be removed. See OSPRH-2503
• Debug (StopService, StopJob) and PreserveJob: We need to decide if we want to keep this and support this or remove it from the CRD. Or if we can support these with ENV variables instead.
  • Handled in OSPRH-4290
• PasswordSelector.Database + DatabaseUser can be replaced with the new field referencing a MariaDBAccount by name once the mariadb password rotation feature is landed.
• PasswordSelector.Service + ServiceUser: Can be deleted if we follow the pattern of password rotation from MariaDBAccount and create a KeystoneAccount CR. At the moment we have no stories to do this globally. This is not is scope for OSPRH-92.
• Secret (osp-secret): If mariadb, and keystone passwords are all moved to *Account CRs like MariaDBAccount then we can remove this field.