Dear all, I know I did it before.... But for the moment I can't connect to virsh... [root@mercury1 ~]# saslpasswd2 -a libvirt koen Password: Again (for verification): [root@mercury1 ~]# virsh Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # pool-list Please enter your authentication name: koen Please enter your password: error: failed to connect to the hypervisor error: no valid connection error: authentication failed: authentication failed So, i created a new username (I had the same error when I tried to set a password for "admin" user), gave the user a password, but still, I can't connect... What am I missing? We are running on ovirt 4. Hypervisors are running. These are the version of qemu
I wasn't finished... :-) Dear all, I know I did it before.... But for the moment I can't connect to virsh... [root@mercury1 ~]# saslpasswd2 -a libvirt koen Password: Again (for verification): [root@mercury1 ~]# virsh Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # pool-list Please enter your authentication name: koen Please enter your password: error: failed to connect to the hypervisor error: no valid connection error: authentication failed: authentication failed So, i created a new username (I had the same error when I tried to set a password for "admin" user), gave the user a password, but still, I can't connect... What am I missing? We are running on ovirt 4. Hypervisors are running. These are the version of qem: [root@mercury1 ~]# rpm -qa | grep -i qemu qemu-kvm-common-ev-2.3.0-31.el7.16.1.x86_64 qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64 qemu-img-ev-2.3.0-31.el7.16.1.x86_64 qemu-kvm-tools-ev-2.3.0-31.el7.16.1.x86_64 ipxe-roms-qemu-20130517-8.gitc4bce43.el7_2.1.noarch libvirt-daemon-driver-qemu-1.2.17-13.el7_2.5.x86_64 [root@mercury1 ~]# rpm -qa | grep -i libvirt libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-storage-1.2.17-13.el7_2.5.x86_64 libvirt-client-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-kvm-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-1.2.17-13.el7_2.5.x86_64 libvirt-python-1.2.17-2.el7.x86_64 libvirt-lock-sanlock-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-interface-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-qemu-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-network-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-secret-1.2.17-13.el7_2.5.x86_64 Anybody any idea? Thanks in advance. Kind regards, Koen On 2 March 2017 at 07:37, Koen Vanoppen <vanoppen.koen@gmail.com> wrote:
Dear all,
I know I did it before.... But for the moment I can't connect to virsh... [root@mercury1 ~]# saslpasswd2 -a libvirt koen Password: Again (for verification): [root@mercury1 ~]# virsh Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands 'quit' to quit
virsh # pool-list Please enter your authentication name: koen Please enter your password: error: failed to connect to the hypervisor error: no valid connection error: authentication failed: authentication failed
So, i created a new username (I had the same error when I tried to set a password for "admin" user), gave the user a password, but still, I can't connect... What am I missing? We are running on ovirt 4. Hypervisors are running. These are the version of qemu
what about: virsh -r list ps aux | grep libvirt On Thu, Mar 2, 2017 at 7:38 AM, Koen Vanoppen <vanoppen.koen@gmail.com> wrote:
I wasn't finished... :-) Dear all,
I know I did it before.... But for the moment I can't connect to virsh... [root@mercury1 ~]# saslpasswd2 -a libvirt koen Password: Again (for verification): [root@mercury1 ~]# virsh Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands 'quit' to quit
virsh # pool-list Please enter your authentication name: koen Please enter your password: error: failed to connect to the hypervisor error: no valid connection error: authentication failed: authentication failed
So, i created a new username (I had the same error when I tried to set a password for "admin" user), gave the user a password, but still, I can't connect... What am I missing? We are running on ovirt 4. Hypervisors are running. These are the version of qem: [root@mercury1 ~]# rpm -qa | grep -i qemu qemu-kvm-common-ev-2.3.0-31.el7.16.1.x86_64 qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64 qemu-img-ev-2.3.0-31.el7.16.1.x86_64 qemu-kvm-tools-ev-2.3.0-31.el7.16.1.x86_64 ipxe-roms-qemu-20130517-8.gitc4bce43.el7_2.1.noarch libvirt-daemon-driver-qemu-1.2.17-13.el7_2.5.x86_64 [root@mercury1 ~]# rpm -qa | grep -i libvirt libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-storage-1.2.17-13.el7_2.5.x86_64 libvirt-client-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-kvm-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-1.2.17-13.el7_2.5.x86_64 libvirt-python-1.2.17-2.el7.x86_64 libvirt-lock-sanlock-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-interface-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-qemu-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-network-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-secret-1.2.17-13.el7_2.5.x86_64
Anybody any idea?
Thanks in advance.
Kind regards,
Koen
On 2 March 2017 at 07:37, Koen Vanoppen <vanoppen.koen@gmail.com> wrote:
Dear all,
I know I did it before.... But for the moment I can't connect to virsh... [root@mercury1 ~]# saslpasswd2 -a libvirt koen Password: Again (for verification): [root@mercury1 ~]# virsh Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands 'quit' to quit
virsh # pool-list Please enter your authentication name: koen Please enter your password: error: failed to connect to the hypervisor error: no valid connection error: authentication failed: authentication failed
So, i created a new username (I had the same error when I tried to set a password for "admin" user), gave the user a password, but still, I can't connect... What am I missing? We are running on ovirt 4. Hypervisors are running. These are the version of qemu
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
That works... [root@mercury1 ~]# virsh -r list Id Name State ---------------------------------------------------- 3 elear01prod running ... [root@mercury1 ~]# ps aux | grep libvirt root 6137 1.6 0.0 1283180 23636 ? Ssl Feb16 325:14 /usr/sbin/libvirtd --listen root 48600 0.0 0.0 112652 1008 pts/7 S+ 11:37 0:00 grep --color=auto libvirt On 2 March 2017 at 10:00, Arman Khalatyan <arm2arm@gmail.com> wrote:
what about: virsh -r list ps aux | grep libvirt
On Thu, Mar 2, 2017 at 7:38 AM, Koen Vanoppen <vanoppen.koen@gmail.com> wrote:
I wasn't finished... :-) Dear all,
I know I did it before.... But for the moment I can't connect to virsh... [root@mercury1 ~]# saslpasswd2 -a libvirt koen Password: Again (for verification): [root@mercury1 ~]# virsh Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands 'quit' to quit
virsh # pool-list Please enter your authentication name: koen Please enter your password: error: failed to connect to the hypervisor error: no valid connection error: authentication failed: authentication failed
So, i created a new username (I had the same error when I tried to set a password for "admin" user), gave the user a password, but still, I can't connect... What am I missing? We are running on ovirt 4. Hypervisors are running. These are the version of qem: [root@mercury1 ~]# rpm -qa | grep -i qemu qemu-kvm-common-ev-2.3.0-31.el7.16.1.x86_64 qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64 qemu-img-ev-2.3.0-31.el7.16.1.x86_64 qemu-kvm-tools-ev-2.3.0-31.el7.16.1.x86_64 ipxe-roms-qemu-20130517-8.gitc4bce43.el7_2.1.noarch libvirt-daemon-driver-qemu-1.2.17-13.el7_2.5.x86_64 [root@mercury1 ~]# rpm -qa | grep -i libvirt libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-storage-1.2.17-13.el7_2.5.x86_64 libvirt-client-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-kvm-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-1.2.17-13.el7_2.5.x86_64 libvirt-python-1.2.17-2.el7.x86_64 libvirt-lock-sanlock-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-interface-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-qemu-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-network-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-secret-1.2.17-13.el7_2.5.x86_64
Anybody any idea?
Thanks in advance.
Kind regards,
Koen
On 2 March 2017 at 07:37, Koen Vanoppen <vanoppen.koen@gmail.com> wrote:
Dear all,
I know I did it before.... But for the moment I can't connect to virsh... [root@mercury1 ~]# saslpasswd2 -a libvirt koen Password: Again (for verification): [root@mercury1 ~]# virsh Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands 'quit' to quit
virsh # pool-list Please enter your authentication name: koen Please enter your password: error: failed to connect to the hypervisor error: no valid connection error: authentication failed: authentication failed
So, i created a new username (I had the same error when I tried to set a password for "admin" user), gave the user a password, but still, I can't connect... What am I missing? We are running on ovirt 4. Hypervisors are running. These are the version of qemu
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
ok I forgot that if you let vdsmd to manage libvirtd than everything is lockdown to readonly you should try this: 1) saslpasswd2 -a libvirt username 2) then virsh list --all On Thu, Mar 2, 2017 at 11:39 AM, Koen Vanoppen <vanoppen.koen@gmail.com> wrote:
That works...
[root@mercury1 ~]# virsh -r list Id Name State ---------------------------------------------------- 3 elear01prod running ...
[root@mercury1 ~]# ps aux | grep libvirt root 6137 1.6 0.0 1283180 23636 ? Ssl Feb16 325:14 /usr/sbin/libvirtd --listen root 48600 0.0 0.0 112652 1008 pts/7 S+ 11:37 0:00 grep --color=auto libvirt
On 2 March 2017 at 10:00, Arman Khalatyan <arm2arm@gmail.com> wrote:
what about: virsh -r list ps aux | grep libvirt
On Thu, Mar 2, 2017 at 7:38 AM, Koen Vanoppen <vanoppen.koen@gmail.com> wrote:
I wasn't finished... :-) Dear all,
I know I did it before.... But for the moment I can't connect to virsh... [root@mercury1 ~]# saslpasswd2 -a libvirt koen Password: Again (for verification): [root@mercury1 ~]# virsh Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands 'quit' to quit
virsh # pool-list Please enter your authentication name: koen Please enter your password: error: failed to connect to the hypervisor error: no valid connection error: authentication failed: authentication failed
So, i created a new username (I had the same error when I tried to set a password for "admin" user), gave the user a password, but still, I can't connect... What am I missing? We are running on ovirt 4. Hypervisors are running. These are the version of qem: [root@mercury1 ~]# rpm -qa | grep -i qemu qemu-kvm-common-ev-2.3.0-31.el7.16.1.x86_64 qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64 qemu-img-ev-2.3.0-31.el7.16.1.x86_64 qemu-kvm-tools-ev-2.3.0-31.el7.16.1.x86_64 ipxe-roms-qemu-20130517-8.gitc4bce43.el7_2.1.noarch libvirt-daemon-driver-qemu-1.2.17-13.el7_2.5.x86_64 [root@mercury1 ~]# rpm -qa | grep -i libvirt libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-storage-1.2.17-13.el7_2.5.x86_64 libvirt-client-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-kvm-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-1.2.17-13.el7_2.5.x86_64 libvirt-python-1.2.17-2.el7.x86_64 libvirt-lock-sanlock-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-interface-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-qemu-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-network-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-secret-1.2.17-13.el7_2.5.x86_64
Anybody any idea?
Thanks in advance.
Kind regards,
Koen
On 2 March 2017 at 07:37, Koen Vanoppen <vanoppen.koen@gmail.com> wrote:
Dear all,
I know I did it before.... But for the moment I can't connect to virsh... [root@mercury1 ~]# saslpasswd2 -a libvirt koen Password: Again (for verification): [root@mercury1 ~]# virsh Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands 'quit' to quit
virsh # pool-list Please enter your authentication name: koen Please enter your password: error: failed to connect to the hypervisor error: no valid connection error: authentication failed: authentication failed
So, i created a new username (I had the same error when I tried to set a password for "admin" user), gave the user a password, but still, I can't connect... What am I missing? We are running on ovirt 4. Hypervisors are running. These are the version of qemu
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[root@mercury1 ~]# saslpasswd2 -a libvirt koen Password: Again (for verification): [root@mercury1 ~]# virsh list --all Please enter your authentication name: koen Please enter your password: error: failed to connect to the hypervisor error: no valid connection error: authentication failed: authentication failed On 2 March 2017 at 11:55, Arman Khalatyan <arm2arm@gmail.com> wrote:
ok I forgot that if you let vdsmd to manage libvirtd than everything is lockdown to readonly you should try this: 1) saslpasswd2 -a libvirt username 2) then virsh list --all
On Thu, Mar 2, 2017 at 11:39 AM, Koen Vanoppen <vanoppen.koen@gmail.com> wrote:
That works...
[root@mercury1 ~]# virsh -r list Id Name State ---------------------------------------------------- 3 elear01prod running ...
[root@mercury1 ~]# ps aux | grep libvirt root 6137 1.6 0.0 1283180 23636 ? Ssl Feb16 325:14 /usr/sbin/libvirtd --listen root 48600 0.0 0.0 112652 1008 pts/7 S+ 11:37 0:00 grep --color=auto libvirt
On 2 March 2017 at 10:00, Arman Khalatyan <arm2arm@gmail.com> wrote:
what about: virsh -r list ps aux | grep libvirt
On Thu, Mar 2, 2017 at 7:38 AM, Koen Vanoppen <vanoppen.koen@gmail.com> wrote:
I wasn't finished... :-) Dear all,
I know I did it before.... But for the moment I can't connect to virsh... [root@mercury1 ~]# saslpasswd2 -a libvirt koen Password: Again (for verification): [root@mercury1 ~]# virsh Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands 'quit' to quit
virsh # pool-list Please enter your authentication name: koen Please enter your password: error: failed to connect to the hypervisor error: no valid connection error: authentication failed: authentication failed
So, i created a new username (I had the same error when I tried to set a password for "admin" user), gave the user a password, but still, I can't connect... What am I missing? We are running on ovirt 4. Hypervisors are running. These are the version of qem: [root@mercury1 ~]# rpm -qa | grep -i qemu qemu-kvm-common-ev-2.3.0-31.el7.16.1.x86_64 qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64 qemu-img-ev-2.3.0-31.el7.16.1.x86_64 qemu-kvm-tools-ev-2.3.0-31.el7.16.1.x86_64 ipxe-roms-qemu-20130517-8.gitc4bce43.el7_2.1.noarch libvirt-daemon-driver-qemu-1.2.17-13.el7_2.5.x86_64 [root@mercury1 ~]# rpm -qa | grep -i libvirt libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-storage-1.2.17-13.el7_2.5.x86_64 libvirt-client-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-kvm-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-1.2.17-13.el7_2.5.x86_64 libvirt-python-1.2.17-2.el7.x86_64 libvirt-lock-sanlock-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-interface-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-qemu-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-network-1.2.17-13.el7_2.5.x86_64 libvirt-daemon-driver-secret-1.2.17-13.el7_2.5.x86_64
Anybody any idea?
Thanks in advance.
Kind regards,
Koen
On 2 March 2017 at 07:37, Koen Vanoppen <vanoppen.koen@gmail.com> wrote:
Dear all,
I know I did it before.... But for the moment I can't connect to virsh... [root@mercury1 ~]# saslpasswd2 -a libvirt koen Password: Again (for verification): [root@mercury1 ~]# virsh Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands 'quit' to quit
virsh # pool-list Please enter your authentication name: koen Please enter your password: error: failed to connect to the hypervisor error: no valid connection error: authentication failed: authentication failed
So, i created a new username (I had the same error when I tried to set a password for "admin" user), gave the user a password, but still, I can't connect... What am I missing? We are running on ovirt 4. Hypervisors are running. These are the version of qemu
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Thu, Mar 2, 2017 at 12:49 PM, Koen Vanoppen <vanoppen.koen@gmail.com> wrote:
[root@mercury1 ~]# saslpasswd2 -a libvirt koen Password: Again (for verification): [root@mercury1 ~]# virsh list --all Please enter your authentication name: koen Please enter your password: error: failed to connect to the hypervisor error: no valid connection error: authentication failed: authentication failed
I can only say that I just tested on my environment, with plain CentOS 7.3 in oVirt 4.1 and it works. In theory, your connection string should use unix domain sockets if I'm not wrong and should be the same as "-c qemu:///system" In fact, using that connection URI I get the same prompts as without anything (only thing I just get the login/pwd prompt before running any command). Possibly there is something SELinux related? Is it enabled? Strange enough I'm verifying in my 4.1 system that I can actually run this command below without any password..... (obviously all the caveat of running it out of oVirt are applicable...) [root@ovmsrv05 ~]# virsh -c qemu://ovmsrv05.mydomain/system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # list Id Name State ---------------------------------------------------- 2 raclab1 running 10 c7testovn1 running virsh # This happens using the hostname used for the host when added to oVirt infra Instead if I use localhost I get [root@ovmsrv05 ~]# virsh -c qemu://localhost/system 2017-03-02 13:58:16.190+0000: 25221: info : libvirt version: 2.0.0, package: 10.el7_3.4 (CentOS BuildSystem <http://bugs.centos.org>, 2017-01-17-23:37:48, c1bm.rdu2.centos.org) 2017-03-02 13:58:16.190+0000: 25221: info : hostname: ovmsrv05.mydomain 2017-03-02 13:58:16.190+0000: 25221: warning : virNetTLSContextCheckCertificate:1125 : Certificate check failed Certificate [session] owner does not match the hostname localhost error: failed to connect to the hypervisor error: authentication failed: Failed to verify peer's certificate [root@ovmsrv05 ~]# Does this command work for you too in 4.0? Is it in general a bug or a feature? Or anything cached (I don't think so because I can execute the same on another host where I didn't run anything before and where I didn't use the saslpasswd2 command to add a local virsh user)? Gianluca
On Thu, Mar 2, 2017 at 3:10 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Thu, Mar 2, 2017 at 12:49 PM, Koen Vanoppen <vanoppen.koen@gmail.com> wrote:
[root@mercury1 ~]# saslpasswd2 -a libvirt koen Password: Again (for verification): [root@mercury1 ~]# virsh list --all Please enter your authentication name: koen Please enter your password: error: failed to connect to the hypervisor error: no valid connection error: authentication failed: authentication failed
I can only say that I just tested on my environment, with plain CentOS 7.3 in oVirt 4.1 and it works.
In theory, your connection string should use unix domain sockets if I'm not wrong and should be the same as "-c qemu:///system" In fact, using that connection URI I get the same prompts as without anything (only thing I just get the login/pwd prompt before running any command).
Possibly there is something SELinux related? Is it enabled?
Strange enough I'm verifying in my 4.1 system that I can actually run this command below without any password..... (obviously all the caveat of running it out of oVirt are applicable...)
[root@ovmsrv05 ~]# virsh -c qemu://ovmsrv05.mydomain/system Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands 'quit' to quit
virsh # list Id Name State ---------------------------------------------------- 2 raclab1 running 10 c7testovn1 running
virsh #
This happens using the hostname used for the host when added to oVirt infra Instead if I use localhost I get
[root@ovmsrv05 ~]# virsh -c qemu://localhost/system 2017-03-02 13:58:16.190+0000: 25221: info : libvirt version: 2.0.0, package: 10.el7_3.4 (CentOS BuildSystem <http://bugs.centos.org>, 2017-01-17-23:37:48, c1bm.rdu2.centos.org) 2017-03-02 13:58:16.190+0000: 25221: info : hostname: ovmsrv05.mydomain 2017-03-02 13:58:16.190+0000: 25221: warning : virNetTLSContextCheckCertificate:1125 : Certificate check failed Certificate [session] owner does not match the hostname localhost error: failed to connect to the hypervisor error: authentication failed: Failed to verify peer's certificate [root@ovmsrv05 ~]#
Does this command work for you too in 4.0? Is it in general a bug or a feature? Or anything cached (I don't think so because I can execute the same on another host where I didn't run anything before and where I didn't use the saslpasswd2 command to add a local virsh user)?
It's a feature: we configure it for TLS/x509 authentication for the engine over TCP and SASL authentication for the local access overt the unix domain socket.
Gianluca
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (4)
-
Arman Khalatyan -
Gianluca Cecchi -
Koen Vanoppen -
Simone Tiraboschi