Re: cloudstack on debian 10/11
ok quick update debian 11.9 as managemnt and host both work on 192.168.xxx.xxx address space as aio, cant seem to connect XCP-NG 8.2.0 though have to debug On Monday 15 April 2024 08:55:34 PM (+07:00), Embedded wrote: > > > > On Monday 15 April 2024 06:33:26 PM (+07:00), Wei ZHOU wrote: > > > Is eth0 added to cloudbr0 bridge ? > > > > further to this once you add the same machine as a host from the gui, you end > up with this, which is curious to me because its using inet > 169.254.0.1/16 scope global cloud0 > on cloud0 and my CentOs template never downloads... so something is off > > > ip a > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group > default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo >valid_lft forever preferred_lft forever > inet6 ::1/128 scope host >valid_lft forever preferred_lft forever > 2: eno1: mtu 1500 qdisc mq master cloudbr0 > state UP group default qlen 1000 > link/ether 84:8f:69:fd:ea:1c brd ff:ff:ff:ff:ff:ff > altname enp2s0f0 > 3: eno2: mtu 1500 qdisc noop state DOWN group default > qlen 1000 > link/ether 84:8f:69:fd:ea:1d brd ff:ff:ff:ff:ff:ff > altname enp2s0f3 > 4: cloudbr0: mtu 1500 qdisc noqueue state > UP group default qlen 1000 > link/ether 4a:d3:e8:49:08:00 brd ff:ff:ff:ff:ff:ff > inet 46.23.82.133/25 brd 46.23.82.255 scope global cloudbr0 >valid_lft forever preferred_lft forever > inet6 fe80::48d3:e8ff:fe49:800/64 scope link >valid_lft forever preferred_lft forever > 5: cloudbr1: mtu 1500 qdisc noqueue state > DOWN group default qlen 1000 > link/ether 3e:63:d5:63:5d:18 brd ff:ff:ff:ff:ff:ff > 6: cloud0: mtu 1500 qdisc noqueue state UP > group default qlen 1000 > link/ether b6:67:93:f4:bd:ad brd ff:ff:ff:ff:ff:ff > inet 169.254.0.1/16 scope global cloud0 >valid_lft forever preferred_lft forever > inet6 fe80::b467:93ff:fef4:bdad/64 scope link >valid_lft forever preferred_lft forever > 7: eno1.500@eno1: mtu 1500 qdisc noqueue > master breno1-500 state UP group default qlen 1000 > link/ether 84:8f:69:fd:ea:1c brd ff:ff:ff:ff:ff:ff > 8: breno1-500: mtu 1500 qdisc noqueue state > UP group default qlen 1000 > link/ether 66:8f:69:eb:49:9e brd ff:ff:ff:ff:ff:ff > 9: vnet0: mtu 1500 qdisc noqueue master > cloud0 state UNKNOWN group default qlen 1000 > link/ether fe:00:a9:fe:7a:64 brd ff:ff:ff:ff:ff:ff > inet6 fe80::fc00:a9ff:fefe:7a64/64 scope link >valid_lft forever preferred_lft forever > 10: vnet1: mtu 1500 qdisc noqueue master > cloudbr0 state UNKNOWN group default qlen 1000 > link/ether fe:00:ae:00:00:66 brd ff:ff:ff:ff:ff:ff > inet6 fe80::fc00:aeff:fe00:66/64 scope link >valid_lft forever preferred_lft forever > 11: vnet2: mtu 1500 qdisc noqueue master > breno1-500 state UNKNOWN group default qlen 1000 > link/ether fe:00:00:00:00:01 brd ff:ff:ff:ff:ff:ff > inet6 fe80::fc00:ff:fe00:1/64 scope link >valid_lft forever preferred_lft forever > 12: vnet3: mtu 1500 qdisc noqueue master > cloud0 state UNKNOWN group default qlen 1000 > link/ether fe:00:a9:fe:c6:3a brd ff:ff:ff:ff:ff:ff > inet6 fe80::fc00:a9ff:fefe:c63a/64 scope link >valid_lft forever preferred_lft forever > 13: vnet4: mtu 1500 qdisc noqueue master > cloudbr0 state UNKNOWN group default qlen 1000 > link/ether fe:00:9b:00:00:6b brd ff:ff:ff:ff:ff:ff > inet6 fe80::fc00:9bff:fe00:6b/64 scope link >valid_lft forever preferred_lft forever > 14: vnet5: mtu 1500 qdisc noqueue master > breno1-500 state UNKNOWN group default qlen 1000 > link/ether fe:00:3e:00:00:02 brd ff:ff:ff:ff:ff:ff > inet6 fe80::fc00:3eff:fe00:2/64 scope link >valid_lft forever preferred_lft forever > root@cs:~# brctl show > bridge name bridge id STP enabled interfaces > breno1-5008000.668f69eb499e no eno1.500 > vnet2 > vnet5 > cloud08000.b66793f4bdad no vnet0 > vnet3 > cloudbr0 8000.4ad3e8490800 no eno1 > vnet1 > vnet4 > cloudbr1 8000.3e63d5635d18 no > > > > -Wei > > > > On Mon, Apr 15, 2024 at 1:14 PM lists wrote: > > > > > > > > > > > > > > > I did in fact get a debian 11 install up and running pretty much as a > > > management server and almost good as a host. Have to figure out why the > > > cloidbr0 is on a 169.xxx adress and why no centos template was > > > downloaded. Systemvms came up without a problem. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Apr 15, 2024
Re: cloudstack on debian 10/11
On Monday 15 April 2024 06:33:26 PM (+07:00), Wei ZHOU wrote: > Is eth0 added to cloudbr0 bridge ? > further to this once you add the same machine as a host from the gui, you end up with this, which is curious to me because its using inet 169.254.0.1/16 scope global cloud0 on cloud0 and my CentOs template never downloads... so something is off ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq master cloudbr0 state UP group default qlen 1000 link/ether 84:8f:69:fd:ea:1c brd ff:ff:ff:ff:ff:ff altname enp2s0f0 3: eno2: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 84:8f:69:fd:ea:1d brd ff:ff:ff:ff:ff:ff altname enp2s0f3 4: cloudbr0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 4a:d3:e8:49:08:00 brd ff:ff:ff:ff:ff:ff inet 46.23.82.133/25 brd 46.23.82.255 scope global cloudbr0 valid_lft forever preferred_lft forever inet6 fe80::48d3:e8ff:fe49:800/64 scope link valid_lft forever preferred_lft forever 5: cloudbr1: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 3e:63:d5:63:5d:18 brd ff:ff:ff:ff:ff:ff 6: cloud0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether b6:67:93:f4:bd:ad brd ff:ff:ff:ff:ff:ff inet 169.254.0.1/16 scope global cloud0 valid_lft forever preferred_lft forever inet6 fe80::b467:93ff:fef4:bdad/64 scope link valid_lft forever preferred_lft forever 7: eno1.500@eno1: mtu 1500 qdisc noqueue master breno1-500 state UP group default qlen 1000 link/ether 84:8f:69:fd:ea:1c brd ff:ff:ff:ff:ff:ff 8: breno1-500: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 66:8f:69:eb:49:9e brd ff:ff:ff:ff:ff:ff 9: vnet0: mtu 1500 qdisc noqueue master cloud0 state UNKNOWN group default qlen 1000 link/ether fe:00:a9:fe:7a:64 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc00:a9ff:fefe:7a64/64 scope link valid_lft forever preferred_lft forever 10: vnet1: mtu 1500 qdisc noqueue master cloudbr0 state UNKNOWN group default qlen 1000 link/ether fe:00:ae:00:00:66 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc00:aeff:fe00:66/64 scope link valid_lft forever preferred_lft forever 11: vnet2: mtu 1500 qdisc noqueue master breno1-500 state UNKNOWN group default qlen 1000 link/ether fe:00:00:00:00:01 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc00:ff:fe00:1/64 scope link valid_lft forever preferred_lft forever 12: vnet3: mtu 1500 qdisc noqueue master cloud0 state UNKNOWN group default qlen 1000 link/ether fe:00:a9:fe:c6:3a brd ff:ff:ff:ff:ff:ff inet6 fe80::fc00:a9ff:fefe:c63a/64 scope link valid_lft forever preferred_lft forever 13: vnet4: mtu 1500 qdisc noqueue master cloudbr0 state UNKNOWN group default qlen 1000 link/ether fe:00:9b:00:00:6b brd ff:ff:ff:ff:ff:ff inet6 fe80::fc00:9bff:fe00:6b/64 scope link valid_lft forever preferred_lft forever 14: vnet5: mtu 1500 qdisc noqueue master breno1-500 state UNKNOWN group default qlen 1000 link/ether fe:00:3e:00:00:02 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc00:3eff:fe00:2/64 scope link valid_lft forever preferred_lft forever root@cs:~# brctl show bridge name bridge id STP enabled interfaces breno1-500 8000.668f69eb499e no eno1.500 vnet2 vnet5 cloud0 8000.b66793f4bdad no vnet0 vnet3 cloudbr08000.4ad3e8490800 no eno1 vnet1 vnet4 cloudbr18000.3e63d5635d18 no > -Wei > > On Mon, Apr 15, 2024 at 1:14 PM lists wrote: > > > > > > > > > > I did in fact get a debian 11 install up and running pretty much as a > > management server and almost good as a host. Have to figure out why the > > cloidbr0 is on a 169.xxx adress and why no centos template was downloaded. > > Systemvms came up without a problem. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Apr 15, 2024 at 3:58 PM, Nuxwrote: > > > > > > > > > Found some notes on Debian here, there could be others.. > > > https://gist.github.com/rohityadavcloud/fc401a0fe8e8ea16b4b3a4e3d149ce0c > > > > > > On 2024-04-15 09:54, Nux wrote: > > > > Not as yet, no formal support for Debian. > > > > That said, this could change in the future.. > > > > If you're a keen Debianista then it might be worth having a go > > > > nevertheless, it might just work or with
Re: cloudstack on debian 10/11
ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc mq master cloudbr0 state UP group default qlen 1000 link/ether 84:8f:69:fd:ea:1c brd ff:ff:ff:ff:ff:ff altname enp2s0f0 3: eno2: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 84:8f:69:fd:ea:1d brd ff:ff:ff:ff:ff:ff altname enp2s0f3 4: cloudbr0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 4a:d3:e8:49:08:00 brd ff:ff:ff:ff:ff:ff inet 46.23.82.133/25 brd 46.23.82.255 scope global cloudbr0 valid_lft forever preferred_lft forever inet6 fe80::48d3:e8ff:fe49:800/64 scope link valid_lft forever preferred_lft forever 5: cloudbr1: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 3e:63:d5:63:5d:18 brd ff:ff:ff:ff:ff:ff dingo@cs:~$ brctl show bridge name bridge id STP enabled interfaces cloudbr08000.4ad3e8490800 no eno1 cloudbr18000.3e63d5635d18 no dingo@cs:~$ cat /etc/network/interfaces source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eno1 auto cloudbr0 iface cloudbr0 inet static bridge_ports eno1 bridge_fd 0 bridge_stp off bridge_maxwait 1 address 46.23.82.133 netmask 255.255.255.128 gateway 46.23.82.129 dns-nameservers 8.8.8.8 8.8.4.4 dns-domain optimcloud.com # guest network auto cloudbr1 iface cloudbr1 inet manual bridge_ports eth0.500 bridge_fd 0 bridge_stp off bridge_maxwait 1 On Monday 15 April 2024 06:33:26 PM (+07:00), Wei ZHOU wrote: > Is eth0 added to cloudbr0 bridge ? > > -Wei > > On Mon, Apr 15, 2024 at 1:14 PM lists wrote: > > > > > > > > > > I did in fact get a debian 11 install up and running pretty much as a > > management server and almost good as a host. Have to figure out why the > > cloidbr0 is on a 169.xxx adress and why no centos template was downloaded. > > Systemvms came up without a problem. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Apr 15, 2024 at 3:58 PM, Nuxwrote: > > > > > > > > > Found some notes on Debian here, there could be others.. > > > https://gist.github.com/rohityadavcloud/fc401a0fe8e8ea16b4b3a4e3d149ce0c > > > > > > On 2024-04-15 09:54, Nux wrote: > > > > Not as yet, no formal support for Debian. > > > > That said, this could change in the future.. > > > > If you're a keen Debianista then it might be worth having a go > > > > nevertheless, it might just work or with minimum changes. > > > > > > > > > > > > On 2024-04-13 10:49, Embedded wrote: > > > >> the install guide states Preferred: CentOS/RHEL 7.2+ or Ubuntu > > > >> 16.04(.2) or higher > > > >> > > > >> > > > >> would this include say debian 10/11 as a manager / and host/kvm > > > >> hypervisor ??? > > > > > > -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com
Re: cloudstack on debian 10/11
Is eth0 added to cloudbr0 bridge ? -Wei On Mon, Apr 15, 2024 at 1:14 PM lists wrote: > > > > > I did in fact get a debian 11 install up and running pretty much as a > management server and almost good as a host. Have to figure out why the > cloidbr0 is on a 169.xxx adress and why no centos template was downloaded. > Systemvms came up without a problem. > > > > > > > > > > > > > > > > > On Apr 15, 2024 at 3:58 PM, Nuxwrote: > > > > > > Found some notes on Debian here, there could be others.. > > https://gist.github.com/rohityadavcloud/fc401a0fe8e8ea16b4b3a4e3d149ce0c > > > > On 2024-04-15 09:54, Nux wrote: > > > Not as yet, no formal support for Debian. > > > That said, this could change in the future.. > > > If you're a keen Debianista then it might be worth having a go > > > nevertheless, it might just work or with minimum changes. > > > > > > > > > On 2024-04-13 10:49, Embedded wrote: > > >> the install guide states Preferred: CentOS/RHEL 7.2+ or Ubuntu > > >> 16.04(.2) or higher > > >> > > >> > > >> would this include say debian 10/11 as a manager / and host/kvm > > >> hypervisor ??? > > >
Re: cloudstack on debian 10/11
I did in fact get a debian 11 install up and running pretty much as a management server and almost good as a host. Have to figure out why the cloidbr0 is on a 169.xxx adress and why no centos template was downloaded. Systemvms came up without a problem. > > On Apr 15, 2024 at 3:58 PM, Nuxwrote: > > > Found some notes on Debian here, there could be others.. > https://gist.github.com/rohityadavcloud/fc401a0fe8e8ea16b4b3a4e3d149ce0c > > On 2024-04-15 09:54, Nux wrote: > > Not as yet, no formal support for Debian. > > That said, this could change in the future.. > > If you're a keen Debianista then it might be worth having a go > > nevertheless, it might just work or with minimum changes. > > > > > > On 2024-04-13 10:49, Embedded wrote: > >> the install guide states Preferred: CentOS/RHEL 7.2+ or Ubuntu > >> 16.04(.2) or higher > >> > >> > >> would this include say debian 10/11 as a manager / and host/kvm > >> hypervisor ??? >
Re: cloudstack on debian 10/11
Found some notes on Debian here, there could be others.. https://gist.github.com/rohityadavcloud/fc401a0fe8e8ea16b4b3a4e3d149ce0c On 2024-04-15 09:54, Nux wrote: Not as yet, no formal support for Debian. That said, this could change in the future.. If you're a keen Debianista then it might be worth having a go nevertheless, it might just work or with minimum changes. On 2024-04-13 10:49, Embedded wrote: the install guide states Preferred: CentOS/RHEL 7.2+ or Ubuntu 16.04(.2) or higher would this include say debian 10/11 as a manager / and host/kvm hypervisor ???
Re: cloudstack on debian 10/11
Not as yet, no formal support for Debian. That said, this could change in the future.. If you're a keen Debianista then it might be worth having a go nevertheless, it might just work or with minimum changes. On 2024-04-13 10:49, Embedded wrote: the install guide states Preferred: CentOS/RHEL 7.2+ or Ubuntu 16.04(.2) or higher would this include say debian 10/11 as a manager / and host/kvm hypervisor ???
cloudstack on debian 10/11
the install guide states Preferred: CentOS/RHEL 7.2+ or Ubuntu 16.04(.2) or higher would this include say debian 10/11 as a manager / and host/kvm hypervisor ??? -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com
