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

Q2 goals checkpoint #2543

Closed
damianavila opened this issue May 17, 2023 · 7 comments
Closed

Q2 goals checkpoint #2543

damianavila opened this issue May 17, 2023 · 7 comments
Assignees

Comments

@damianavila
Copy link
Contributor

Context

This is a checkpoint issue trying to collect high-level information about the status quo on the existing Q2 goals.

Proposal

If you are an engineer leading one of the existing goals (gdoc: https://docs.google.com/document/d/1dUO2USQlRbcjOEkjlCu1gyTaPBZmGZSRF4L-_9xecmA/edit#heading=h.ycnyhh6g1ri6 and https://github.com/orgs/2i2c-org/projects/22/views/50), please respond to this issue with:

# Goal title
# Status (a summary of the work done and the current state, no more than a paragraph)
# Execution plan for the rest of the quarter (a summary as well, no more than a paragraph).

cc @2i2c-org/engineering

Updates and actions

No response

@pnasrat
Copy link
Contributor

pnasrat commented May 23, 2023

Billing

#2431

Status

Historic cost analysis done manually with @yuvipanda and handed over to @colliand who has been doing cost recovey.
Automation work in progress and nearing completion.

Execution plan for the rest of the quarter

@pnasrat Complete GCP shared cluster code and merge (support has taken up my time this last week post Paris)
@pnasrat complete documentation tasks
@pnasrat Co-ordinate Q2 billing with @colliand for early July

@pnasrat
Copy link
Contributor

pnasrat commented May 23, 2023

Monitoring and Alerting

#2267

Status

Unstarted - @yuvipanda and I want to request pushing a Quarter as billing took far more cycles plus travel/vacation

@yuvipanda
Copy link
Member

JMTE normalization

#2201

Status

It's now integrated into our infrastructure! They have also been asked to use the 2i2c support process, rather than ping us on slack.

The image needs to be moved to something matching what we do for all our other images.

@consideRatio
Copy link
Member

consideRatio commented May 24, 2023

GESIS

Status

The project has established a place in the existing ecosystem of open source projects that fits quite well. A github repo for the binderhub-service chart is setup with relevant automation, and we have one for the UI side of things. The chart and UI is separately demoed to a degree.

Execution plan for the rest of the quarter

  • chart: Handle pushing to docker registries that requires credentials
  • Deploy for testing as a opt-in basehub dependency
  • End to end test setup including use of Yuvi's UI
  • Help binderhub towards 1.0.0
  • Document critical things to enable contributions
  • Ensure UI repo gets relevant automation

@consideRatio
Copy link
Member

Node sharing

#2121

Status

It has been piloted and adopted in a few clusters successfully, where overall faster startup times seem to be especially appreciated by end users. The goal of allowing all communities to opt-in to this won't be met with the available capacity allocation, and I propose 2i2c focus towards this as soon as possible.

Execution plan for the rest of the quarter

I'm allocated 5% time on this, and I'm already out of this time for the quarter.

@consideRatio
Copy link
Member

k8s cluster upgrades

#2293

Status

Its me and Georgiana who is allocated time towards this goal, me at 10% and Georgiana at 5%. I've worked more than the allotted time already and can't focus on this much going onwards.

  • All EKS clusters are upgraded, with a guide on how to upgrade, seven clusters were upgraded
  • Not all GKE clusters are upgraded, with preliminary notes on how to upgrade established
  • The AKS cluster (utoronto) is not upgraded, and needs to be recreated

Execution plan for the rest of the quarter

  • Schedule cluster upgrade time slots with remaining clusters' communities, prioritizing utoronto

@damianavila damianavila moved this from Ready to work to In progress in DEPRECATED Engineering and Product Backlog Jun 8, 2023
@damianavila damianavila moved this from Todo 👍 to In Progress ⚡ in Sprint Board Jun 8, 2023
@damianavila damianavila moved this from In progress to Waiting in DEPRECATED Engineering and Product Backlog Jul 5, 2023
@damianavila
Copy link
Contributor Author

Remaining updates:

Closing this one since Q2 is already behind us!

@github-project-automation github-project-automation bot moved this from In Progress ⚡ to Done 🎉 in Sprint Board Jul 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Archived in project
Development

No branches or pull requests

4 participants