---
# System prepended metadata

title: "Bi-weekly Nebari community meeting | 11 April 2023 \U0001FAB4\U0001F48E"

---

# Bi-weekly Nebari community meeting | 11 April 2023 🪴💎

###### tags: community-meeting 

**Meeting link: https://meet.google.com/rio-ngrj-kyh**
**Moderator: Pavithra**
**Notetaker: ?**

Welcome to the Nebari community meeting! 

## Guidelines

* This meeting is covered by [Nebari's Code of Conduct](https://github.com/nebari-dev/governance/blob/main/CODE_OF_CONDUCT.md).
* 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](https://takingnotes.rocks/) to **randomly select a meeting moderator and note taker** at the beginning of each meeting. We'll make sure to select returning members, as to not put new community members 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](https://github.com/orgs/nebari-dev/discussions/categories/community-meetings) after the meeting for better searchability.

## Attendees

_All meeting attendees can add your details here!_

* Prefered name / pronouns (optional) / @github-handle / affiliation (optional)
* Chris / @costrouc / Quansight
* Vinicius / @viniciusdc / Quansight
* Pavithra / she-her / @pavithraes / Quansight
* Dharhas / @dharhas / Quansight
* Maxime / @Dr0p42 / NaasAI
* Jeremy / @jravenel / NaasAI
* Loic / @l-loic / NaasAI
* Philip / he-his / @pmeier / Quansight
* Eskild / @iameskild / Quansight
* Adam / @Adam-D-Lewis / Quansight
* Tania / she-her / @trallard / Quansight Labs
* Kim

## 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 comfortable sharing. :)_

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

* Jeremy, CEO of Naas.ai happy to connect here. We are building an all-in-one data platform based on Jupyter. 
* Maxime - CTO at Naas, joined naas 2 years ago
* Loic - from France, part of infra team
* Florent -- background in business, Naas team. from Barcelona
* Scott -- DevOps at Metrostar (Onyx, built with Nebari)
* Johnny -- Metrostar, works with Scott on Onyx
* Dharhas, CTO of Quansight. I helped start Nebari a few years ago because I was fed up of how difficult it was to install Jupyterhub and Dask on the cloud.
* Chris, Tech-Lead of Nebari/Conda-Store. Everyting devops. 
* Adam, Software Developer at Quansight, contributor to Nebari,
* Philip, Software Developer at Quansight, nebari newcomer
* Eskild, Software Developer at Quansight, Nebari developer

## Updates and announcements

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

* [Jeremy] naas.ai:
    > We will prepare a small presentation on how we see the integration with Nebari and our Terragrunt approach for multi-cluster deployment.
    - Integration with Nebari:
        - Offload JupyterHub infra to Nebari
        - Accelerate deployment on multi-cloud
    - Experiments with nebari:
        - Started at the CLI, easy to us
        - helm extensions were , tf_extensions were Neabri-specific, injecting terraform module was too complex
    - Terragrunt to extract Nebari's TF states:
    - https://docs.google.com/presentation/d/1pQcONNB7R5b1R-IhMVYidxlPl3lSzSSnmmTpUV61kpU/edit#slide=id.g1ba5831ca05_1_311
> [name=Tania Allard] - is there any chance you can share the slides Maxime/Jeremy?
> [name=Tania Allard] -  what type of JLab customisations are you considering?
> [name=Chris] nfs permissions (efs, ids/gids), keycloak integration, extension mechanism

- Dharhas: we have Keycloak integrated but we don't use it to it's full potential
    - customizing juputerlab: differnt machines already exisits, we can improve "management", see: https://github.com/nebari-dev/governance/issues/22
    - we're also looking into dev/staging/prod setups
 - Chris: Overall the ask is to modify/extend Nebari -- the extension mechanism will address this
        - NFS / gids questions -- have ids in keycloack and have a way to sync with user, then launch JupyterLab with those ids (some rough ideas)
    - Rich: The need for a fast drive (for temporary files) comes up often

* [Chris]
    * New superadmin group (enough permissions to shoot yourself in the foot and destroy the cluster)
        * conda-store superadmin group can CRUD all environments
    * Keycloak realm-management roles for users (meaning nebari users can now edit users/groups if they hae admin or superadmin credenials)
    * New conda-store ui integrated into conda-store as default ui
    * conda-store will now refuse to build environments when free disk space is less than 5GB (and will give error message to users)
    * conda-store view storage per namespace

* [Pavithra]
    * Nebari-adjacent tutorial & talk at PyCon next week :)

* [Adam]
    * PR in progress - https://github.com/nebari-dev/nebari/pull/1639#issuecomment-1498045124 - Added warning to users when they upgrade to 2023.5.1 telling them they need to manually delete Argo CRDs.
    * PR in progress - add several dashboards from https://github.com/jupyterhub/grafana-dashboards, I want to add a little bit more (folders for dashboards, investigate removing existing dashboards or putting in their own folder, make Prometheus pick up all services with specific annotations on it)

## 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](https://github.com/orgs/nebari-dev/discussions) would be a place to ask. :)_

* Nebari Extension Mechanism see https://github.com/nebari-dev/governance/issues/35
    * High level. Use [pluggy](https://pluggy.readthedocs.io/en/stable/) establish two initial interfaces:
        * Arbitrary commands (passed the nebari config)
        * Stage (render, deploy, destroy, context)
        * Would love feedback on the rfd
        * Philip has used pluggy before, and likes it
        * Tania: Terragrunt might be able to help with the dev/stage deployment story
        * Metrostar -- onboard with the extension direction
* Make the "API" private: https://github.com/nebari-dev/governance/issues/37
* April release `2023.4.1` tomorrow
* Scott -- conda-store 🎉, upcoming reqs for azure deployment and on-prem gpus
    * Azure may not have gpu support currently, need to test
    * on-prem gpus can be exposed using the k8s nebari deployment
* 

## Actions

_Clear action items with an assignee._

- [ ] Assignee - Action item
- [ ] Pavithra -- Make issues to update corresponding docs for April release (conda-store, superuser:keycloak)
- [ ] 

Did we complete last meeting's actions?

(Note taker to copy past action items here)
