Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

Overhaul the current FBC schema for OLMv1. This will be a design and prototypes to address multiple issues we have today with the catalogs.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

The goal is to address those problems we have today:

• Improve OCP and Operator updates
  • Design FBC Schemas for support lifecycle and OCP compatibility metadata
• Support more than just registry+v1 (e.g. Helm)
  • Extensible in the direction of supporting multiple bundle formats
  • Configuration schema discovery
• Size / Performance considerations
  • Reduce metadata to minimum necessary
  • Consideration for CPU/memory needs for processing the data structures
• Data quality
  • Move package-level metadata to package level in FBC
  • Metadata for all bundles
• Console UX needs
  • Decouple UI metadata from resolution metadata
  • Package metadata is queryable
  • Bundle metadata is queryable
  • Bundle search facets

Non-Goals

No expectation of migration from existing FBC schemas to new FBC schemas.

No expectation of support for new FBC schemas in OLMv0.

No expectation of tooling changes to generate new FBC schemas.

No expectation of backward compatibility with any previous release of OLMv0 or opm.

No expectation of downstreaming anything for use in OpenShift.

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

<enter general Feature acceptance here>

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

<your text here>

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

<your text here>

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>