[07:47:01] XioNoX: wrt fastnetmon_api_client, I'll have a look in a bit, might simply be that it's missing in the .install file [07:47:59] moritzm: ok! thanks [09:21:54] XioNoX: the fastnetmon_api_client depends on the gRPC API, which is disabled in the build. I'll see if I can enable this later, not sure yet what kind of dependencies this would pull in and if they are available [09:23:13] ok, we don't need it for now but might in the future, so please ignore if it's a pain [09:25:39] ack, I'll give it a quick shot later [09:36:03] XioNoX: you around? [09:36:42] volans: yep [09:37:35] so the prefix for svc in netbox are marked as pool [09:37:39] see https://netbox.wikimedia.org/ipam/prefixes/93/ [09:37:48] and effie just went to add a new IP and got the .0 [09:37:55] https://netbox.wikimedia.org/ipam/ip-addresses/6906/ [09:38:14] the svc prefixes were not included on purpose on those where we reserved the first 5 IPs [09:39:03] yeah, that's valid [09:40:13] confusing, but .0 is a valid IP. We can remove the "is pool" flag so it doesn't assign them [09:40:16] you're not in -serviceops [09:40:17] same with .255 [09:40:27] or reserve them [09:41:41] that would works too [09:41:59] or change the assignment script to not assign .0 and .255 [09:42:12] might be better? [09:42:45] as that applies to both v4 and v6 [09:43:01] those are assigned manually [09:43:04] and not only /24s, but any smaller prefixes [09:43:14] frpm https://wikitech.wikimedia.org/wiki/DNS/Netbox#How_to_manually_allocate_a_special_purpose_IP_address_in_Netbox [09:44:19] ok [09:45:02] other option is to accept using .0 and .255 [09:45:14] theywant mostly manual pick [09:46:05] ? [09:48:34] you should really be in the chat [09:48:36] in -serviceops [09:53:32] joined [09:58:18] thx [11:42:47] XioNoX: I guess enabling api_client needs a closer look at the build, my quick attempts weren [11:43:06] sufficient, best to open a task for now I'd say [11:43:18] moritzm: thanks for having a look!