Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve gather metrics pipeline #118

Closed
6 of 10 tasks
pacospace opened this issue Jul 7, 2021 · 7 comments
Closed
6 of 10 tasks

Improve gather metrics pipeline #118

pacospace opened this issue Jul 7, 2021 · 7 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@pacospace
Copy link

pacospace commented Jul 7, 2021

Is your feature request related to a problem? Please describe.
Improve gather metrics pipeline

Describe the solution you'd like

  • Add env variable for namespace deployment, leave aicoe-ci as default
  • Add namespace deployment to .aicoe.yaml check
  • Add task for platform metrics gathering
  • doc for users to create roles (DOC)
  • SA for custom deployment for users
  • add secrets for Ceph
  • add runtime for test (default to root) to .aicoe.yaml
  • add test name for test type (e.g. feature name for behave) to .aicoe.yaml
  • allow multiple deployments from the same repo.
  • Include docs link in the PR comment explaining the goal of the pipeline.

Describe alternatives you've considered
Leave as it is.

Additional context

@harshad16
Copy link
Member

@Gregory-Pereira would like to assist with remaining.

The remaining task is to enable users to give their namespace information through the .aicoe-ci.yaml
and the aicoe-ci would deploy the deployment in that namespace.
To deploy an app in a different namespace, via an app in another namespace, the service account(SA) requires access to the namespace (which is gained via roles).

@sesheta
Copy link
Contributor

sesheta commented Jan 19, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. labels Jan 19, 2022
@harshad16
Copy link
Member

/remove-lifecycle stale

@sesheta sesheta removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 17, 2022
@sesheta
Copy link
Contributor

sesheta commented May 18, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 18, 2022
@sesheta
Copy link
Contributor

sesheta commented Jun 18, 2022

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 18, 2022
@sesheta
Copy link
Contributor

sesheta commented Jul 18, 2022

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta sesheta closed this as completed Jul 18, 2022
@sesheta
Copy link
Contributor

sesheta commented Jul 18, 2022

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants