management_cidr basically to ensure the services installed on this host will be bound to
Hey Klaus, In order: the right IP, so they'll pick the host IP belonging to the network management_cidr, in short NO NEW IP, only the host IP.
MetalLB addresses are used „for internal and public services“ This is mostly due to technical constraints that at this time we can't define two different ip pools in MetalLB, but they will be in the future, we're laying the foundations. Basically, public is intended to be used by the cloud consumers (people starting vms...), therefore it must be exposed to users. While internal is used only by the OpenStack services and should not be exposed to users.
I am afraid OpenStack interfear with the rest of my LAN Sunbeam does not run DHCP server, it relies on MetalLB L2 mode, which basically means MetalLB will respond to ARP requests with its own mac address to redirect traffic inside the cluster. Your DHCP service should be configured NOT to hand out the IP addresses you've given sunbeam. (dhcp reservation)
If I use different networks, do I have to setup one of the servers NIC first? I'm not sure what you're trying to do. But if you want to expose the OpenStack cloud to users outside of the host (be it company user or just yourself from another host), you will need to configure sunbeam external access in remote mode, in this case, you need a dedicated NIC unconfigured that sunbeam will configure for you. (sunbeam configure step)
Don't hesitate if you have any other question. If you want more interactive chatting, we're quite active on this matrix channel https://matrix.to/#/#openstack-sunbeam:ubuntu.com Regards, Guillaume On Tue, Jul 16, 2024 at 1:15 PM klaus.becker@webmen.de < klaus.becker@webmen.de> wrote:
Hi Guillaume,
thanx a lot for Your reply.
I checked the interactive prompts. Honestly, I am not getting the special vocabulary used there. I am a IT guy for years, know everything about IPv4 and of course CIDR notation.
When I am getting You right „management network shared by host“ is my LAN and the OpenStack host ist one node in this. When You write „that’s the address to bind most network services“, all these services will be reached directly from any PC in my LAN. Do these services have different IPs? Or do they use the ONE IP from my host?
MetalLB addresses are used „for internal and public services“ Why internal AND PUBLIC? Where is the border between internal and public?
I am afraid OpenStack interfear with the rest of my LAN I have a dhcp server running. Does OpenStack ask for IPs so? Or does it have its own dhcp server? Or does it just give some IPs during installation?
If I use different networks, do I have to setup one of the servers NIC first? Or will OpenStack use a virtual NIC for that?
I m still confused…
I would be glad to get some more hints.
Best regards
Klaus
Am 12.07.2024 um 17:36 schrieb Guillaume Boutry < guillaume.boutry@canonical.com>:
Hello Klaus,
Glad you're trying out MicroStack.
These questions have more explanations at https://microstack.run/docs/interactive-prompts
But to get you sorted: Management networks shared by hosts The management CIDR is the network your machine(s) have access to. In your case, you have one machine, but you still want to configure it because that's the address that will be used to bind most network services. MetalLB address allocation range (supports multiple ranges, comma separated) It's the addresses used for internal and public services, you should need between 4 and 7 depending on your configuration / plugins enabled. They'll be assigned to services like rabbitmq, ovn-relay, traefik (public, internal, observability, radosgw) and bind, (I might have forgotten some). If you have bootstrapped with --role storage, you'll need at least 5. This can live in your management cidr, allowing other hosts on this network to access services such as Horizon.
You can also have a look at the manifest reference at https://microstack.run/docs/manifest-reference, this will allow you to see all that's available, and to have a deployment without prompts.
To configure the external access to the VMs, you'll be prompted (or not if using manifest) during the configure step:
user: # Local or remote access to VMs # Local mode - single node only # Remote - also available for single node remote_access_location: [local,remote]
external_network: nic: <interface-name> # CIDR of OpenStack external network cidr: <cidr> # IP address of default gateway for external network gateway: <ip-address> # Start of IP allocation range start: <ip-address> # End of IP allocation range end: <ip-address> # Network type for access to external network network_type: [flat,vlan] # VLAN ID if 'vlan' is chosen above segmentation_id: <vlan-id>
Hope this helps!
Guillaume
On Fri, Jul 12, 2024 at 4:50 PM klaus.becker@webmen.de < klaus.becker@webmen.de> wrote:
Dear OpenStackers,
I started my 2nd try installing OpenStack single node guided using this link: https://microstack.run/docs/single-node-guided
At the point sunbeam cluster bootstrap I have to decide network settings:
sudo sunbeam cluster bootstrap Management networks shared by hosts (CIDRs, separated by comma) *(192.168.196.0/24 <http://192.168.196.0/24>)*:
The example given is this:
Management networks shared by hosts (CIDRs, separated by comma) ( 10.20.20.0/24): 172.16.1.0/24 MetalLB address allocation range (supports multiple ranges, comma separated) (10.20.20.10-10.20.20.20): 172.16.1.201-172.16.1.220
Unfortunately there is no information about the LAN the server is running in.
What does "Management networks shared by hosts“ mean? I have ONE host (OpenStack) What should be shared? To whom ? I do not understand the clue behind that.
The MetalLB addresses are for the VMs, right? So they must be in an address range of my LAN
During my first installation (also single node, but not guided) I was not asked for different networks. Finally I was unable to reach Horizon from my LAN. I tried many efforts with routing (nft), but I did not work. Everything seemed live inside my host, but unusable, because I am running Ubuntu Server 24.02 in a Rack using ssh - so: no GUI.
I hoped to get another chance with this „guided" installation.
*What I hoped to get:* 1. A dedicated network inside OpenStack where all components are communicating with each other without interfering with my LAN. 2. Access to the Dashboard (Horizon) from my LAN 3. Access to VMs I am using inside OpenStack from my LAN
Because I am working over ssh, the host uses an IP number from my LAN (192.168.196.11) There are about 20 IPs free in my LAN
The question "Management networks shared by hosts (CIDRs, separated by comma) *(192.168.196.0/24 <http://192.168.196.0/24>)*:“ shows the whole network (/24) as given. I do not want to run into IP conflicts with other PCs, routers etc. in my LAN.
So could someone PLEASE give me a bit more background to this network topic?
Thanx a lot!
Klaus