Performing DevOps for a COmanage Registry installation is largely the same as that for any other configuration that uses the database that you are using. This page explores several use cases (such as high availability needs, or large deployments) that may warrant special hosting configurations.

On this Page

1. For High Availability Needs

COmanage Registry provides enrollment flows, identifier management, group management, and lifecycle management for members of organizations. Many organizations feel that those capabilities do NOT require high availability (HA). Instead the identifiers, group memberships, and other details about users are consumed by services and used for authorization and access control and those services, tools, and applications DO require HA. We provide guidance when High Availability may be needed.

2. For Large Deployments

For the most part, COmanage Registry does not need specialized tuning for larger deployments (10k+ records). However, there are a few things to keep in mind.

3. Useful links

  • Container Roadmap - Outlines the strategy for managing and evolving containerized packaging for COmanage. Includes the guiding principles for the work's direction and a description of the resources that support this work. 


  • No labels