Andrei Gherzan – Principal Open Source Architect,
Open Source Technology Center
华为技术有限公司 Huawei Technologies Co., Ltd.
![Company_logo]()
Email: andrei.gherzan@xxxxxxxxxx
本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中
的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!
This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!
From: kanto-dev [mailto:kanto-dev-bounces@xxxxxxxxxxx]
On Behalf Of Gramatova Dr. Konstantina (IOB/PAD-PM1)
Sent: 10 May 2022 13:56
To: kanto developer discussions <kanto-dev@xxxxxxxxxxx>
Cc: Amit Kucheria <amit.kucheria.ext@xxxxxxxxxx>; Zygmunt Krynicki <zygmunt.krynicki@xxxxxxxxxx>
Subject: Re: [kanto-dev] Yocto integration of Kanto's components
Hi Andrei!
Thank you for the input and please accept our apologies for the late response!
The Yocto integration of Kanto is currently an ongoing work on our side but still – I can give you a heads-up regarding what we are aiming
for there. The goal is to provide a single meta layer (e.g. meta-kanto) that will include a recipe per building block (e.g. recipes-connectivity/suite-connector_git.bb, recipes-containers/container-management_git.bb, etc. ) alongside an .inc file per recipe
for flexibility.
As it is still an ongoing work, unfortunately, there is still no official user documentation in the Kanto website. Nevertheless, as the
Bosch IoT Edge Agent is a basis we are open sourcing as part of Kanto, you can take a look at
its user documentation and the approach that we took there a while ago. The one for Kanto will be similar with regards to structure of the layer with the difference that all recipes will be built from the source that is now available in the respective public
GitHub repos in Kanto.
Please, let us know if we can provide further information regarding the layer and/or a specific recipe upfront so that we can enable you
in your PoC experience until we get the layer publicly available!
Mit freundlichen Grüßen / Best regards
Dr. Konstantina Gramatova
(IOB/PAD-DDM-ES3)
Bosch.IO GmbH | Ziegelei 7 | 88090 Immenstaad |
GERMANY | www.bosch.io
Tel. +359 2 9055876 | Mobile +359 883 472547 | Fax +359 2 95326-17 |
Konstantina.Gramatova@xxxxxxxx
Registered Office: Berlin, Registration Court: Amtsgericht Charlottenburg; HRB 148411 B
Chairman of the Supervisory Board: Stefan Koss; Managing Directors: Dr. Andreas Nauerz, Yvonne Reckling
Hello Kanto team,
We had a call a couple of weeks ago where Kanto and Oniro Projects met and tried to have an initial assessment for possible collaboration. I have started to look a bit deeper into Kanto’s components to try to get hands-on/PoC experience.
We are currently in the phase where we select the container runtime and while doing so we want to play with the associated support in Kanto.
We have mentioned in the call that our build system of choice is Yocto and we were happy to understand that Yocto/OE is one of the supported “distros”. I have checked the public documentation available at
https://www.eclipse.org/kanto/docs/ but I couldn’t find any references for a Kanto Yocto layer – or similar integration. Could you guide me to where that is available? The current instructions assume a Debian-like host distro -
https://www.eclipse.org/kanto/docs/getting-started/install/.
Thanks,
Andrei Gherzan – Principal Open Source Architect,
Open Source Technology Center
华为技术有限公司 Huawei Technologies Co., Ltd.
本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中
的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!
This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!