!qALrQaRCgWgkQcBoKG:matrix.org

exosphere

16 Members
User-friendly client for OpenStack, https://gitlab.com/exosphere/exosphere/4 Servers

Load older messages


SenderMessageTime
13 May 2021
@cmart:matrix.orgcmart nvm install 14.17.0 mighta done the trick 21:55:42
@cmart:matrix.orgcmartI was on an ancient node/npm21:55:57
@cmart:matrix.orgcmartyep that fixed it, sorry for the trouble21:56:59
@cmart:matrix.orgcmarti still feel dirty every time i have to touch nvm22:09:46
14 May 2021
@julianp:matrix.orgjulianpAll good. Glad you figured it out.21:33:04
@julianp:matrix.orgjulianpI'm having a look at #50721:33:26
@julianp:matrix.orgjulianp

With the monorepo solutions, how were you thinking of solving:

  1. It's easy for cloud operators to offer a customized Exosphere with their own provisioning code that is different from ours

GitLab forks?

22:13:45
@cmart:matrix.orgcmartresponded in #50723:02:20
@cmart:matrix.orgcmartsounds like we're ready to build it then23:05:26
@cmart:matrix.orgcmart😎23:05:34
@julianp:matrix.orgjulianpYup.23:06:14
@julianp:matrix.orgjulianpI can have a look at it if you want. It meshes/overlaps somewhat with "Custom workflow/toolchain/stack sharing"23:07:31
@cmart:matrix.orgcmartsure but how so?23:07:51
@cmart:matrix.orgcmartfeels somewhat self-contained to me23:08:03
@cmart:matrix.orgcmarti feel a bit of ownership for the mess i got us in, so inclined to get us out of it. but if you get to it first i won't stop you23:08:45
@julianp:matrix.orgjulianp It's not really a mess. 23:09:24
@julianp:matrix.orgjulianpBoth issues involve ways to install, share, and configure software on virtual machines.23:09:41
@julianp:matrix.orgjulianpOne may build on the other. Or they might operate at different levels of abstraction.23:10:24
@cmart:matrix.orgcmartsure. though IMO there's requirements-gathering, design work, design review, and a reasonable amount of consensus to be built (both within and beyond this group) before shovel enters ground on that one23:11:21
@cmart:matrix.orgcmart(for one, the meeting with Jeremy)23:11:30
@julianp:matrix.orgjulianpYup.23:11:35
@cmart:matrix.orgcmartnot trying to slow you down, just like, we've done a lot of inductive work but not the deductive work needed to focus a solution23:12:10
@julianp:matrix.orgjulianp#507 might provide lessons for #441.23:12:11
@cmart:matrix.orgcmartI think the closest we've come to deductive/scope is the CSSI proposal23:12:24
@cmart:matrix.orgcmartand that was pretty dang broad 😁23:13:23
@julianp:matrix.orgjulianpRighto.23:14:44
@cmart:matrix.orgcmarthttps://gitlab.com/exosphere/exosphere/-/merge_requests/432 is ready for review!23:54:00
@cmart:matrix.orgcmart

I realize that it implements a feature (assign/unassign floating IPs) that other parts of Exosphere makes kinda broken. julianp if you think we should hide the "unassign" button until the follow-up issue is fixed, i'm cool with that. though I plan to work on the follow-up issue shortly after this is merged.

the diff was just getting real big and I figured I should bite off this chunk rather than trying to fit more in.

23:56:08
@cmart:matrix.orgcmart *

I realize that it implements a feature (assign/unassign floating IPs) that other parts of Exosphere makes kinda broken. julianp if you think we should hide the "unassign" button until the follow-up issue is fixed, i'm cool with that. though I plan to work on the follow-up issue shortly after this is merged.

the diff was just getting real big and I figured I should bite off this chunk rather than trying to fit more in

23:56:28
@cmart:matrix.orgcmart *

I realize that it implements a feature (assign/unassign floating IPs) that other parts of Exosphere makes kinda broken. julianp if you think we should hide the "unassign" button until the follow-up issue is fixed, i'm cool with that. though I plan to work on the follow-up issue shortly after this is merged.

the diff was just getting real big and I figured I should bite off this chunk rather than trying to fit more in.

23:56:30

There are no newer messages yet.


Back to Room List