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.

Sign up for GitHub

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

Status updates (raw notes) #5

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Status updates (raw notes) #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 31 additions & 1 deletion index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,10 @@ mobu would run the nublado notebooks but not attempt the tap one.

The advantage of this approach is that developers can check in new notebooks for services without necessitating mobu changes.

**Status:**

https://mobu.lsst.io/user_guide/in_repo_config.html#service-specific-notebooks

Notebook caching (or not)
-------------------------

Expand All @@ -114,7 +118,7 @@ We could manually invoke an API or refresh on a timer, but a notebook on-merge i
We still need to re-read on mobu (re-)start; this will be the only way to pick up notebook changes in sites without in-bound internet (eg the summit).
It is a feature for the summit mobu's behavior to remain stable until manual intervention in any case.


**Status:** https://mobu.lsst.io/user_guide/github/refresh.html

Reliance on specific data holdings
----------------------------------
Expand Down Expand Up @@ -144,6 +148,7 @@ Branches
The need to maintain two different branches has been eliminated with mobu's ability to easily be configured to run off different branches for cases where it is useful to have an "in-development" version deployed.
Hence cherry-picking is just annoying with no particular benefit.


Outputs
-------

Expand All @@ -158,6 +163,8 @@ Ideally something like https://github.com/srstevenson/nb-clean would be integrat

This may also be of use to other notebook repo maintainers.

**Status:** There is a pre-commit hook and a Github action that runs the pre-commit hook for system-test.


Write-Only (or not)
-------------------
Expand All @@ -176,6 +183,8 @@ This means a user will have easy access to these additional repos without clutte

Mobu bot users check notebooks directly from Github and hence will not be affected by this.

**Status:** We have resolved this by the new tutorial pull mechanism

Directories
-----------

Expand All @@ -193,6 +202,10 @@ Reasons for opting for a directory exclusion list include:
- An exclusion manifest at directory granularity is less hassle than per-notebook (less bookkeeping when renaming, etc)
- Whether to run or not is self-serve for repo maintainers and does not involve phalanx PRs.

**Status:**

https://mobu.lsst.io/user_guide/in_repo_config.html#exclude-notebooks-in-specific-directories

Summit
------

Expand All @@ -204,6 +217,7 @@ Summit

These had better be passive, we don't want to move the telescope or anything.... We should check what if any protections there are for this, eg is there further authorisation required to perform certain tasks


Timing
------

Expand All @@ -217,6 +231,9 @@ This has been controversial in discussion with the reasonable argument that note

Any metrics should arguably be dispatched to Sasquatch for self-evident dogfooding purposes.

**Status:**

Handled in the new metrics system [screenshot]

Recommended
-----------
Expand All @@ -230,6 +247,10 @@ Recommended
We already mobu the latest (most recent) weekly; the problem is that due to the time it takes to identify, test and deploy a new recommended image, the latest weekly is no longer the candidate recommended.
Given the amount of human attention involved in bumping recommended, adding the candidate to a mobu configuration explicitly is no less expedient that engineering a specific pattern such as tagging the container.

**Status:**

[document process]

Mobu as CI
----------

Expand All @@ -242,6 +263,10 @@ Mobu as CI
Humans are doing right now what the computer can do.
We want to allow notebook contributors to see errors before they go to production.

**Status:**

https://mobu.lsst.io/user_guide/github/ci.html

Mobu's role in phalanx
----------------------

Expand Down Expand Up @@ -270,6 +295,10 @@ Documentation

**After:** Create mobu.lsst.io documentation for developer (user) documentation.

**Status:**

https://mobu.lsst.io

Permissions
-----------

Expand All @@ -289,3 +318,4 @@ This means they'll require help getting their flocks started, and iterating on a

We need to rethink the interaction of the REST API and the Phalanx configuration for mobu, figure out where we want to put the relevant configuration, and probably figure out a better security model for manipulating running flocks.
This probably includes additional operations on flocks as well, such as pausing a flock so that it still shows up in the daily report but reports as paused.

Loading