You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Jimmy Huybrechts <ji...@linservers.com> on 2023/11/01 19:32:50 UTC
System VM network
Hi Team,
I’m trying to built a lab of ACS 4.18 in Ubuntu 22 but I may be looking at the network and system vm’s the wrong way.
I have a /27 my management server host has an IP out of and my KVM host has an IP out of lets call this range 192.168.10.0/27 (in reality this is a public subnet).
Now when creating the zone and pods and such I created a Public range of 10.0.0.0/24 (or at least an internal range).
When asked for the system reserved addresses I filled out 9 ip’s from my management subnet (192.168.10.0/27) under the impression that the console proxy etc would get an IP out of that range.
When the System VM’s were built they yes had an IP from that management range but then as “Private IP”, the “Public IP” was an IP from 10.0.0.0/24 and of course I wasn’t able to use any of them not being reachable from the outside since the gateway and IP where the wrong one.
Should I have set my management range as the public range with the ip’s it should use? And an internal range as system reserved addresses or what are the system reserved addresses for?
--
Jimmy
Re: System VM network
Posted by Jimmy Huybrechts <ji...@linservers.com>.
Hi Wei,
That was it indeed, currently my system vm's are up, and the console proxy works.
--
Jimmy
Van: Wei ZHOU <us...@gmail.com>
Datum: donderdag, 2 november 2023 om 20:03
Aan: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Onderwerp: Re: System VM network
Hi Jimmy,
Can you check the global setting "host"?
-Wei
在 2023年11月2日星期四，Jimmy Huybrechts <ji...@linservers.com> 写道：
> Hi,
>
> I’ve changed it now so that my system-vm gets an internal ip as internal
> and external as external IP.
> But the agent state keeps being unknown, when logged in to one of them I
> think I can see why.
>
> The IP for my management server is also an external one as done when I
> first created the management server for the cluster (I was still under the
> impression the reserved system range needed to be external, see further
> back here).
>
> So currently the management ip on the system vm looks like this:
> 4.4.4.4 via 10.17.1.254 dev eth1
>
> Should the cluster ip also be in the range of the system reserved ip’s? So
> it picks the correct range.
>
> --
> Jimmy
>
> Van: Jithin Raju <ji...@shapeblue.com>
> Datum: donderdag, 2 november 2023 om 11:05
> Aan: users@cloudstack.apache.org <us...@cloudstack.apache.org>
> Onderwerp: Re: System VM network
> Hi Jimmy,
>
> Yes, for example:
>
> CPVM needs to connect to hosts to relay the VM console.
> SSVM would need connectivity to hosts if you are using VMware ESXi for
> Volume Snapshot operations etc.
>
> -Jithin
>
> From: Jimmy Huybrechts <ji...@linservers.com>
> Date: Thursday, 2 November 2023 at 2:18 PM
> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
> Subject: Re: System VM network
> Hi Jithin,
>
> Do the system vm’s actually need to communicate with the hosts?
>
> --
> Jimmy
>
>
>
>
Re: System VM network
Posted by Wei ZHOU <us...@gmail.com>.
Hi Jimmy,
Can you check the global setting "host"?
-Wei
在 2023年11月2日星期四，Jimmy Huybrechts <ji...@linservers.com> 写道：
> Hi,
>
> I’ve changed it now so that my system-vm gets an internal ip as internal
> and external as external IP.
> But the agent state keeps being unknown, when logged in to one of them I
> think I can see why.
>
> The IP for my management server is also an external one as done when I
> first created the management server for the cluster (I was still under the
> impression the reserved system range needed to be external, see further
> back here).
>
> So currently the management ip on the system vm looks like this:
> 4.4.4.4 via 10.17.1.254 dev eth1
>
> Should the cluster ip also be in the range of the system reserved ip’s? So
> it picks the correct range.
>
> --
> Jimmy
>
> Van: Jithin Raju <ji...@shapeblue.com>
> Datum: donderdag, 2 november 2023 om 11:05
> Aan: users@cloudstack.apache.org <us...@cloudstack.apache.org>
> Onderwerp: Re: System VM network
> Hi Jimmy,
>
> Yes, for example:
>
> CPVM needs to connect to hosts to relay the VM console.
> SSVM would need connectivity to hosts if you are using VMware ESXi for
> Volume Snapshot operations etc.
>
> -Jithin
>
> From: Jimmy Huybrechts <ji...@linservers.com>
> Date: Thursday, 2 November 2023 at 2:18 PM
> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
> Subject: Re: System VM network
> Hi Jithin,
>
> Do the system vm’s actually need to communicate with the hosts?
>
> --
> Jimmy
>
>
>
>
Re: System VM network
Posted by Jimmy Huybrechts <ji...@linservers.com>.
Hi,
I’ve changed it now so that my system-vm gets an internal ip as internal and external as external IP.
But the agent state keeps being unknown, when logged in to one of them I think I can see why.
The IP for my management server is also an external one as done when I first created the management server for the cluster (I was still under the impression the reserved system range needed to be external, see further back here).
So currently the management ip on the system vm looks like this:
4.4.4.4 via 10.17.1.254 dev eth1
Should the cluster ip also be in the range of the system reserved ip’s? So it picks the correct range.
--
Jimmy
Van: Jithin Raju <ji...@shapeblue.com>
Datum: donderdag, 2 november 2023 om 11:05
Aan: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Onderwerp: Re: System VM network
Hi Jimmy,
Yes, for example:
CPVM needs to connect to hosts to relay the VM console.
SSVM would need connectivity to hosts if you are using VMware ESXi for Volume Snapshot operations etc.
-Jithin
From: Jimmy Huybrechts <ji...@linservers.com>
Date: Thursday, 2 November 2023 at 2:18 PM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: Re: System VM network
Hi Jithin,
Do the system vm’s actually need to communicate with the hosts?
--
Jimmy
Re: System VM network
Posted by Jithin Raju <ji...@shapeblue.com>.
Hi Jimmy,
Yes, for example:
CPVM needs to connect to hosts to relay the VM console.
SSVM would need connectivity to hosts if you are using VMware ESXi for Volume Snapshot operations etc.
-Jithin
From: Jimmy Huybrechts <ji...@linservers.com>
Date: Thursday, 2 November 2023 at 2:18 PM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: Re: System VM network
Hi Jithin,
Do the system vm’s actually need to communicate with the hosts?
--
Jimmy
Re: System VM network
Posted by Jimmy Huybrechts <ji...@linservers.com>.
Hi Jithin,
Do the system vm’s actually need to communicate with the hosts?
--
Jimmy
Re: System VM network
Posted by Jithin Raju <ji...@shapeblue.com>.
Hi Jimmy,
Typically subnets with RFC1918 IP addresses are used for management/pod/Private networks. The reserved IP address range that you input for a pod will be used for System VMs and Virtual Routers by cloud stack. for We could use IP addresses in the same subnet for the hosts.
-Jithin
From: Jimmy Huybrechts <ji...@linservers.com>
Date: Thursday, 2 November 2023 at 1:17 AM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: Re: System VM network
So I guess yes:
In each zone, you need to configure a range of reserved IP addresses for the management network. This network carries communication between the CloudStack Management Server and various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP.
The reserved IP addresses must be unique across the cloud. You cannot, for example, have a host in one zone which has the same private IP address as a host in another zone.
The hosts in a pod are assigned private IP addresses. These are typically RFC1918 addresses. The Console Proxy and Secondary Storage system VMs are also allocated private IP addresses in the CIDR of the pod that they are created in.
So I guess the system reserved IP’s should indeed be the private ones and not public IP’s, which would lead to my next question I suppose I cannot give this a self-defined VLAN and should be with my management network which is already defined on cloudbr0? Should I give the management and KVM host an IP from this private subnet as well?
--
Jimmy
Van: Jimmy Huybrechts <ji...@linservers.com>
Datum: woensdag, 1 november 2023 om 20:33
Aan: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Onderwerp: System VM network
Hi Team,
I’m trying to built a lab of ACS 4.18 in Ubuntu 22 but I may be looking at the network and system vm’s the wrong way.
I have a /27 my management server host has an IP out of and my KVM host has an IP out of lets call this range 192.168.10.0/27 (in reality this is a public subnet).
Now when creating the zone and pods and such I created a Public range of 10.0.0.0/24 (or at least an internal range).
When asked for the system reserved addresses I filled out 9 ip’s from my management subnet (192.168.10.0/27) under the impression that the console proxy etc would get an IP out of that range.
When the System VM’s were built they yes had an IP from that management range but then as “Private IP”, the “Public IP” was an IP from 10.0.0.0/24 and of course I wasn’t able to use any of them not being reachable from the outside since the gateway and IP where the wrong one.
Should I have set my management range as the public range with the ip’s it should use? And an internal range as system reserved addresses or what are the system reserved addresses for?
--
Jimmy
Re: System VM network
Posted by Jimmy Huybrechts <ji...@linservers.com>.
So I guess yes:
In each zone, you need to configure a range of reserved IP addresses for the management network. This network carries communication between the CloudStack Management Server and various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP.
The reserved IP addresses must be unique across the cloud. You cannot, for example, have a host in one zone which has the same private IP address as a host in another zone.
The hosts in a pod are assigned private IP addresses. These are typically RFC1918 addresses. The Console Proxy and Secondary Storage system VMs are also allocated private IP addresses in the CIDR of the pod that they are created in.
So I guess the system reserved IP’s should indeed be the private ones and not public IP’s, which would lead to my next question I suppose I cannot give this a self-defined VLAN and should be with my management network which is already defined on cloudbr0? Should I give the management and KVM host an IP from this private subnet as well?
--
Jimmy
Van: Jimmy Huybrechts <ji...@linservers.com>
Datum: woensdag, 1 november 2023 om 20:33
Aan: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Onderwerp: System VM network
Hi Team,
I’m trying to built a lab of ACS 4.18 in Ubuntu 22 but I may be looking at the network and system vm’s the wrong way.
I have a /27 my management server host has an IP out of and my KVM host has an IP out of lets call this range 192.168.10.0/27 (in reality this is a public subnet).
Now when creating the zone and pods and such I created a Public range of 10.0.0.0/24 (or at least an internal range).
When asked for the system reserved addresses I filled out 9 ip’s from my management subnet (192.168.10.0/27) under the impression that the console proxy etc would get an IP out of that range.
When the System VM’s were built they yes had an IP from that management range but then as “Private IP”, the “Public IP” was an IP from 10.0.0.0/24 and of course I wasn’t able to use any of them not being reachable from the outside since the gateway and IP where the wrong one.
Should I have set my management range as the public range with the ip’s it should use? And an internal range as system reserved addresses or what are the system reserved addresses for?
--
Jimmy