Skip to content

Milestones

List view

  • - End-user reports may need to be different than admin reports (or not) - Admin and end-user reports need some cleanup on resource descriptions, consistent measurement (fewer decimals), and descriptions of what the measurements mean - Cases, where individuals are members or owners of multiple projects, may need some grooming--haven’t really seen them yet - Decide if we want to keep the “rough” reports around, now that we have the ability to download rough data through the API

    Due by December 23, 2021
    1/1 issues closed
  • Detailed documentation of the Curator project should be created in Read the Docs. The document should have version control access through GitHub.

    Due by November 30, 2021
    2/2 issues closed
  • As an administrator of the OpenShift platform, I should be able to visualize the infrastructure utilization information in Trino and Superset which in turn will use the Curator data.

    Due by November 30, 2021
    4/4 issues closed
  • Integrate at least 2 external applications with the Curator project. Applications under consideration: - Trino (AI-CoE) - Tableau

    Due by September 30, 2021
  • As an end-user, I should be able to install the entire technical stack required to run the Curator project by just executing install.sh. DoD: - Images should be pulled - Database should be installed with the default tables

    Due by September 30, 2021
    1/1 issues closed
  • As an end-user of the Curator, I should be able to make API calls to: - Download autogenerated reports. - Query for reports for a specific time period. - Fetch the Curator data to a 3rd party tool.

    Due by October 8, 2021
    3/3 issues closed
  • As an end-user, I should be able to receive daily, weekly, and monthly reports for the project I own in an email without having to log in to the Curator project. Note: If a user owns more than one project, multiple emails will be sent for individual projects. DoD: - Identify the project owner's email address with the projects/namespaces. - Push the automated reports generated for individual projects to the respective email addresses.

    Due by October 31, 2021
    4/4 issues closed
  • As a developer in the Curator project, I should be able to add the test cases for the code I write in a test suite and the CI/CD pipeline will check for any feature breakage before my code is committed to the remote repository. DoD: - Identify functional and unit test cases. - Identify features to consider for regression testing. - Build the test suite. - Integrate the testing environment to the CI/CD pipeline.

    Due by August 31, 2021
    2/2 issues closed
  • DoD: - Generate at least one daily report for the entire Operate First infrastructure utilization. - Generate at least one custom report for the CPU utilization for any project for any 6 hour period. - Generate at least one daily report in the PSI and MOC OCP clusters.

    Due by September 30, 2021
  • DoD: - Tag/map Curator to Operate First community to provide visibility. - Move GitHub repository, communication challenges to the Operate First organization. - Send out an announcement after the transistion.

    Due by August 31, 2021
    4/4 issues closed
  • DoD: - Define the reports metrics - Define time period for reports - Commit the documentation for reports metrics and time period to GitHub.

    Due by May 19, 2021
    2/2 issues closed
  • DoD: - Reports should be generated from the OCP system using the Koku operator. - The report generated should be committed to the GitHub repository with YAML and the procedure to generate reports.

    Due by May 12, 2021
    1/1 issues closed
  • DoD: - PRD should be viewed and approved by MOC staff, OCP Metering team. - PRD should be committed to the GitHub repository.

    Due by May 12, 2021
    1/1 issues closed
  • DoD: - Every report generated by the Curator should be stored in persistent storage. - An admin should be able to log in and view the data from the storage. - Persistent storage should be fault-tolerant (Power/cluster outage) - An admin should be able to access persistent storage even if the cluster is down. - Define Database lifecycle. - Persistent storage should not be part of the OCP ecosystem.

    Due by August 4, 2021
    15/15 issues closed