Problem:

We are implementing the Primaza Project. There is a need to claim registered services. See Primaza Architecture for details on cluster registration.

Goal:

To enable developers working on application clusters to claim services in the primaza claimable service catalog. Claims can be created in primaza cluster or in application cluster. The scope of this epic is for primaza MVP (v0.1)

Why is it important?

This will enable developers to be abstracted away from the details about how services are provisioned and managed. They will only have visibility to claimable service catalog and to manage claims for those services.

Use cases

• As a k8 developer, I would like to be able to inspect all registered services in the Primaza catalog, so that I can predict the service I can claim for my application
• As a k8 developer, I would like to be able to claim a RegisteredService in Primaza catalog for my application running in a specified environment (dev, test, stage, prod), so that I can use the service in my applications running in that environment.
• As a k8 developer, I would like to be able to claim a RegisteredService in Primaza catalog targeting a specific cluster and namespace, so that I can use the service in my applications running in that namespace.
• As a k8 developer, I would like to be able to claim a RegisteredService in Primaza catalog targeting a specific cluster, namespace and compute resource, so that I can use the service in my specified resource.
• As a k8 developer, I would like to be able to inspect all claims targeting one of my environments so that I can predict what services are ready to bind to my application.

Demo requirements

A great demo will show developer claiming services from primaza cluster targeting a specific environment tag but also claims on specific application clusters that get routed to the primaza cluster for processing.

UI requirements

The UI for primaza will be used for demo and marketing purposes only during MVP. For GA the UI will depend on what OpenShift or StoneSoup tools we integrate with.

Acceptance criteria

• Development:
  Can claim registered service from primaza clusters.
  Can claim registered service from the application cluster
  Can delete a claim
  Can get status about service being claimed
  Can Track Service Claim metrics for the OpenShift Fleet

• QE:
  Github flow set up to execute behave test harness
  Service Claim Tests are implemented and run on PR updates

• Documentation:
  All claim options are documented in our primaza github project
• UI:
  There is a UI that can facilitate the lifecycle of claims in primaza cluster

Dependencies (External/Internal)

TBD

Design Artifacts

Primaza Architecture

Exploration

Note