Hi,
I am facing the issue while porting Host's "adb-devices" to lava-dispatcher docker.
Please can some one provide the right steps to detect "adb-devices" in "lava-dispatcher" docker?
Current steps: (still my lava-dispatcher fail to detect the Host's "adb-devices") ########### 1. Lauch the LAVA-lab using "docker-compose up" from the repo " https://github.com/danrue/lava-docker-compose.git" 2. add "/dev/bus/usb" , "/etc/udev/rules.d" and "privileged: True" to "lava-dispatcher" i.e " dispatcher: image: lavasoftware/lava-dispatcher:2019.12 container_name: lava_dispatcher privileged: True devices: - /dev/kvm # needed for QEMU - /dev/net/tun # needed for QEMU - /dev/bus/usb cap_add: - NET_ADMIN # needed for QEMU environment: - "DISPATCHER_HOSTNAME=--hostname=dispatcher" - "LOGGER_URL=tcp://server:5555" # url to send logs - "MASTER_URL=tcp://server:5556" # url of lava master volumes: - '/boot:/boot:ro' - '/lib/modules:/lib/modules:ro' - '/dev/bus/usb:/dev/bus/usb' - '/etc/udev/rules.d:/etc/udev/rules.d'" 3. Run the command #docker-compose up 4. Login to lava-dispatcher #docker exec -it <dispatcher-name" bash #apt-get update;apt-get install android-tools-adb android-tools-fastboot usbutils #adb devices
Can some one let me know the steps to detect my host's "adb-devices" in lava-dispatcher's docker?
Regards, Koti
On Tue, 31 Mar 2020 at 09:36, koti koti kotisoftwaretest@gmail.com wrote:
Hi,
I am facing the issue while porting Host's "adb-devices" to lava-dispatcher docker.
Please can some one provide the right steps to detect "adb-devices" in "lava-dispatcher" docker?
Current steps: (still my lava-dispatcher fail to detect the Host's "adb-devices") ###########
- Lauch the LAVA-lab using "docker-compose up" from the repo "https://github.com/danrue/lava-docker-compose.git"
- add "/dev/bus/usb" , "/etc/udev/rules.d" and "privileged: True" to "lava-dispatcher" i.e
you don't need privileged container. It beats the purpose of containerizing the dispatcher.
" dispatcher: image: lavasoftware/lava-dispatcher:2019.12 container_name: lava_dispatcher privileged: True devices: - /dev/kvm # needed for QEMU - /dev/net/tun # needed for QEMU - /dev/bus/usb cap_add: - NET_ADMIN # needed for QEMU environment: - "DISPATCHER_HOSTNAME=--hostname=dispatcher" - "LOGGER_URL=tcp://server:5555" # url to send logs - "MASTER_URL=tcp://server:5556" # url of lava master volumes: - '/boot:/boot:ro' - '/lib/modules:/lib/modules:ro' - '/dev/bus/usb:/dev/bus/usb' - '/etc/udev/rules.d:/etc/udev/rules.d'" 3. Run the command #docker-compose up 4. Login to lava-dispatcher #docker exec -it <dispatcher-name" bash #apt-get update;apt-get install android-tools-adb android-tools-fastboot usbutils #adb devices
Can some one let me know the steps to detect my host's "adb-devices" in lava-dispatcher's docker?
you need to pass the devices to the container as they show up on USB bus. lava-dispatcher-host package takes care of that.
milosz
Regards, Koti _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Thanks Milosz.
Your comment in previous email : "you need to pass the devices to the container as they show up on USB bus"
Currently I am facing the issue while implement your comments in my docker-cmopose.yaml . Can you let me know how can I pass the devices to the container through docker-conmpose.yaml file i.e https://github.com/danrue/lava-docker-compose/blob/master/docker-compose.yml ?
Regards, Koti
On Tue, 31 Mar 2020 at 14:41, Milosz Wasilewski < milosz.wasilewski@linaro.org> wrote:
On Tue, 31 Mar 2020 at 09:36, koti koti kotisoftwaretest@gmail.com wrote:
Hi,
I am facing the issue while porting Host's "adb-devices" to
lava-dispatcher docker.
Please can some one provide the right steps to detect "adb-devices" in
"lava-dispatcher" docker?
Current steps: (still my lava-dispatcher fail to detect the Host's
"adb-devices")
###########
- Lauch the LAVA-lab using "docker-compose up" from the repo "
https://github.com/danrue/lava-docker-compose.git"
- add "/dev/bus/usb" , "/etc/udev/rules.d" and "privileged: True"
to "lava-dispatcher" i.e
you don't need privileged container. It beats the purpose of containerizing the dispatcher.
" dispatcher: image: lavasoftware/lava-dispatcher:2019.12 container_name: lava_dispatcher privileged: True devices: - /dev/kvm # needed for QEMU - /dev/net/tun # needed for QEMU - /dev/bus/usb cap_add: - NET_ADMIN # needed for QEMU environment: - "DISPATCHER_HOSTNAME=--hostname=dispatcher" - "LOGGER_URL=tcp://server:5555" # url to send logs - "MASTER_URL=tcp://server:5556" # url of lava master volumes: - '/boot:/boot:ro' - '/lib/modules:/lib/modules:ro' - '/dev/bus/usb:/dev/bus/usb' - '/etc/udev/rules.d:/etc/udev/rules.d'" 3. Run the command #docker-compose up 4. Login to lava-dispatcher #docker exec -it <dispatcher-name" bash #apt-get update;apt-get install android-tools-adb
android-tools-fastboot usbutils
#adb devicesCan some one let me know the steps to detect my host's "adb-devices" in
lava-dispatcher's docker?
you need to pass the devices to the container as they show up on USB bus. lava-dispatcher-host package takes care of that.
milosz
Regards, Koti _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
On Tue, 31 Mar 2020 at 13:19, koti koti kotisoftwaretest@gmail.com wrote:
Thanks Milosz.
Your comment in previous email : "you need to pass the devices to the container as they show up on USB bus"
Currently I am facing the issue while implement your comments in my docker-cmopose.yaml . Can you let me know how can I pass the devices to the container through docker-conmpose.yaml file i.e https://github.com/danrue/lava-docker-compose/blob/master/docker-compose.yml ?
You didn't read till the end: "lava-dispatcher-host package takes care of that." You need to install lava-dispatcher-host package or build it from sources if you're not on debian.
milosz
Regards, Koti
On Tue, 31 Mar 2020 at 14:41, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On Tue, 31 Mar 2020 at 09:36, koti koti kotisoftwaretest@gmail.com wrote:
Hi,
I am facing the issue while porting Host's "adb-devices" to lava-dispatcher docker.
Please can some one provide the right steps to detect "adb-devices" in "lava-dispatcher" docker?
Current steps: (still my lava-dispatcher fail to detect the Host's "adb-devices") ###########
- Lauch the LAVA-lab using "docker-compose up" from the repo "https://github.com/danrue/lava-docker-compose.git"
- add "/dev/bus/usb" , "/etc/udev/rules.d" and "privileged: True" to "lava-dispatcher" i.e
you don't need privileged container. It beats the purpose of containerizing the dispatcher.
" dispatcher: image: lavasoftware/lava-dispatcher:2019.12 container_name: lava_dispatcher privileged: True devices: - /dev/kvm # needed for QEMU - /dev/net/tun # needed for QEMU - /dev/bus/usb cap_add: - NET_ADMIN # needed for QEMU environment: - "DISPATCHER_HOSTNAME=--hostname=dispatcher" - "LOGGER_URL=tcp://server:5555" # url to send logs - "MASTER_URL=tcp://server:5556" # url of lava master volumes: - '/boot:/boot:ro' - '/lib/modules:/lib/modules:ro' - '/dev/bus/usb:/dev/bus/usb' - '/etc/udev/rules.d:/etc/udev/rules.d'" 3. Run the command #docker-compose up 4. Login to lava-dispatcher #docker exec -it <dispatcher-name" bash #apt-get update;apt-get install android-tools-adb android-tools-fastboot usbutils #adb devices
Can some one let me know the steps to detect my host's "adb-devices" in lava-dispatcher's docker?
you need to pass the devices to the container as they show up on USB bus. lava-dispatcher-host package takes care of that.
milosz
Regards, Koti _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Thanks Milosz.
I have not find the lava-dispatcher-package in below lists. Please can you let me know the download URL for "lava-dispatcher-host" package
1. https://packages.debian.org/stable/allpackages 2.https://packages.debian.org/testing/allpackages 3.https://packages.debian.org/unstable/allpackages
You can find my docker details as mentioned below.
" root@2292fa2d595a:/# uname -a Linux 2292fa2d595a 4.15.0-88-generic #88~16.04.1-Ubuntu SMP Wed Feb 12 04:19:15 UTC 2020 x86_64 GNU/Linux
root@2292fa2d595a:/# apt-get install lava-dispatcher Reading package lists... Done Building dependency tree Reading state information... Done lava-dispatcher is already the newest version (2019.12+10+buster). 0 upgraded, 0 newly installed, 0 to remove and 45 not upgraded. root@2292fa2d595a:/# root@2292fa2d595a:/#
root@2292fa2d595a:/# apt-get install lava-dispatcher-host Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package lava-dispatcher-host
"
Regards, Koti
On Tue, 31 Mar 2020 at 18:13, Milosz Wasilewski < milosz.wasilewski@linaro.org> wrote:
On Tue, 31 Mar 2020 at 13:19, koti koti kotisoftwaretest@gmail.com wrote:
Thanks Milosz.
Your comment in previous email : "you need to pass the devices to the
container as they show up on USB bus"
Currently I am facing the issue while implement your comments in my
docker-cmopose.yaml . Can you let me know how can I pass the devices to the container through docker-conmpose.yaml file i.e https://github.com/danrue/lava-docker-compose/blob/master/docker-compose.yml ?
You didn't read till the end: "lava-dispatcher-host package takes care of that." You need to install lava-dispatcher-host package or build it from sources if you're not on debian.
milosz
Regards, Koti
On Tue, 31 Mar 2020 at 14:41, Milosz Wasilewski <
milosz.wasilewski@linaro.org> wrote:
On Tue, 31 Mar 2020 at 09:36, koti koti kotisoftwaretest@gmail.com
wrote:
Hi,
I am facing the issue while porting Host's "adb-devices" to
lava-dispatcher docker.
Please can some one provide the right steps to detect "adb-devices"
in "lava-dispatcher" docker?
Current steps: (still my lava-dispatcher fail to detect the Host's
"adb-devices")
###########
- Lauch the LAVA-lab using "docker-compose up" from the repo "
https://github.com/danrue/lava-docker-compose.git"
- add "/dev/bus/usb" , "/etc/udev/rules.d" and "privileged:
True" to "lava-dispatcher" i.e
you don't need privileged container. It beats the purpose of containerizing the dispatcher.
" dispatcher: image: lavasoftware/lava-dispatcher:2019.12 container_name: lava_dispatcher privileged: True devices: - /dev/kvm # needed for QEMU - /dev/net/tun # needed for QEMU - /dev/bus/usb cap_add: - NET_ADMIN # needed for QEMU environment: - "DISPATCHER_HOSTNAME=--hostname=dispatcher" - "LOGGER_URL=tcp://server:5555" # url to send logs - "MASTER_URL=tcp://server:5556" # url of lava master volumes: - '/boot:/boot:ro' - '/lib/modules:/lib/modules:ro' - '/dev/bus/usb:/dev/bus/usb' - '/etc/udev/rules.d:/etc/udev/rules.d'" 3. Run the command #docker-compose up 4. Login to lava-dispatcher #docker exec -it <dispatcher-name" bash #apt-get update;apt-get install android-tools-adb
android-tools-fastboot usbutils
#adb devicesCan some one let me know the steps to detect my host's "adb-devices"
in lava-dispatcher's docker?
you need to pass the devices to the container as they show up on USB bus. lava-dispatcher-host package takes care of that.
milosz
Regards, Koti _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
On Tue, 31 Mar 2020 at 13:59, koti koti kotisoftwaretest@gmail.com wrote:
Thanks Milosz.
I have not find the lava-dispatcher-package in below lists. Please can you let me know the download URL for "lava-dispatcher-host" package
2.https://packages.debian.org/testing/allpackages 3.https://packages.debian.org/unstable/allpackages
You can find my docker details as mentioned below.
Try: http://apt.lavasoftware.org/
@Antonio Terceiro could you upload lava-dispatcher-host to debian?
milosz
" root@2292fa2d595a:/# uname -a Linux 2292fa2d595a 4.15.0-88-generic #88~16.04.1-Ubuntu SMP Wed Feb 12 04:19:15 UTC 2020 x86_64 GNU/Linux
root@2292fa2d595a:/# apt-get install lava-dispatcher Reading package lists... Done Building dependency tree Reading state information... Done lava-dispatcher is already the newest version (2019.12+10+buster). 0 upgraded, 0 newly installed, 0 to remove and 45 not upgraded. root@2292fa2d595a:/# root@2292fa2d595a:/#
root@2292fa2d595a:/# apt-get install lava-dispatcher-host Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package lava-dispatcher-host
"
Regards, Koti
On Tue, 31 Mar 2020 at 18:13, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On Tue, 31 Mar 2020 at 13:19, koti koti kotisoftwaretest@gmail.com wrote:
Thanks Milosz.
Your comment in previous email : "you need to pass the devices to the container as they show up on USB bus"
Currently I am facing the issue while implement your comments in my docker-cmopose.yaml . Can you let me know how can I pass the devices to the container through docker-conmpose.yaml file i.e https://github.com/danrue/lava-docker-compose/blob/master/docker-compose.yml ?
You didn't read till the end: "lava-dispatcher-host package takes care of that." You need to install lava-dispatcher-host package or build it from sources if you're not on debian.
milosz
Regards, Koti
On Tue, 31 Mar 2020 at 14:41, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On Tue, 31 Mar 2020 at 09:36, koti koti kotisoftwaretest@gmail.com wrote:
Hi,
I am facing the issue while porting Host's "adb-devices" to lava-dispatcher docker.
Please can some one provide the right steps to detect "adb-devices" in "lava-dispatcher" docker?
Current steps: (still my lava-dispatcher fail to detect the Host's "adb-devices") ###########
- Lauch the LAVA-lab using "docker-compose up" from the repo "https://github.com/danrue/lava-docker-compose.git"
- add "/dev/bus/usb" , "/etc/udev/rules.d" and "privileged: True" to "lava-dispatcher" i.e
you don't need privileged container. It beats the purpose of containerizing the dispatcher.
" dispatcher: image: lavasoftware/lava-dispatcher:2019.12 container_name: lava_dispatcher privileged: True devices: - /dev/kvm # needed for QEMU - /dev/net/tun # needed for QEMU - /dev/bus/usb cap_add: - NET_ADMIN # needed for QEMU environment: - "DISPATCHER_HOSTNAME=--hostname=dispatcher" - "LOGGER_URL=tcp://server:5555" # url to send logs - "MASTER_URL=tcp://server:5556" # url of lava master volumes: - '/boot:/boot:ro' - '/lib/modules:/lib/modules:ro' - '/dev/bus/usb:/dev/bus/usb' - '/etc/udev/rules.d:/etc/udev/rules.d'" 3. Run the command #docker-compose up 4. Login to lava-dispatcher #docker exec -it <dispatcher-name" bash #apt-get update;apt-get install android-tools-adb android-tools-fastboot usbutils #adb devices
Can some one let me know the steps to detect my host's "adb-devices" in lava-dispatcher's docker?
you need to pass the devices to the container as they show up on USB bus. lava-dispatcher-host package takes care of that.
milosz
Regards, Koti _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Thanks Milosz.
Still "adb devices" does list the devices in the docker even those were listed in host machine.
" root@0feacfced787:/opt# dpkg -i lava-common_2020.02.0143.gd20f3bc24+10+buster_all.deb (Reading database ... 24077 files and directories currently installed.) Preparing to unpack lava-common_2020.02.0143.gd20f3bc24+10+buster_all.deb ... Unpacking lava-common (2020.02.0143.gd20f3bc24+10+buster) over (2020.02.0143.gd20f3bc24+10+buster) ... Setting up lava-common (2020.02.0143.gd20f3bc24+10+buster) ...
root@0feacfced787:/opt# dpkg -i lava-dispatcher-host_2020.02.0143.gd20f3bc24+10+buster_all.deb (Reading database ... 24077 files and directories currently installed.) Preparing to unpack lava-dispatcher-host_2020.02.0143.gd20f3bc24+10+buster_all.deb ... Unpacking lava-dispatcher-host (2020.02.0143.gd20f3bc24+10+buster) over (2020.02.0143.gd20f3bc24+10+buster) ... Setting up lava-dispatcher-host (2020.02.0143.gd20f3bc24+10+buster) ...
root@0feacfced787:/opt# /etc/init.d/udev restart [ ok ] Stopping hotplug events dispatcher: systemd-udevd. [ ok ] Starting hotplug events dispatcher: systemd-udevd.
root@0feacfced787:/opt# adb devices List of devices attached
root@0feacfced787:/opt#
Regards, Koti On Tue, 31 Mar 2020 at 18:32, Milosz Wasilewski < milosz.wasilewski@linaro.org> wrote:
On Tue, 31 Mar 2020 at 13:59, koti koti kotisoftwaretest@gmail.com wrote:
Thanks Milosz.
I have not find the lava-dispatcher-package in below lists. Please can
you let me know the download URL for "lava-dispatcher-host" package
2.https://packages.debian.org/testing/allpackages 3.https://packages.debian.org/unstable/allpackages
You can find my docker details as mentioned below.
Try: http://apt.lavasoftware.org/
@Antonio Terceiro could you upload lava-dispatcher-host to debian?
milosz
" root@2292fa2d595a:/# uname -a Linux 2292fa2d595a 4.15.0-88-generic #88~16.04.1-Ubuntu SMP Wed Feb 12
04:19:15 UTC 2020 x86_64 GNU/Linux
root@2292fa2d595a:/# apt-get install lava-dispatcher Reading package lists... Done Building dependency tree Reading state information... Done lava-dispatcher is already the newest version (2019.12+10+buster). 0 upgraded, 0 newly installed, 0 to remove and 45 not upgraded. root@2292fa2d595a:/# root@2292fa2d595a:/#
root@2292fa2d595a:/# apt-get install lava-dispatcher-host Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package lava-dispatcher-host
"
Regards, Koti
On Tue, 31 Mar 2020 at 18:13, Milosz Wasilewski <
milosz.wasilewski@linaro.org> wrote:
On Tue, 31 Mar 2020 at 13:19, koti koti kotisoftwaretest@gmail.com
wrote:
Thanks Milosz.
Your comment in previous email : "you need to pass the devices to
the container as they show up on USB bus"
Currently I am facing the issue while implement your comments in my
docker-cmopose.yaml . Can you let me know how can I pass the devices to the container through docker-conmpose.yaml file i.e https://github.com/danrue/lava-docker-compose/blob/master/docker-compose.yml ?
You didn't read till the end: "lava-dispatcher-host package takes care of that." You need to install lava-dispatcher-host package or build it from sources if you're not on debian.
milosz
Regards, Koti
On Tue, 31 Mar 2020 at 14:41, Milosz Wasilewski <
milosz.wasilewski@linaro.org> wrote:
On Tue, 31 Mar 2020 at 09:36, koti koti kotisoftwaretest@gmail.com
wrote:
Hi,
I am facing the issue while porting Host's "adb-devices" to
lava-dispatcher docker.
Please can some one provide the right steps to detect
"adb-devices" in "lava-dispatcher" docker?
Current steps: (still my lava-dispatcher fail to detect the
Host's "adb-devices")
###########
- Lauch the LAVA-lab using "docker-compose up" from the repo "
https://github.com/danrue/lava-docker-compose.git"
- add "/dev/bus/usb" , "/etc/udev/rules.d" and "privileged:
True" to "lava-dispatcher" i.e
you don't need privileged container. It beats the purpose of containerizing the dispatcher.
" dispatcher: image: lavasoftware/lava-dispatcher:2019.12 container_name: lava_dispatcher privileged: True devices: - /dev/kvm # needed for QEMU - /dev/net/tun # needed for QEMU - /dev/bus/usb cap_add: - NET_ADMIN # needed for QEMU environment: - "DISPATCHER_HOSTNAME=--hostname=dispatcher" - "LOGGER_URL=tcp://server:5555" # url to send logs - "MASTER_URL=tcp://server:5556" # url of lava master volumes: - '/boot:/boot:ro' - '/lib/modules:/lib/modules:ro' - '/dev/bus/usb:/dev/bus/usb' - '/etc/udev/rules.d:/etc/udev/rules.d'" 3. Run the command #docker-compose up 4. Login to lava-dispatcher #docker exec -it <dispatcher-name"
bash
#apt-get update;apt-get install android-tools-adbandroid-tools-fastboot usbutils
#adb devicesCan some one let me know the steps to detect my host's
"adb-devices" in lava-dispatcher's docker?
you need to pass the devices to the container as they show up on USB bus. lava-dispatcher-host package takes care of that.
milosz
Regards, Koti _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
On Tue, Mar 31, 2020 at 07:32:08PM +0530, koti koti wrote:
Thanks Milosz.
Still "adb devices" does list the devices in the docker even those were listed in host machine.
" root@0feacfced787:/opt# dpkg -i lava-common_2020.02.0143.gd20f3bc24+10+buster_all.deb (Reading database ... 24077 files and directories currently installed.) Preparing to unpack lava-common_2020.02.0143.gd20f3bc24+10+buster_all.deb ... Unpacking lava-common (2020.02.0143.gd20f3bc24+10+buster) over (2020.02.0143.gd20f3bc24+10+buster) ... Setting up lava-common (2020.02.0143.gd20f3bc24+10+buster) ...
root@0feacfced787:/opt# dpkg -i lava-dispatcher-host_2020.02.0143.gd20f3bc24+10+buster_all.deb (Reading database ... 24077 files and directories currently installed.) Preparing to unpack lava-dispatcher-host_2020.02.0143.gd20f3bc24+10+buster_all.deb ... Unpacking lava-dispatcher-host (2020.02.0143.gd20f3bc24+10+buster) over (2020.02.0143.gd20f3bc24+10+buster) ... Setting up lava-dispatcher-host (2020.02.0143.gd20f3bc24+10+buster) ...
root@0feacfced787:/opt# /etc/init.d/udev restart [ ok ] Stopping hotplug events dispatcher: systemd-udevd. [ ok ] Starting hotplug events dispatcher: systemd-udevd.
root@0feacfced787:/opt# adb devices List of devices attached
root@0feacfced787:/opt#
This is not suppposed to work. lava-dispatcher-host will interact with the dispatcher and give device accesst to containers that were started by the dispatcher, not to the container where the dispatcher itself is running.
On Tue, Mar 31, 2020 at 01:02:00PM +0000, Milosz Wasilewski wrote:
On Tue, 31 Mar 2020 at 13:59, koti koti kotisoftwaretest@gmail.com wrote:
Thanks Milosz.
I have not find the lava-dispatcher-package in below lists. Please can you let me know the download URL for "lava-dispatcher-host" package
2.https://packages.debian.org/testing/allpackages 3.https://packages.debian.org/unstable/allpackages
You can find my docker details as mentioned below.
Try: http://apt.lavasoftware.org/
@Antonio Terceiro could you upload lava-dispatcher-host to debian?
This is in my TODO list, yes.
However, the upload will be to Debian unstable, and should also be available in Debian testing after a few days. But it will only be available for stable after the next Debian release, scheduled for next year.
For a server running stable, you should probably get the packages from apt.lavasoftware.org instead.
lava-users@lists.lavasoftware.org
-
Antonio Terceiro -
koti koti -
Milosz Wasilewski