[11:25:06] useful Netbox feature for us: https://github.com/netbox-community/netbox/issues/3703 [16:24:51] XioNoX: should cr3-eqsin be in some other state in netbox to get homer to ignore it? [16:25:22] hm actually it's in state 'staged' which seems reasonable enough [16:27:56] first time we're in this situation :) [16:28:51] I have to go, will think about it later [16:28:55] np [20:33:05] cdanis: maybe a specific flag to include non active devices? It's needed to be able to generate a configuration to load on a device not in prod yet [20:33:10] cc volans ^ [20:33:25] yeah there's already a bit in the conffile [20:33:43] what's the initial issue? [20:33:57] volans: cr3-eqsin is staged in netbox but not connected to the network yet, nor any config defined [20:34:24] ok [20:34:59] and? [20:36:07] volans: /etc/homer/config.yaml lists staged [20:36:27] so the daily diff and manual runs will try to push stuff to the device and fail [20:36:53] I guess either only put active in the config, or change its status to planned? [20:36:53] although the lifecycle server page is mostly for servers, staged means online with an OS and puppet, although not yet in full production [20:37:09] so maybe you want to keep it in planned until then [20:37:10] so maybe should be 'planned'? [20:37:12] volans: it's online with an OS but no puppet :) [20:37:20] yeah planned lgtm [20:37:27] in planned will be skipped by the netbox report too [20:37:42] ok, doing that then [20:37:44] but both can be adapted for network devices (the netbox report and homer's config) [20:37:56] if you feel strongly we should ignore staged [20:38:24] nah it's fine like that [20:38:55] nah lgtm [20:39:03] can go 'staged' right when ready to load initial config [20:39:36] https://netbox.wikimedia.org/dcim/devices/?q=&status=planned&role=asw&role=cr [20:39:40] we don't have any staged [20:39:43] those are all planned [20:39:49] we can adapt the workflow as needed [20:40:01] this is the first apparently :D