| 28 May 2024 |
 frank.af | now configurable in config.js.
Doing cloud_configs is a bit more, since we need to poll per-keystone, and only show relevant banners. Same with the status.io integration | 19:48:03 |
 cmart | cool. perhaps for now, just a static banner one can configure on the live server? region-specific and status.io integration in subsequent MRs? | 20:24:14 |
| frank.af | Exactly my plans. I added a flag to let admins configure the url to banners.json, just cleaning things up a bit | 20:24:51 |
| cmart | sharing from another friend group..
https://spectrum.ieee.org/lean-software-development | 21:17:00 |
| cmart changed the room topic to "Development discussion for Exosphere. See https://gitlab.com/exosphere/exosphere/activity for project activity on GitLab. For general community discussion, please join #exosphere:matrix.org." from "Development discussion for Exosphere (https://gitlab.com/exosphere/exosphere). For general community discussion, please join #exosphere:matrix.org.". | 23:07:35 |
| 29 May 2024 |
 Kyle | Apologies! I may not be able to make today's meeting as it's (another) public holiday here for voting day 🗳️ | 09:11:46 |
| 3 Jun 2024 |
| cmart | we've got several reports from JS2 users of inability to create instances, with this error:
Message
{"conflictingRequest": {"code": 409, "message": "Multiple security_group matches found for name 'exosphere', use an ID to be more specific."}}
Recovery hint
It's possible your quota is not large enough to launch the requested server
| 17:41:06 |
| cmart | the timing of reports suggests some kind of new issue, given recent work on security groups | 17:41:50 |
 julianp | https://gitlab.com/exosphere/exosphere/-/issues/997 | 18:08:44 |
| 4 Jun 2024 |
| Kyle | Sorry for the unintended new project consequences & thanks for the fix, cmart 🙇 | 07:18:20 |
| cmart | all good, I definitely would not have caught it reviewing !934 | 14:23:44 |
| 11 Jun 2024 |
| frank.af | Investigating 934 (showing the amount of GPU ram for a flavor)
Is it reasonable to ask integrators (JS2 specifically here) to use the extra_specs to add more metadata, or to set descriptions for their flavors?
I could parse the custom "trait:CUSTOM_A100X_[gb]C" spec, but that would only work for that specific trait | 17:06:53 |
| cmart | I think it's reasonable to ask folks to set metadata, provided we degrade gracefully when they don't | 17:08:36 |
| cmart | the description makes too much sense, Frank | 17:11:34 |
| cmart | * the description field makes too much sense, Frank | 17:11:38 |
| frank.af | I was thinking the "best" options here would be to show the flavor description if set, and additionally support fields like display:VGPU_COUNT, display:VGPU_VRAM, etc | 17:11:45 |
| frank.af | description was added in nova 2.55, so we may need to consider that too 😁 | 17:12:04 |
| cmart | aye, that's kind of ancient though.. Queens release in 2018 had it | 17:13:13 |
| cmart | * aye, 2.55 is kind of ancient though.. Queens release in 2018 had it | 17:13:19 |
| frank.af | I don't love how rigid the elm-ui table is in this case. anything more than a couple word description would get messy | 17:44:19 |
| cmart | agreed.
one simple idea: where the flavor description is non-empty, we could show it in a toggle tip. | 19:00:17 |
| cmart | that would add just one icon to each table row (at most) | 19:00:41 |
| frank.af | Not a bad idea, I was getting all deep playing with fudging CSS grid into elm-ui | 19:00:46 |
| frank.af | grid isn't hard, but it's a hack | 19:57:31 |
| 13 Jun 2024 |
| cmart | if folks like !947 and !948, we should merge them at the same time, and also create banners.json files in each prod environment at the same time. | 23:01:59 |
| 14 Jun 2024 |
| julianp | They look good. | 01:05:49 |
| 15 Jun 2024 |
| frank.af | https://jfmengels.net/analyzing-extra-files/ | 19:24:37 |
| 18 Jun 2024 |
| cmart | I think our banner woes are sorted. I merged !947 and !948. I created empty banners.json in the web root dir for each of the prod sites. they all load without any complaint about a missing banners file. | 21:33:26 |
| cmart | lol, spoke too soon, local dev environment tries to fetch http://banners.json | 21:36:26 |
| cmart | I figured it out. when the URL path prefix is blank, we end up with a double leading slash in the banners URL (//banners.json). | 21:55:46 |
