networks api doesn't include range information

[Michael Foord]

For Juju we need to know the networks for a node, including the static and dynamic range for a network.

The networks api allows us to filter by node, but doesn't return the dynamic/static range information. The nodegroups interface api does include the information, but (AFAICS) doesn't allow us to filter by node. The nodegroup-interface api doesn't include the CIDR (although it can be manually constructed).

[Blake Rouse (blake-rouse)]

How is this information useful to Juju?

Do you want to be able to filter node selection based on a network?

With juju using the static ip address API call, what is the reason for knowing the dynamic range?

[Michael Foord (mfoord)]

We only need the static range (but it would seem odd if you added that and not the dynamic range - although in principle either one is fine as you can deduce the other).

At the moment we need to fetch both the nodegroup interfaces and the networks, construct CIDRs for the nodegroup interfaces, and then pair them up in order to get all the information we need. (We also need the network name and the VLANtag.)

We want all the networks a node is on - so we're filtering networks by node (not nodes by network). The current filtering works fine for that.

[Blake Rouse (blake-rouse)]

We need to include the cluster interface information in the networks API, when that network is linked to a cluster interface.