No hint on the number of IP addresses required for MetalLB

Bug #2065389 reported by Nobuto Murata
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Snap
Triaged
Low
Unassigned

Bug Description

The prompt of setting the IP range doesn't hint anything about the number of IP addresses required for the Sunbeam deployment.

$ 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):

I didn't take a deeper look yet, but it seems at least two are required. Otherwise it simply fails.

Name: ovn-relay
Namespace: openstack
Labels: app.juju.is/created-by=ovn-relay
                          app.kubernetes.io/managed-by=juju
                          app.kubernetes.io/name=ovn-relay
Annotations: controller.juju.is/id: fa151232-96dc-4330-8917-edddfa4c45d6
                          juju.is/version: 3.2.0
                          model.juju.is/id: 9b04a76e-d8b8-43b0-8bd7-9b453d044523
Selector: app.kubernetes.io/name=ovn-relay
Type: LoadBalancer
IP Family Policy: SingleStack
IP Families: IPv4
IP: 10.152.183.134
IPs: 10.152.183.134
LoadBalancer Ingress: 192.168.123.81
Port: southbound 6642/TCP
TargetPort: 6642/TCP
NodePort: southbound 30907/TCP
Endpoints: 10.1.32.221:6642
Session Affinity: None
External Traffic Policy: Cluster
Events:
  Type Reason Age From Message
  ---- ------ ---- ---- -------
  Normal nodeAssigned 65s (x27 over 124m) metallb-speaker announcing from node "sunbeam-1" with protocol "layer2"

Name: traefik
Namespace: openstack
Labels: app.juju.is/created-by=traefik
                          app.kubernetes.io/managed-by=juju
                          app.kubernetes.io/name=traefik
Annotations: controller.juju.is/id: fa151232-96dc-4330-8917-edddfa4c45d6
                          juju.is/version: 3.2.0
                          model.juju.is/id: 9b04a76e-d8b8-43b0-8bd7-9b453d044523
Selector: app.kubernetes.io/name=traefik
Type: LoadBalancer
IP Family Policy: SingleStack
IP Families: IPv4
IP: 10.152.183.35
IPs: 10.152.183.35
Port: traefik 80/TCP
TargetPort: 80/TCP
NodePort: traefik 30149/TCP
Endpoints: 10.1.32.220:80
Port: traefik-tls 443/TCP
TargetPort: 443/TCP
NodePort: traefik-tls 32023/TCP
Endpoints: 10.1.32.220:443
Session Affinity: None
External Traffic Policy: Cluster
Events: <none>

Revision history for this message
Nobuto Murata (nobuto) wrote :

Looks like the number is 4 as of today.

$ kubectl describe all -n openstack | grep -B1 'Type: *LoadBalancer'
Selector: app.kubernetes.io/name=ovn-relay
Type: LoadBalancer
--
Selector: app.kubernetes.io/name=traefik
Type: LoadBalancer
--
Selector: app.kubernetes.io/name=traefik-public
Type: LoadBalancer
--
Selector: app.kubernetes.io/name=rabbitmq
Type: LoadBalancer

Revision history for this message
Nobuto Murata (nobuto) wrote :

Additionally, what's MetalLB and why it's needed is not well covered in the tutorial. e.g.
https://microstack.run/docs/single-node-guided

It would be good to explain it in both CLI and the tutorials or naming it differently in CLI would be good.

> MetalLB address allocation range

Since the initial users do not care much what's technology is used for exposing OpenStack services in the beginning.

Revision history for this message
Nobuto Murata (nobuto) wrote :
Revision history for this message
James Page (james-page) wrote :

Lets update the documentation and the prompt to detail the range required and remove MetalLB from the wording - this is for access to control plane services and that level of detail should be sufficient (and insulates the prompt from future changes to the loadbalancing choice in k8s).

Changed in snap-openstack:
status: New → Triaged
importance: Undecided → Medium
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.