Hey Folks,
We will have our weekly CoCo meeting tomorrow (March 21st), at 2:00 PM UTC - 10 AM EDT - 10PM CST.
We'll start with opens and hopefully some initial report from the ongoing KubeCon.
Then we'll talk about our merge to main [1] progress.
And our technical talk of the week will be lead by Thomas Fossati from Linaro. He will talk about Trustee and EAR (EAT Attestation Results).
A weekly reminder that the community agenda [2] is open for new technical topis suggestions, or for any additional agenda item for the upcoming meetings.
See you all in a few hours!
Cheers,
Samuel.
[1] https://github.com/orgs/kata-containers/projects/38/views/2
[2] https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRTJ0QnJh…
Hello Everyone,
The April PTG is rapidly approaching and team moderators are signing up for
time to meet via the PTGbot. The schedule is filling up and we are excited
to see you all!
If you have not yet registered, please do so! It's free![1].
Another note about this PTG in particular, Meetpad is the default video
conferencing tool. TTeam moderators are able to override the meeting URL if
they choose to do so in order to make use of other tools. We do have a few
zoom rooms if needed. This is the first PTG we are doing this for, so
please give us feedback[2] with as many details as possible if you run into
any issues with Meetpad. Open source needs open tools after all!
If you have any questions, please let us know via email to ptg(a)openinfra.dev
.
Thank you!
-Kendall Nelson
Senior Upstream Developer Advocate
The OpenInfra Foundation
[1] http://ptg2023.openinfra.dev/
[2] https://etherpad.opendev.org/p/April2024-PTG-Feedback
Dear Kata Containers Community,
I have open an issue on github, https://github.com/kata-containers/kata-containers/issues/9279, but<https://github.com/kata-containers/kata-containers/issues/9279,%20but> nobody helps me to resolve this issue.
Could you please help me figure out where is wrong about my step?
Thanks very much.
Yangfei
发件人: Yang Fei 杨斐
发送时间: 2024年3月13日 22:09
收件人: 'kata-dev(a)lists.katacontainers.io'
主题: Kata Containers CNI Network Problems on kata 3.2
Dear Kata Containers Community,
I'm the user of Kata Containers from Haier Corp of China。Now I want your support to resolve my problems.
I run Kata(version:3.2.0) containers on Containerd (v1.7.9) with CNI Network, and the hypervisor is ACRN(V3.2.0) 。Now I can run a kata containers on acrn hypervisor,but the SOS cannot communicate with each other over the cni network,but it works when using hypervisor QEMU。
Here are my steps:
1. Create cni conf file
cat << EOF | tee /etc/cni/net.d/redisnet.conf
{
"cniVersion": "0.4.0",
"name": "redisnet",
"type": "bridge",
"bridge": "cni0",
"isDefaultGateway": true,
"forceAddress": false,
"ipMasq": true,
"hairpinMode": true,
"ipam": {
"type": "host-local",
"subnet": "10.77.0.0/16"
}
}
EOF
2. Create networkspace and add network into it.
ip netns add redisnet
export CNI_PATH=/opt/cni/bin
cnitool add redisnet /var/run/netns/redisnet
cnitool check redisnet /var/run/netns/redisnet
[https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=ZWYz…]
I am now able to ping 10.77.0.2.
[https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=MGVh…]
3. Start a kata container with CNI Network
ctr run --snapshotter devmapper --runtime "io.containerd.kata.v2" --with-ns=network:/var/run/netns/redisnet -d registry2-qingdao.cosmoplat.com/62_edegecloud/ubuntu-vim-ip:22.04 kata-test sh
but the container's eth0 is link down.
[https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=YjJi…]
Now I cannot ping 10.77.0.2。
[https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=MmM0…]
could you please help me figure out where is wrong about my steps? If not wrong ,could you please help me resolve this problems?
Here are some logs and configs of my test.
Thanks and Best Regards,
Jason Yang
The information transmitted is intended solely for the use of the addressee and may contain confidential and/or privileged material. Any unauthorized disclosure, reproduction, distribution, dissemination, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the email together with any material attached (if any) completely from any device immediately. Unless otherwise stated, any views or opinions expressed in this email are solely those of the author and do not necessarily represent those of Haier Group.
本邮件可能包含敏感信息且仅限于发给指定的收件人,任何未经授权泄露、复制、散布或传播此信息的行为将被禁止。如果您错误收到了此邮件,请及时告知发送者并立即从所有设备中完全删除此邮件及附件。除非另有说明,否则邮件中可能包含的观点或建议仅代表发件者本人,并不代表海尔集团。
Dear Kata Containers Community,
I'm the user of Kata Containers from Haier Corp of China。Now I want your support to resolve my problems.
I run Kata(version:3.2.0) containers on Containerd (v1.7.9) with CNI Network, and the hypervisor is ACRN(V3.2.0) 。Now I can run a kata containers on acrn hypervisor,but the SOS cannot communicate with each other over the cni network,but it works when using hypervisor QEMU。
Here are my steps:
1. Create cni conf file
cat << EOF | tee /etc/cni/net.d/redisnet.conf
{
"cniVersion": "0.4.0",
"name": "redisnet",
"type": "bridge",
"bridge": "cni0",
"isDefaultGateway": true,
"forceAddress": false,
"ipMasq": true,
"hairpinMode": true,
"ipam": {
"type": "host-local",
"subnet": "10.77.0.0/16"
}
}
EOF
2. Create networkspace and add network into it.
ip netns add redisnet
export CNI_PATH=/opt/cni/bin
cnitool add redisnet /var/run/netns/redisnet
cnitool check redisnet /var/run/netns/redisnet
[https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=ZWYz…]
I am now able to ping 10.77.0.2.
[https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=MGVh…]
3. Start a kata container with CNI Network
ctr run --snapshotter devmapper --runtime "io.containerd.kata.v2" --with-ns=network:/var/run/netns/redisnet -d registry2-qingdao.cosmoplat.com/62_edegecloud/ubuntu-vim-ip:22.04 kata-test sh
but the container's eth0 is link down.
[https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=YjJi…]
Now I cannot ping 10.77.0.2。
[https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=MmM0…]
could you please help me figure out where is wrong about my steps? If not wrong ,could you please help me resolve this problems?
Here are some logs and configs of my test.
Thanks and Best Regards,
Jason Yang
The information transmitted is intended solely for the use of the addressee and may contain confidential and/or privileged material. Any unauthorized disclosure, reproduction, distribution, dissemination, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the email together with any material attached (if any) completely from any device immediately. Unless otherwise stated, any views or opinions expressed in this email are solely those of the author and do not necessarily represent those of Haier Group.
本邮件可能包含敏感信息且仅限于发给指定的收件人,任何未经授权泄露、复制、散布或传播此信息的行为将被禁止。如果您错误收到了此邮件,请及时告知发送者并立即从所有设备中完全删除此邮件及附件。除非另有说明,否则邮件中可能包含的观点或建议仅代表发件者本人,并不代表海尔集团。
Hey Everyone,
We have our CoCo community meeting tomorrow. Remember, the meeting time
is specified in UTC, so if you are now experiencing daylight saving
time, the meeting will appear to be an hour later than it was
previously. In other words, it's at 2:00 PM UTC - 10 AM EDT - 10PM CST.
At the meeting we will first poke fun at everyone who showed up an hour
early, then we'll discuss the merge to main. There are also a few very
interesting proposals/PRs to point towards. Then we'll see a great demo
of CoCo in action.
As always, if you have something good for the community meeting, please
add it to the agenda. [1]
See you soon,
Tobin
[1]
https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRTJ0QnJh…
Dear Kata Containers Community,
I'm the user of Kata Containers from Haier Corp of China。Now I want your support to resolve my problems.
I run Kata(version:3.2.0) containers on Containerd (v1.7.9) with CNI Network, and the hypervisor is ACRN(V3.2.0) 。Now I can run a kata containers on acrn hypervisor,but the SOS cannot communicate with each other over the cni network,but it works when using hypervisor QEMU。
Here are my steps:
1. Create cni conf file
cat << EOF | tee /etc/cni/net.d/redisnet.conf
{
"cniVersion": "0.4.0",
"name": "redisnet",
"type": "bridge",
"bridge": "cni0",
"isDefaultGateway": true,
"forceAddress": false,
"ipMasq": true,
"hairpinMode": true,
"ipam": {
"type": "host-local",
"subnet": "10.77.0.0/16"
}
}
EOF
2. Create networkspace and add network into it.
ip netns add redisnet
export CNI_PATH=/opt/cni/bin
cnitool add redisnet /var/run/netns/redisnet
cnitool check redisnet /var/run/netns/redisnet
[https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=ZWYz…]
I am now able to ping 10.77.0.2.
[https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=MGVh…]
3. Start a kata container with CNI Network
ctr run --snapshotter devmapper --runtime "io.containerd.kata.v2" --with-ns=network:/var/run/netns/redisnet -d registry2-qingdao.cosmoplat.com/62_edegecloud/ubuntu-vim-ip:22.04 kata-test sh
but the container's eth0 is link down.
[https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=YjJi…]
Now I cannot ping 10.77.0.2。
[https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=MmM0…]
could you please help me figure out where is wrong about my steps? If not wrong ,could you please help me resolve this problems?
Here are some logs and configs of my test.
Thanks and Best Regards,
Jason Yang
The information transmitted is intended solely for the use of the addressee and may contain confidential and/or privileged material. Any unauthorized disclosure, reproduction, distribution, dissemination, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the email together with any material attached (if any) completely from any device immediately. Unless otherwise stated, any views or opinions expressed in this email are solely those of the author and do not necessarily represent those of Haier Group.
本邮件可能包含敏感信息且仅限于发给指定的收件人,任何未经授权泄露、复制、散布或传播此信息的行为将被禁止。如果您错误收到了此邮件,请及时告知发送者并立即从所有设备中完全删除此邮件及附件。除非另有说明,否则邮件中可能包含的观点或建议仅代表发件者本人,并不代表海尔集团。
Hey everyone,
Tomorrow we have a special LEAP DAY edition of our community meeting. It
will be at the usual time of 2:00 PM UTC - 9 AM EST - 10PM CST.
While we could spend the entire meeting basking in the cosmic glory of
the leap day, we do have a few things to talk about. First, we'll catch
up on the Merge2Main. We've had some great progress in the last week,
but we still have a long way to go.
Next we'll have a series of smallish updates about different parts of
the project. We'll touch on the KBS renaming, which is expected to
complete this week. We'll get an update on the CoCo website, which is
looking amazing. We'll talk about the forks we are going to use to keep
some track of some of the AMD components, and finally we'll get an
update on the recent PR for the split API work.
If you happen to have another update you want to share, this meeting
might be a good one (assuming we can get through all of the above), so
feel free to add it to the agenda. [1]
See you soon,
Tobin
[1]
https://docs.google.com/document/d/1E3GLCzNgrcigUlgWAZYlgqNTdVwiMwCRTJ0QnJh…
Hi Kata Containers Community,
I’m reaching out to you about the upcoming Architecture Committee (AC) elections.
Members of the AC are selected through a staggered election process, and their term is valid for one year. AC elections happen twice a year, and the next round is scheduled for April, 2024, with the below timeline:
* April 08, 15:00 UTC - April 15, 2024 14:59 UTC: Candidate nominations open
* April 15, 15:00 UTC - April 22, 2024 14:59 UTC: Q&A/Debate period
* April 22, 15:00 UTC - April 29, 2024 14:59 UTC: Voting open
* April 30, 2024, results announced
There are three seats up for re-election in this round.
You can find more information about the upcoming elections here: https://github.com/kata-containers/community/tree/main/elections/arch-commi…
To learn more about the election process and how to submit your candidacy, please check out the documentation here: https://github.com/kata-containers/community/tree/main/elections
I’m also looking for election officials to assist with running the process. Please reply to this email or reach out to me on Slack if you would like to volunteer to help out!
Thanks and Best Regards,
Ildikó
———
Ildikó Váncsa
Director of Community
Open Infrastructure Foundation
Hello Everyone!
The April 2024 Project Teams List is official!
Projects + Teams
- OpenInfra Foundation Teams
-
- Diversity & Inclusion Working Group
- OpenInfra Edge Computing Group
- Kata Containers
- OpenDev
- StarlingX
- OpenStack
-
- Services
-
- Blazar
- Cinder
- CloudKitty
- Designate
- Glance
- Horizon
- Ironic
- Keystone
- Kolla
- Magnum
- Manila
- Neutron
- Nova
- Octavia
- OpenStackAnsible
- OpenStack-Helm
- OpenStackSDK/CLI
- Quality Assurance
- Release Management
- Tacker
- Other OpenStack Teams
-
- OpenStack Security SIG
- OpenStack Technical Committee
- PublicCloud SIG
- RBAC
- VDI
If your team was planning to meet and isn’t on this list, please contact
ptg(a)openinfra.dev IMMEDIATELY.
Soon, I will be contacting moderators to sign up for time via the PTGBot[1]
once I have it configured for the teams that are signed up to attend the
event.
Otherwise, please don't forget to register[2] — it's FREE!
As usual, feel free to let us know if you have any questions!
Thanks!
-Kendall (diablo_rojo)
[1] PTGBot Docs:
https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot
[2] PTG Registration: https://ptg2024.openinfra.dev/
<http://ptg2023.openinfra.dev/>