On 2020/02/21 18:04:01, Marciel Bonamigo <[email protected]>
wrote:
>
>
> On 2020/02/21 14:53:32, Andrija Panic <[email protected]> wrote:
> > Reason is misconfigured SSVM (by ACS) due to some other possible human
> > misconfiguration (usually, can't say your case)
> >
> > 1.Can you ping the actual IP of the Secondary Storage NFS from inside the
> > SSVM?
> > 2. Did you try destroying the SSVM, new one will be created
> >
> >
> > On Fri, 21 Feb 2020 at 13:07, Marciel Bonamigo <
> > [email protected]> wrote:
> >
> > >
> > >
> > > On 2020/02/21 09:07:56, Andrija Panic <[email protected]> wrote:
> > > > Hi,
> > > >
> > > > your NFS server (secondary storate) is reported as 255.255.255.0 - which
> > > is
> > > > obviously wrong, and indicates that SSVM was not correctly configured,
> > > > which is usually due to wrong network configuration.
> > > > Did you "really" follow the guide?
> > > >
> > > > As NFS is not mounted, you can't register new ISO/template or upload
> > > volume.
> > > > Best
> > > >
> > > > On Thu, 20 Feb 2020 at 22:46, Marciel Bonamigo <
> > > > [email protected]> wrote:
> > > >
> > > > >
> > > > >
> > > > > On 2020/02/20 17:37:27, Marciel Bonamigo <
> > > [email protected]>
> > > > > wrote:
> > > > > >
> > > > > >
> > > > > > On 2020/02/19 19:15:01, Andrija Panic <[email protected]>
> > > wrote:
> > > > > > > Hi there,
> > > > > > >
> > > > > > > I don't get what is installed inside what (KVM vs VirtualBox)?
> > > > > > >
> > > > > > > Why don't you take a look into ACS Quick install guide which
> > > requires
> > > > > only
> > > > > > > a single host (your physical KVM host would do fine) -
> > > > > > >
> > > > >
> > > http://docs.cloudstack.apache.org/en/latest/quickinstallationguide/qig.html
> > > > > -
> > > > > > > you can go with ACS 4.13 (this guide is for 4.11) - there are 3
> > > things
> > > > > that
> > > > > > > needs change:
> > > > > > > - do NOT add the mysql repo - but instead install Epel repo which
> > > will
> > > > > > > provide the needed mysql-connector-python (rmost recent versions
> > > of it
> > > > > from
> > > > > > > the MysQL repo are incompatible with ACS)
> > > > > > > - use 4.13 in ACS repo
> > > > > > > - use systemVM template 4.11.3 (instead of 4.11.2) when preseeding
> > > it
> > > > > (just
> > > > > > > replace "4.11.2" with "4.11.3" inside the section
> > > > > > >
> > > > >
> > > http://docs.cloudstack.apache.org/en/latest/quickinstallationguide/qig.html#system-template-setup
> > > > > > > )
> > > > > > >
> > > > > > > Cheers
> > > > > > > Andrija
> > > > > > >
> > > > > > > On Wed, 19 Feb 2020 at 18:01, Marciel Bonamigo <
> > > > > > > [email protected]> wrote:
> > > > > > >
> > > > > > > > Hello, I'm setting up a test lab with ACS 4.13 and KVM at
> > > > > > > > centos7
> > > > > > > >
> > > > > > > > Scenario:
> > > > > > > > -KVM physical server
> > > > > > > > -ACS is in the Virtual Box
> > > > > > > >
> > > > > > > > After all the configurations when starting SSVM it takes a long
> > > time
> > > > > and
> > > > > > > > when I start I can't access them by any IP address, because for
> > > some
> > > > > reason
> > > > > > > > these SSVM are not going out to the internet.
> > > > > > > >
> > > > > > > > KVM Network Settings:
> > > > > > > >
> > > > > > > > cloudbr0:
> > > > > > > > DEVICE = cloudbr0
> > > > > > > > TYPE = Bridge
> > > > > > > > ONBOOT = yes
> > > > > > > > BOOTPROTO = none
> > > > > > > > IPADDR = 172.26.0.222
> > > > > > > > GATEWAY = 172.26.0.1
> > > > > > > > NETMASK = 255.255.255.0
> > > > > > > > USERCTL = no
> > > > > > > >
> > > > > > > > cloudbr1:
> > > > > > > > DEVICE = cloudbr1
> > > > > > > > TYPE = Bridge
> > > > > > > > ONBOOT = yes
> > > > > > > > BOOTPROTO = none
> > > > > > > > IPV6INIT = no
> > > > > > > > IPV6_AUTOCONF = no
> > > > > > > >
> > > > > > > > enp6s0:
> > > > > > > > DEVICE = enp6s0
> > > > > > > > ONBOOT = yes
> > > > > > > > HOTPLUG = no
> > > > > > > > BOOTPROTO = none
> > > > > > > > TYPE = Ethernet
> > > > > > > > BRIDGE = cloudbr0
> > > > > > > >
> > > > > > > > enp6s0.300:
> > > > > > > > DEVICE = enp6s0.300
> > > > > > > > ONBOOT = yes
> > > > > > > > HOTPLUG = no
> > > > > > > > BOOTPROTO = none
> > > > > > > > TYPE = Ethernet
> > > > > > > > VLAN = yes
> > > > > > > > BRIDGE = cloudbr1
> > > > > > > >
> > > > > > > > ACS Network Settings in Virtual BOx:
> > > > > > > > Adapter A connected in Bridge mode, so that it stays on the same
> > > KVM
> > > > > > > > network as on 172.26.0.0/24
> > > > > > > > _____________________________________
> > > > > > > >
> > > > > > > > My question is how to configure the Public network so that SSVM
> > > can
> > > > > start
> > > > > > > > correctly.
> > > > > > > >
> > > > > > > > Anyone who could help I appreciate it.
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > Andrija Panić
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ________________________
> > > > > > Thank you for the informations, Andrija Panić.
> > > > > >
> > > > > > I installed and ACS on the same host as the KVM, I did all the
> > > > > configurations and the SSVM started, connected to them by ssh.
> > > > > >
> > > > > > I am now having trouble adding an iso.
> > > > > > I realized that when I connect to SSVM I am not responding to DNS.
> > > > > >
> > > > > > My resolv.conf is:
> > > > > > nameserver 8.8.8.8
> > > > > > nameserver 1.1.1.1
> > > > > >
> > > > > > Any tips on how to add the ISo?
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Additional information:
> > > > >
> > > > >
> > > > > I would like to know how to configure eth2 that belongs to the public
> > > > > network, that network that is not going out to the internet.
> > > > >
> > > > > root@v-79-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh
> > > > > ================================================
> > > > > First DNS server is 1.1.1.1
> > > > > PING 1.1.1.1 (1.1.1.1): 56 data bytes
> > > > > 64 bytes from 1.1.1.1: icmp_seq=0 ttl=59 time=19.085 ms
> > > > > 64 bytes from 1.1.1.1: icmp_seq=1 ttl=59 time=19.065 ms
> > > > > --- 1.1.1.1 ping statistics ---
> > > > > 2 packets transmitted, 2 packets received, 0% packet loss
> > > > > round-trip min/avg/max/stddev = 19.065/19.075/19.085/0.000 ms
> > > > > Good: Can ping DNS server
> > > > > ================================================
> > > > > Good: DNS resolves cloudstack.apache.org
> > > > > ================================================
> > > > > ERROR: NFS is not currently mounted
> > > > > Try manually mounting from inside the VM
> > > > > NFS server is 255.255.255.0
> > > > > PING 255.255.255.0 (255.255.255.0): 56 data bytes
> > > > > 92 bytes from v-79-VM (172.26.0.169): Destination Host Unreachable
> > > > > 92 bytes from v-79-VM (172.26.0.169): Destination Host Unreachable
> > > > > --- 255.255.255.0 ping statistics ---
> > > > > 2 packets transmitted, 0 packets received, 100% packet loss
> > > > > WARNING: cannot ping nfs server
> > > > > routing table follows
> > > > > Kernel IP routing table
> > > > > Destination Gateway Genmask Flags Metric Ref
> > > > > Use
> > > > > Iface
> > > > > 0.0.0.0 172.26.0.1 0.0.0.0 UG 0 0 > > > > > 0
> > > > > eth2
> > > > > 1.1.1.1 172.26.0.1 255.255.255.255 UGH 0 0 > > > > > 0
> > > > > eth1
> > > > > 8.8.8.8 172.26.0.1 255.255.255.255 UGH 0 0 > > > > > 0
> > > > > eth1
> > > > > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 > > > > > 0
> > > > > eth0
> > > > > 172.26.0.0 0.0.0.0 255.255.255.0 U 0 0 > > > > > 0
> > > > > eth1
> > > > > 172.26.0.0 0.0.0.0 255.255.255.0 U 0 0 > > > > > 0
> > > > > eth2
> > > > > ================================================
> > > > > Management server is 172.26.0.222. Checking connectivity.
> > > > > /usr/local/cloud/systemvm/ssvm-check.sh: line 121: warning: command
> > > > > substitution: ignored null byte in input
> > > > > Good: Can connect to management server port 8250
> > > > > ================================================
> > > > > Good: Java process is running
> > > > > ================================================
> > > > > Tests Complete. Look for ERROR or WARNING above.
> > > > >
> > > > >
> > > >
> > > > --
> > > >
> > > > Andrija Panić
> > > >
> > >
> > >
> > >
> > > Thanks for the feedback.
> > >
> > > As you follow the steps, the panel appears or indicates:
> > >
> > > System-wide capacity
> > > Memory Allocated - Allocated: 1.50 GB / 6.63 GB - 22%
> > > CPU Allocated - Allocated: 1.00 GHz / 12.40 GHz - 8%
> > > Primary Storage Used - Allocated: 4.32 GB / 49.98 GB - 8%
> > > Primary Storage Allocated - Allocated: 0 / 0 - 0%
> > > Public IP Addresses - Allocated: 2 / 11 - 18%
> > > Management IP Addresses - -Allocated: 3 / 55 - 5%
> > > Secondary Storage - Allocated: 4.32 GB / 49.98 GB - 8%
> > > Local Storage - Allocated: 585.68 MB / 99.95 GB - 0%
> > >
> > > This is setting up the secondary storage correctly
> > > df -h
> > > 172.26.0.222:/export/secondary 50G 4,4G 46G 9% /mnt
> > >
> > > I couldn't understand the reason for testing the ping 255.255.255.0
> > >
> > > Secondary storage is ok, because SSVM created
> > >
> > >
> > >
> > >
> >
> > --
> >
> > Andrija Panić
> >
>
>
>
>
> Within the SSVM the ping test responds to the actual NFS IP.
>
> At that time I created a share on another server, also responding.
>
> I'm trying to upload the ISO of my local machine and the error.
>
> My local machine is on the same network.
>
> I tested ping the SSVm addresses
>
> Public IP Address 172.26.0.179
> $ ping 172.26.0.179
> PING 172.26.0.179 (172.26.0.179) 56(84) bytes of data.
>
> Private IP Address 172.26.0.224
> $ ping 172.26.0.224
> PING 172.26.0.224 (172.26.0.224) 56(84) bytes of data.
> 64 bytes from 172.26.0.224: icmp_seq=1 ttl=64 time=0.885 ms
> 64 bytes from 172.26.0.224: icmp_seq=2 ttl=64 time=0.466 ms
>
> Link Local IP Address 169.254.246.63
> $ ping 169.254.246.63
> PING 169.254.246.63 (169.254.246.63) 56(84) bytes of data.
> From 172.26.0.190 icmp_seq=1 Destination Host Unreachable
> From 172.26.0.190 icmp_seq=2 Destination Host Unreachable
> ____________________
>
> My network structure at ACS is:
>
> Management:
> pod-acs413 172.26.0.1 255.255.255.0 vlan://untagged 172.26.0.200
> 172.26.0.254
>
> Public:
> 172.26.0.1 255.255.255.0 vlan://untagged 172.26.0.170
> 172.26.0.180
>
> ACS and KVM on the same server:
> IP Server ACS 172.26.0.222
> IP Server KVM 172.26.0.222
>
> I am suspicious that it must have something to do with the public network.
>
With some adjustments to the global settings at
secstorage.allowed.internal.sites I got access to the internet inside the
Secondary Storage VM and in the ssvm-check.sh test everything was ok.
___________________________________________________________
Now in Console Proxy Vm I do not have access to the internet, is there any
configuration to be done?
Resultado do teste:
root@v-98-VM:/# /usr/local/cloud/systemvm/ssvm-check.sh
================================================
First DNS server is 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=58 time=19.002 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=58 time=19.060 ms
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 19.002/19.031/19.060/0.029 ms
Good: Can ping DNS server
================================================
Good: DNS resolves cloudstack.apache.org
================================================
ERROR: NFS is not currently mounted
Try manually mounting from inside the VM
NFS server is 255.255.255.0
PING 255.255.255.0 (255.255.255.0): 56 data bytes
92 bytes from v-98-VM (172.26.0.180): Destination Host Unreachable
92 bytes from v-98-VM (172.26.0.180): Destination Host Unreachable
--- 255.255.255.0 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
WARNING: cannot ping nfs server
routing table follows
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 172.26.0.1 0.0.0.0 UG 0 0 0 eth2
8.8.4.4 172.26.0.1 255.255.255.255 UGH 0 0 0 eth1
8.8.8.8 172.26.0.1 255.255.255.255 UGH 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
172.26.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
172.26.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
================================================
Management server is 172.26.0.222. Checking connectivity.
/usr/local/cloud/systemvm/ssvm-check.sh: line 121: warning: command
substitution: ignored null byte in input
Good: Can connect to management server port 8250
================================================
Good: Java process is running
================================================
Tests Complete. Look for ERROR or WARNING above.
_________________________________
Logs:
2020-02-28 08:25:57,738 DEBUG [c.c.c.ClusterManagerImpl]
(Cluster-Heartbeat-1:ctx-17a5b15c) (logid:eb0c1e7f) Detected management node
left, id:9, nodeIP:172.26.0.222
2020-02-28 08:25:57,738 INFO [c.c.c.ClusterManagerImpl]
(Cluster-Heartbeat-1:ctx-17a5b15c) (logid:eb0c1e7f) Trying to connect to
172.26.0.222
2020-02-28 08:25:57,738 INFO [c.c.c.ClusterManagerImpl]
(Cluster-Heartbeat-1:ctx-17a5b15c) (logid:eb0c1e7f) Management node 9 is
detected inactive by timestamp but is pingable
2020-02-28 08:25:58,078 DEBUG [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-0cb3f3af) (logid:b6e9f8a1) System vm template is not ready
at data center 1, wait until it is ready to launch console proxy vm
2020-02-28 08:25:58,078 DEBUG [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-0cb3f3af) (logid:b6e9f8a1) Zone 1 is not ready to launch
console proxy yet
2020-02-28 08:25:58,106 DEBUG [o.a.c.s.SecondaryStorageManagerImpl]
(secstorage-1:ctx-4123a496) (logid:ec9ac105) System vm template is not ready at
data center 1, wait until it is ready to launch secondary storage vm
