the default suggestion as 10.20.21.10-10.20.21.20 is not accessible outside of the microstack host machine

[Nobuto Murata]

In the bootstrap process:

$ sunbeam cluster bootstrap --role control --role compute --role storage
WARNING: Minimum system requirements (4 core CPU, 16 GB RAM) not met.
Management networks shared by hosts (CIDRs, separated by comma) (192.168.123.0/24):
MetalLB address allocation range (supports multiple ranges, comma separated) (10.20.21.10-10.20.21.20):

The management network is automatically detected and suggested:
https://github.com/canonical/snap-openstack/blob/599e01aa263729d8f411241531bc424934b9ce05/sunbeam-python/sunbeam/commands/juju.py#L317-L323

However, the default suggestion for MetalLB is hardcoded as 10.20.21.10-10.20.21.20
https://github.com/canonical/snap-openstack/blob/599e01aa263729d8f411241531bc424934b9ce05/sunbeam-python/sunbeam/commands/microk8s.py#L76-L84

That's confusing to users if they don't know the relation between the management network and MetalLB IP addresses. At least, we can suggest that the IP range within the management network should be used here.

[Nobuto Murata (nobuto)]

This is actually a bigger problem when `--accept-defaults` is used.

The single node tutorial relies on --accept-defaults and it could use the non functional 10.20.21.10-10.20.21.20 range.

https://microstack.run/docs/single-node#bootstrap-the-cloud-5
> sunbeam cluster bootstrap --accept-defaults

[James Page (james-page)]

Sounds like we need to improve the docs - the default range for MetalLB for the all-on-one is designed to only be usable directly on the machine, not from outside of the machine so from that perspective there is no relationship with the management network.

External access to API's is explained in the multi-node tutorial - where a subrange from one of the subnets from a configured network interface is used to provide access instead.

[Nobuto Murata (nobuto)]

> Sounds like we need to improve the docs - the default range for MetalLB for the all-on-one is designed to only be usable directly on the machine, not from outside of the machine so from that perspective there is no relationship with the management network.

Is this expectation set/written somewhere? It might be a disappointment when an user finds out that the deployed OpenStack cannot be accessed by anybody other than localhost after deploying everything even though it's an all-in-one scenario.

[James Page (james-page)]

Agreed - this is not explicit in the documentation - we'll get that updated.