Add meetings_notes/ engineering_meeting_24-08-29.md
This commit is contained in:
parent
44efe31a8e
commit
f2c6d2ed76
110
meetings_notes/ engineering_meeting_24-08-29.md
Normal file
110
meetings_notes/ engineering_meeting_24-08-29.md
Normal file
@ -0,0 +1,110 @@
|
||||
<h1>Engineering Circle Meeting 2024-08-29 </h1>
|
||||
|
||||
<h2>Table of Contents</h2>
|
||||
|
||||
- [Main Content](#main-content)
|
||||
- [grid stack project](#grid-stack-project)
|
||||
- [mycelium](#mycelium)
|
||||
- [manual info\_grid + tfgrid-sdk-ts](#manual-info_grid--tfgrid-sdk-ts)
|
||||
- [minting](#minting)
|
||||
- [ZOS changes and minting](#zos-changes-and-minting)
|
||||
- [network filtering story](#network-filtering-story)
|
||||
- [upgrade tfchain runtime, change for billing](#upgrade-tfchain-runtime-change-for-billing)
|
||||
- [QSFS](#qsfs)
|
||||
|
||||
# Main Content
|
||||
|
||||
## grid stack project
|
||||
|
||||
- done
|
||||
- grid stack
|
||||
- hub
|
||||
- next
|
||||
- bert works on some details
|
||||
- notably: to be able to deploy separately or together the grid stack and hub
|
||||
- if together, the specs are higher, so this will be documented
|
||||
|
||||
## mycelium
|
||||
- 0.6 to improve network traffic for protocol
|
||||
- 0.55 (notes below might not be clear)
|
||||
- needs to be released
|
||||
- GUI not part of mycelium itself
|
||||
- Binary mycelium included in the GUI
|
||||
- will be a separate release
|
||||
- GUI
|
||||
- windows users
|
||||
- should be able to use 0.55
|
||||
- will ship an installer for mycelium
|
||||
- need serpare DLS (?) installed
|
||||
- some requirements in place
|
||||
- users experience will be the first to fully support end-users
|
||||
|
||||
## manual info_grid + tfgrid-sdk-ts
|
||||
- added a setting so PRs on info_grid are only merged when dashboard releases are updated
|
||||
- dashboard updates
|
||||
- apps
|
||||
- support
|
||||
- jitsi
|
||||
- jenkins
|
||||
- domains
|
||||
- management a separate
|
||||
- click on domain
|
||||
- create domain
|
||||
- can delete it, etc.
|
||||
|
||||
## minting
|
||||
|
||||
- 3.14 release situation
|
||||
- feature enabled in zos for health checks
|
||||
- implemented in a way when when fbot nodes woke up
|
||||
- attempt health cehck before network stack fully up
|
||||
- creates chain of events in tfchain
|
||||
- resolve in violation
|
||||
- didn't wake up within 30 min
|
||||
- Lee+Scott dsicussed this on github
|
||||
- decision: fixing in minting code not appropriate
|
||||
- not minting issue per se
|
||||
- it's a zos issue
|
||||
- Solution for now
|
||||
- health checks disabled
|
||||
- one month of minting affected: July
|
||||
- numbers of node affected: TBD
|
||||
- TODO: Scott will check the numbers of nodes affected
|
||||
- TODO: Next meeting, we check the numbers of nodes affected and decide if we compensate
|
||||
|
||||
## ZOS changes and minting
|
||||
|
||||
- change in zos needs to be compatible with minting
|
||||
- if changes in zos, can potentially effect the minting
|
||||
- e.g. order of events
|
||||
- need to take special care that it is compatible with mitning
|
||||
- e.g. fbot needs specific order of events
|
||||
|
||||
## network filtering story
|
||||
|
||||
- it is paused until we have updated from ops
|
||||
- we used 18.04 before and it led to issues
|
||||
- fixed with ubuntu 24.04
|
||||
- this is being worked on
|
||||
- will take some time
|
||||
- once fixed
|
||||
- we can continue the testing
|
||||
- priority
|
||||
- get zos works with mycelium, node public IP, change in UI
|
||||
- once we have ready images
|
||||
- we can continue the network filtering story
|
||||
|
||||
## upgrade tfchain runtime, change for billing
|
||||
|
||||
- ready to deploy
|
||||
- start deploying on Monday on devnet
|
||||
|
||||
## QSFS
|
||||
|
||||
- Doing some testing on zdbfs
|
||||
- Need help from Erwan
|
||||
- erwan busy with tfchain
|
||||
- lee busy with lee
|
||||
- TODO: ask Erwan to check issues
|
||||
- IF: by Wednesday next week, no help from Erwan
|
||||
- IFTODO: Lee will try to have a look
|
Loading…
Reference in New Issue
Block a user