Bi-weekly Nebari community meeting | 15 Aug 2023🪴💎

tags: community-meeting

Meeting link: https://meet.google.com/rio-ngrj-kyh
Moderator: …
Notetaker: …

Welcome to the Nebari community meeting!

Guidelines

• This meeting is covered by Nebari's Code of Conduct.
• Please feel free to participate in open discussions, share your projects, or sit back and listen!
• When you'd like to speak in a discussion, use Google Meet's "raise hand" feature, and wait for the moderator to call your name.
• We use takingnotes.rocks to randomly select a meeting moderator and note taker at the begining of each meeting. We'll make sure to select returning members, as to not put new community memebers on the spot. :)
  • The moderator is responsible for running the meeting, and giving everyone a speaking opportunity
  • The note taker is responsible for recording all important points in this HackMD document, and post it on the GitHub Discussions forum after the meeting for better searchability.

Attendees

All meeting attendees can add your details here!

• Prefered name / pronouns (optional) / @github-handle / affiliation (optional)
• Eskild Eriksen / he/him @iameskild / Quansight
• Chris Ostrouchov / he/him / @costrouc / Quansight
• Pavithra
• Johnny
• Scott

Introductions

If you are new to this meeting, this is the time to introduce yourself!
We have an introduction template below, but please share what you're comfortbale sharing. :)

[Quick intro: Hi, I'm ..! I live in …, and study … / work as a … at … I'm a Nebari user/contributor/maintianer, and I'm primarily i interested in … In my spare time, I enjoy …]

Updates and announcements

Share ongoing work, new releases, something cool you built on Nebari, upcoming conferences, and more!

• Nebari Extension Mechanism
  • Documentation WIP https://github.com/nebari-dev/nebari-docs/pull/352
  • Can override arbitrary stages and add new ones before and after
  • Can add arbitrary subcommands
  • Neabri Extension Feedback and necissary improvements https://github.com/nebari-dev/nebari/issues/1894
• Fully embrasing pydantic for Nebari schema
  • project_name: myproject is now a valid nebari-config.yaml since we leverage default values in pydantic
  • domain is now an optional (we use load-balancer default)
• Testing improvements
  • pytest module for nebari testing
    • possible to do paramaetrized deployments of nebari deployments e.g. AWS + gpu node group + monitoring disabled
    • prior to this PR we had a fixed set of tests one for each cloud with default config
  • https://github.com/nebari-dev/nebari/pull/1910

Discussion topics

Is there something we should discuss as a group? Something you want feedback on?

Note: If you have a usage question, our Discussion Forum would be a place to ask. :)

• few branches are protected, release branch that we merge back into main
  • merge conflicts
  • https://github.com/nebari-dev/nebari/pull/1876
• Hashicorp BSL implications and actions link to faq around license
  • No major action right now
• Backup/Restore command https://github.com/nebari-dev/nebari/issues/743
  • Will soon be prioritized
• Argo ENH prioritization: https://github.com/nebari-dev/nebari/issues/1900
• Check with team re, best practices: https://github.com/nebari-dev/nebari/issues/1884
• CDS Dashboard replacement - almost 2 months out

Actions

Clear action items with an assignee.

• @costrouc - review PR https://github.com/nebari-dev/nebari/pull/1910
• @pavithraes - open issue for resolving main and develop history (should always be a fast-forward)
• Scott - Add uninstalling extensions to ENH-tracking issue

Did we complete last meeting's actions?

(Note taker, please copy past action items here)