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

Migrate node-perf-dash to aaa cluster (or retire) #753

Closed
1 task
spiffxp opened this issue Apr 15, 2020 · 13 comments
Closed
1 task

Migrate node-perf-dash to aaa cluster (or retire) #753

spiffxp opened this issue Apr 15, 2020 · 13 comments
Assignees
Labels
area/infra Infrastructure management, infrastructure design, code in infra/ sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability.

Comments

@spiffxp
Copy link
Member

spiffxp commented Apr 15, 2020

/wg k8s-infra
/sig node
/sig scalability
(I don't actually know which of these sigs this belongs to, if any)
/area cluster-infra
/assign @bartsmykla

@k8s-ci-robot k8s-ci-robot added wg/k8s-infra sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. area/infra Infrastructure management, infrastructure design, code in infra/ labels Apr 15, 2020
@spiffxp
Copy link
Member Author

spiffxp commented Apr 15, 2020

Bart has been pinging in kubernetes slack on #sig-node and #sig-scalability trying to find owners or users of this service

@bartsmykla
Copy link
Contributor

Also @thockin is pinging people who I heard wanted to take ownership of this project.

/assign @thockin

@bartsmykla
Copy link
Contributor

@spiffxp @dims we discussed yesterday with @thockin that despite our efforts to communicate with people who can be interested in node-perf-dash there is no response and we are close to the decision to retire the project. We think about setting a deadline as a last day of this month for someone to pick this up and if note we would just retire it and remove the cluster completely (#754) as it's the last project there. Wdyt?

@dims
Copy link
Member

dims commented Apr 22, 2020

@bartsmykla give it 2 weeks please. just in case folks are dealing with other emergencies. hope you have already notified sig-node mailing list

@bartsmykla
Copy link
Contributor

@dims You are right. Do you think we should give people more than 2 weeks? It's not that crutial to turn it down immidiately but I would like to not lose it from the horisont.

@dims
Copy link
Member

dims commented Apr 22, 2020

2 weeks is reasonable to me. we can always resurrect it if needed.

@spiffxp
Copy link
Member Author

spiffxp commented Apr 29, 2020

/assign @bartsmykla
To send message to sig-node mailing list

@bartsmykla
Copy link
Contributor

I have sent the email: https://groups.google.com/forum/#!topic/kubernetes-sig-node/lNR6RiPzYYY

Lazy consensus final date is set to May 14, 2020

@spiffxp
Copy link
Member Author

spiffxp commented May 27, 2020

Just to update here, someone did claim ownership and so it's being moved. Based on discussion in today's meeting it sounds like we're waiting on confirmation to cutover and turn down the old deployment.

@bartsmykla
Copy link
Contributor

So after #903 was merged. The project is now fully migrated and https://node-perf-dash.k8s.io points to the aaa

/close

@k8s-ci-robot
Copy link
Contributor

@bartsmykla: Closing this issue.

In response to this:

So after #903 was merged. The project is now fully migrated and https://node-perf-dash.k8s.io points to the aaa

/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.

@MHBauer
Copy link

MHBauer commented Jun 2, 2020

Who claimed ownership?

I think to myself, "how useful could the dashboard be if the backing data is filled by a bunch of failing tests".

Are they going to fix the tests? They can't be getting good data.

@bartsmykla
Copy link
Contributor

@MHBauer @lorqor claimed ownership

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infra Infrastructure management, infrastructure design, code in infra/ sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability.
Projects
None yet
Development

No branches or pull requests

6 participants