Exosphere

Hi! I've found myself confused by the way allocation use is displayed. Specifically, I keep wondering whether I have, for example, used 43,814 SUs so far, or if I instead have 43,814 SUs remaining. It might have to do partially with the color ... [More] scheme, but I think it's good and makes sense that it uses Indiana University's colors. Instead what this MR proposes is to change the wording, so in my screenshot above, it would instead read 6,186 SUs remaining, and display the amount of the original allocation in the tooltip, under the start and end dates. Here's a mockup: I'm open to any suggestions/changes, and of course I will totally understand if you think it should stay the way it is now. Thanks, and have a good weekend! [Less]

Chris Martin (e77a1b5f) at 03 Dec 00:52 Merge branch 'update-su-counter-text' into 'master' ... and 2 more commits

Problem/Opportunity Statement If a user has set an AAAA recordset for ipv6 using Horizon or Terraform, an error will display upon entering their allocation on Exosphere. First reported by community member and was able to reproduce by creating an ... [More] AAAA record in Horizon, then logging in to Exosphere (error below). As far as I can tell this error has little to none downstream effects, but I do not regularly use ipv6 so I could be wrong. Also, ipv6 is not widely used by the Jetstream2 community yet, so I don't think many users are seeing this error. CRITICAL at 2024-12-03 13:35:40 UTC -- while trying to get a list of record sets for project TRA230023 -- BadBody: Problem with the value at json.recordsets[2]: { "id": "b1392eb7-cfe1-4655-9df8-3e3a714bc3bd", "zone_id": "105ed8b2-270f-4690-bc2d-c215055d25f7", "project_id": "53f449a040d14cef8512b69e4ad521cd", "name": "test.tra230023.projects.jetstream-cloud.org.", "zone_name": "tra230023.projects.jetstream-cloud.org.", "type": "AAAA", "records": [ "2001:18e8:c02:110:3::8" ], "description": null, "ttl": 3600, "status": "ACTIVE", "action": "NONE", "version": 1, "created_at": "2024-12-03T13:35:11.000000", "updated_at": null, "links": { "self": "https://js2.jetstream-cloud.org:9002/v2/zones/105ed8b2-270f-4690-bc2d-c215055d25f7/recordsets/b1392eb7-cfe1-4655-9df8-3e3a714bc3bd" } } Failed to parse DNS record type What would success / a fix look like? The error appears to be due to Exosphere not recognizing this recordset type. I don't believe there is support for managing recordsets in Exosphere, so I don't believe this error will affect any practical use of Exosphere (I could be wrong here). That being said, the display of an error was enough to push a user to submit a ticket. If anything, perhaps the rating of this kind of error should be demoted from 'CRITICAL' to one of less severity so as to not alarm the user. [Less]

Overview Complementary work for !984. Depending on their remote types, Security Group Rules can take remote IP prefixes as a parameter. The remote IP prefix is a subnet prefix in CIDR notation. This adds helpers to: Check whether a CIDR is valid. ... [More] Expand IPv6 addresses from their compact form to full form e.g. 2001:db8::1 -> 2001:0db8:0000:0000:0000:0000:0000:0001. How to Test Review the test cases in Tests.elm. Run npm run test. [Less]

Looks good, nice test coverage, thank you @LordParsley!

(Also, apologies for the very delayed review.)

Chris Martin (13050527) at 03 Dec 18:20 Merge branch 'feature/cidr-validation' into 'master' ... and 2 more commits

Overview Complementary work for !984. Depending on their remote types, Security Group Rules can take remote IP prefixes as a parameter. The remote IP prefix is a subnet prefix in CIDR notation. This adds helpers to: Check whether a CIDR is valid. ... [More] Expand IPv6 addresses from their compact form to full form e.g. 2001:db8::1 -> 2001:0db8:0000:0000:0000:0000:0000:0001. How to Test Review the test cases in Tests.elm. Run npm run test. [Less]

Exosphere can start recognizing AAAA records. Relevant code is here https://gitlab.com/exosphere/exosphere/-/blob/130505272c164d2b1af7685969fa0502903d3b25/src/OpenStack/DnsRecordSet.elm#L24-70 Good first issue!

👍 @kylefmohr this makes sense & I like the new "Original Allocation" tooltip way of capturing that information. 📝 (I'm also just noting that the meter widget behaviour stays the same, so when we are at "0 SUs remaining", the meter is full. For me, that's good, it feels intuitive.)