afnix/infra
0
0
Fork 0
Code Issues 40 Pull requests 10 Projects Releases Packages Wiki Activity

Slowly absorb Lix infrastructure #89

New issue
Open
opened 2024-08-01 20:23:13 +00:00 by raito · 3 comments
raito commented 2024-08-01 20:23:13 +00:00 (Migrated from git.lix.systems)
Copy link

Following a Lix governance decision, the Lix project is willing to let the infrastructure be merged in this repository.

  • build01.aarch64.lix.systems: #129
  • Buildbot (buildbot.lix.systems): #125
    - [ ] build02.aarch64.lix.systems: #125 not required anymore
  • Binary cache (cache.lix.systems)
  • Forgejo (git.lix.systems): done partially in #179
  • Gerrit (gerrit.lix.systems): done partially in #178 #188
  • SSO / IdP (identity.lix.systems): done partially in #180
  • build01.aarch64-darwin.lix.systems
  • core.lix.systems
  • any other box that we are missing

special handling, see below:

  • Grafana/Monitoring (monitoring.lix.systems)

cc @hexchen @jade (let me know if I'm missing something or feel free to edit.)

Following a Lix governance decision, the Lix project is willing to let the infrastructure be merged in this repository. - [x] build01.aarch64.lix.systems: #129 - [x] Buildbot (buildbot.lix.systems): #125 ~~- [ ] build02.aarch64.lix.systems: #125~~ not required anymore - [ ] Binary cache (cache.lix.systems) - [x] Forgejo (git.lix.systems): done partially in #179 - [x] Gerrit (gerrit.lix.systems): done partially in #178 #188 - [x] SSO / IdP (identity.lix.systems): done partially in #180 - [x] build01.aarch64-darwin.lix.systems - [ ] core.lix.systems - [ ] any other box that we are missing special handling, see below: - [x] Grafana/Monitoring (monitoring.lix.systems) cc @hexchen @jade (let me know if I'm missing something or feel free to edit.)
hexchen commented 2024-08-01 20:57:49 +00:00 (Migrated from git.lix.systems)
Copy link

Unsure whether we want to migrate Matrix; or just migrate the draupnir account and put a bunch of static redirects in place for the existing room aliases. Other than that, sounds good to me.

Unsure whether we want to migrate Matrix; or just migrate the draupnir account and put a bunch of static redirects in place for the existing room aliases. Other than that, sounds good to me.
raito commented 2024-08-01 21:23:04 +00:00 (Migrated from git.lix.systems)
Copy link

At least, we can move it under this repo, I guess!

At least, we can move it under this repo, I guess!
raito commented 2024-10-06 10:16:58 +00:00 (Migrated from git.lix.systems)
Copy link

Monitoring stack move will imply redirecting all the new metrics to our existing stack, this requires moving every hosts here or adding a "Floral systems" module in our web-services to start sending the metrics over there.

Then, we can migrate the old data via mimirtool import and destroy the monitoring stack.

Monitoring stack move will imply redirecting all the new metrics to our existing stack, this requires moving every hosts here or adding a "Floral systems" module in our web-services to start sending the metrics over there. Then, we can migrate the old data via `mimirtool import` and destroy the monitoring stack.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
staging
docs-afnix-fr
broker-flows
goaccess
alerting-to-zulip
better-backup-monitoring
forgejo-runners-sprinkles
abm
afnix-social-logins
hyp01
benchmarks
afnix-oidc
voidlinux-tenant
x86_builder_v6_only
besadii-release-branches
tom-hubrecht/audit
repair-ofborg
i-wish-i-had-jj-and-gerrit
scheduled-builds
gerrit-hydra
single-node-ceph
storage-project
cache-lix
email-groups
format
No results found.
Labels
Clear labels   
Compat/Breaking

Breaking change that won't be backward compatible

  
Difficulty/Architectural

Requires changes in multiple pieces of the stack: the Nix interpreter, etc.

  
Difficulty/Easy

Infrastructure beginner friendly tasks

  
Difficulty/Hard

Requires prior knowledge, research and design

  
Help Wanted

Looking for a first task to pick? This one is looking for somefew to do it as well!

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Testing

Issue or pull request related to testing

  
Priority/Critical

The priority is critical

  
Priority/High

The priority is high

  
Priority/Low

The priority is low

  
Priority/Medium

The priority is medium

  
Reviewed/Confirmed

Issue has been confirmed

  
Reviewed/Duplicate

This issue or pull request already exists

  
Reviewed/Invalid

Invalid issue

  
Reviewed/Won't Fix

This issue won't be fixed

  
Security

This is a security issue

  
Silenced Alert

This issue was created to track a silenced alert which needs remediation work.

  
Status/Abandoned

Somebody has started to work on this but abandoned work

  
Status/Blocked

Something is blocking this issue or pull request

  
Status/Need More Info

Feedback is required to reproduce issue or to continue work

  
Status/Postponed

We can do this later

  
Tracking Issue

Umbrella issue of many things at the same time

No labels
Compat/Breaking
Difficulty/Architectural
Difficulty/Easy
Difficulty/Hard
Help Wanted
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Security
Silenced Alert
Status/Abandoned
Status/Blocked
Status/Need More Info
Status/Postponed
Tracking Issue
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: afnix/infra#89
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?