Milestones
List view
- No due date
As a community member, I should be able to find and read resources that indicate the data points such as usage patterns from Curator data. DoD: - Publish at least one article on the Research website.
Overdue by 4 year(s)•Due by March 31, 2022- Overdue by 4 year(s)•Due by June 30, 2022•2/2 issues closed
Get approval from the cost management BU and OpenShift Engg to build Operator Curator. DoD: - Define a PRD and get it approved by the cost management PM - Identify and get commitment from a senior engineer to lead the operator development
Overdue by 4 year(s)•Due by February 11, 2022•1/1 issues closedThe Curator instance should be the go-to option for all the Operate First users who want to know their project utilization. This milestone maps to issue #327(https://github.com/operate-first/SRE/issues/327) in the Operate First SRE board.
Overdue by 4 year(s)•Due by December 17, 2021•4/5 issues closedAs a developer or a system administrator, I should be able to view the health status of Curator deployment retrospectively and also determine the cause of failure in any sub-systems of the Curator by tracing logs.
Overdue by 4 year(s)•Due by December 17, 2021•5/5 issues closedAs a developer in the Curator project, I should be able to go through a checklist before I submit my code for a peer review. DoD: - Unit test cases for code coverage. - Test cases should be integrated with the CI pipeline. - The data passes the sanity check. - Coding standards and Linting should be enabled. - Documentation, demo, and reports should be updated during every release.
Overdue by 4 year(s)•Due by February 28, 2022•4/4 issues closedInclude infomation on quotas as part of reports (what is each user/project quota).
Overdue by 4 year(s)•Due by January 31, 2022At what size do we want to “store” usage data from Koku metrics in an archive, instead of keeping it all? Should this be up to the admin as a configuration item, or default because data stores will get too large for efficient processing at some point? - Should users have the ability to change the database timeline?
Overdue by 4 year(s)•Due by December 17, 2021•3/3 issues closedPublish blogs, demos, and articles for Curator. Keep in mind that demos might be used to help solutions engineers pitch Curator to customers, so the content needs to be fairly polished for things we want to demo. Communicate the inspiration, requirements, plan, and onboarding documents related to the Curator with the general public. DoD: Curator in the Operate First portal. An article on the Red Hat Research website. Common minimum program for the Curator & AIops collaboration. Slide deck for the Curator that can be presented for the potential users. Importance of the Curator project for the Research team. (Research team internal)
Overdue by 4 year(s)•Due by December 17, 2021•9/9 issues closedCurator should be deployed in Mass Open Cloud and PSI. DoD: - Daily, weekly and monthly reports should be generated for Mass Open Cloud OCP. (01/31/2022) - Daily, weekly and monthly reports should be generated for PSI.
Overdue by 4 year(s)•Due by March 31, 2022•10/10 issues closedAs an end-user of the Curator system, I should be able to access the infrastructure usage reports only for the projects I own or have access to using RBAC.
Overdue by 4 year(s)•Due by April 30, 2022•1/1 issues closed