Split OSDU Platform Releases by Service Groups

Status

• Proposed
• Trialing
• Under review
• Approved
• Retired

Context & Scope

The number of OSDU services has grown greatly and it is necessary to rationalize dependencies between groups of services into individual releases.

Service Releases should be grouped in the following manner:

• OSDU Core & Utilities
  • Entitlements
  • Partition
  • Policy
  • Notification
  • Registration
  • Legal
  • Unit
  • CRS Catalog/Conversion

• OSDU Data Catalog
  • Storage
  • Indexer
  • Indexer Queue
  • Search
  • Dataset
  • Elasticsearch (deployment)

• OSDU Data Ingestion
  • Workflow Service
  • CSV Parser
  • Energistics Parsers
  • Airflow (deployment)

Each DDMS and DMS should have an independent release cycle, platform compatibility is tied to OSDU Core version

Decision

Group services into individual releases. Tie Data Catalog and Data Ingestion to release versions of OSDU Core

Rationale

1. Grouping services together by their purpose and position in the platform helps to simplify understanding of the large number of services that now exist on the platform.
2. Allows DDMS services to develop and release separate from Core release cycles

Consequences

Releases need to be coordinated between groups of services. A compatibility matrix might need to be maintained.