Hi, I am an intern with the Open Mainframe Project <https://www.openmainframeproject.org/>. First off, you guys are doing an awesome job actively developing Kata. Thanks a lot. Second, we were initially working on porting gvisor. However, considering the stability and performance of Kata, we have decided to drop gvisor and we will now be working on porting Kata to the IBM Z mainframe platform. This fork would as of now reside under Qata Containers. I would personally love to have the port incorporated into Qata however, some managerial and legal issues remain a hurdle. Once those are sorted and if the community agrees, we would love to merge the port into Kata. The port is not complete yet. Hence, its not publicly available yet. I am just writing this mail to thank you and inform you about the same. -- Thanks Yash D Jain Github : @ydjainopensource <https://github.com/ydjainopensource> Twitter : @Yash_D_Jain <https://twitter.com/Yash_D_Jain> LinkedIn : in/yash-d-jain <https://www.linkedin.com/in/yash-d-jain/>
Great data-point, thanks Yash. Don’t hesitate to reach out if you have questions on the design or if you find anything unexpected from a usability, compatibility, or performance perspective. Cheers, Eric From: yash jain <ydjainopensource@gmail.com> Date: Tuesday, August 7, 2018 at 10:39 AM To: "kata-dev@lists.katacontainers.io" <kata-dev@lists.katacontainers.io> Subject: [kata-dev] Kata on Mainframes Hi, I am an intern with the Open Mainframe Project<https://www.openmainframeproject.org/>. First off, you guys are doing an awesome job actively developing Kata. Thanks a lot. Second, we were initially working on porting gvisor. However, considering the stability and performance of Kata, we have decided to drop gvisor and we will now be working on porting Kata to the IBM Z mainframe platform. This fork would as of now reside under Qata Containers. I would personally love to have the port incorporated into Qata however, some managerial and legal issues remain a hurdle. Once those are sorted and if the community agrees, we would love to merge the port into Kata. The port is not complete yet. Hence, its not publicly available yet. I am just writing this mail to thank you and inform you about the same. -- Thanks Yash D Jain Github : @ydjainopensource<https://github.com/ydjainopensource> Twitter : @Yash_D_Jain<https://twitter.com/Yash_D_Jain> LinkedIn : in/yash-d-jain<https://www.linkedin.com/in/yash-d-jain/>
@Eric Thanks a lot will reach out if I need help. @Anne, @jbryce, Thank you but the legal hurdles are not from your side but ours. I don't know much but I have been told that theres a lot of high performance networking code optimized for Z which IBM wishes to include in the fork and won't like it going out of their control. Second, CI access for open source is proving difficult without the project residing under a IBM/ IBM allied company. Thanks On Wed, Aug 8, 2018 at 2:06 AM Ernst, Eric <eric.ernst@intel.com> wrote:
Great data-point, thanks Yash.
Don’t hesitate to reach out if you have questions on the design or if you find anything unexpected from a usability, compatibility, or performance perspective.
Cheers, Eric
*From: *yash jain <ydjainopensource@gmail.com> *Date: *Tuesday, August 7, 2018 at 10:39 AM *To: *"kata-dev@lists.katacontainers.io" <kata-dev@lists.katacontainers.io
*Subject: *[kata-dev] Kata on Mainframes
Hi,
I am an intern with the Open Mainframe Project <https://www.openmainframeproject.org/>.
First off, you guys are doing an awesome job actively developing Kata. Thanks a lot.
Second, we were initially working on porting gvisor. However, considering the stability and performance of Kata, we have decided to drop gvisor and we will now be working on porting Kata to the IBM Z mainframe platform. This fork would as of now reside under Qata Containers. I would personally love to have the port incorporated into Qata however, some managerial and legal issues remain a hurdle. Once those are sorted and if the community agrees, we would love to merge the port into Kata.
The port is not complete yet. Hence, its not publicly available yet. I am just writing this mail to thank you and inform you about the same.
--
Thanks
Yash D Jain
Github : @ydjainopensource <https://github.com/ydjainopensource>
Twitter : @Yash_D_Jain <https://twitter.com/Yash_D_Jain>
LinkedIn : in/yash-d-jain <https://www.linkedin.com/in/yash-d-jain/>
-- Thanks Yash D Jain Github : @ydjainopensource <https://github.com/ydjainopensource> Twitter : @Yash_D_Jain <https://twitter.com/Yash_D_Jain> LinkedIn : in/yash-d-jain <https://www.linkedin.com/in/yash-d-jain/>
Hi, Good news. We have decided to finally upstream our work to Kata. If there are no objections, I will have some Z nodes join the existing Jenkins CI cluster by next week. Looking forward to working with you. Thanks, Yash On Wed, Aug 8, 2018 at 2:54 AM yash jain <ydjainopensource@gmail.com> wrote:
@Eric Thanks a lot will reach out if I need help.
@Anne, @jbryce, Thank you but the legal hurdles are not from your side but ours. I don't know much but I have been told that theres a lot of high performance networking code optimized for Z which IBM wishes to include in the fork and won't like it going out of their control. Second, CI access for open source is proving difficult without the project residing under a IBM/ IBM allied company.
Thanks
On Wed, Aug 8, 2018 at 2:06 AM Ernst, Eric <eric.ernst@intel.com> wrote:
Great data-point, thanks Yash.
Don’t hesitate to reach out if you have questions on the design or if you find anything unexpected from a usability, compatibility, or performance perspective.
Cheers, Eric
*From: *yash jain <ydjainopensource@gmail.com> *Date: *Tuesday, August 7, 2018 at 10:39 AM *To: *"kata-dev@lists.katacontainers.io" < kata-dev@lists.katacontainers.io> *Subject: *[kata-dev] Kata on Mainframes
Hi,
I am an intern with the Open Mainframe Project <https://www.openmainframeproject.org/>.
First off, you guys are doing an awesome job actively developing Kata. Thanks a lot.
Second, we were initially working on porting gvisor. However, considering the stability and performance of Kata, we have decided to drop gvisor and we will now be working on porting Kata to the IBM Z mainframe platform. This fork would as of now reside under Qata Containers. I would personally love to have the port incorporated into Qata however, some managerial and legal issues remain a hurdle. Once those are sorted and if the community agrees, we would love to merge the port into Kata.
The port is not complete yet. Hence, its not publicly available yet. I am just writing this mail to thank you and inform you about the same.
--
Thanks
Yash D Jain
Github : @ydjainopensource <https://github.com/ydjainopensource>
Twitter : @Yash_D_Jain <https://twitter.com/Yash_D_Jain>
LinkedIn : in/yash-d-jain <https://www.linkedin.com/in/yash-d-jain/>
-- Thanks
Yash D Jain Github : @ydjainopensource <https://github.com/ydjainopensource> Twitter : @Yash_D_Jain <https://twitter.com/Yash_D_Jain> LinkedIn : in/yash-d-jain <https://www.linkedin.com/in/yash-d-jain/>
-- Thanks Yash D Jain Github : @ydjainopensource <https://github.com/ydjainopensource> Twitter : @Yash_D_Jain <https://twitter.com/Yash_D_Jain> LinkedIn : in/yash-d-jain <https://www.linkedin.com/in/yash-d-jain/>
That sounds like good news ! Could you follow up with Salvador about this ? He'll point you to the right ppl and guide you on how to enable this through our CI. Thanks, Sebastien ________________________________ From: yash jain [ydjainopensource@gmail.com] Sent: Thursday, August 16, 2018 6:02 AM To: Ernst, Eric; Jonathan Bryce; anne@openstack.org Cc: kata-dev@lists.katacontainers.io Subject: Re: [kata-dev] Kata on Mainframes Hi, Good news. We have decided to finally upstream our work to Kata. If there are no objections, I will have some Z nodes join the existing Jenkins CI cluster by next week. Looking forward to working with you. Thanks, Yash On Wed, Aug 8, 2018 at 2:54 AM yash jain <ydjainopensource@gmail.com<mailto:ydjainopensource@gmail.com>> wrote: @Eric Thanks a lot will reach out if I need help. @Anne, @jbryce, Thank you but the legal hurdles are not from your side but ours. I don't know much but I have been told that theres a lot of high performance networking code optimized for Z which IBM wishes to include in the fork and won't like it going out of their control. Second, CI access for open source is proving difficult without the project residing under a IBM/ IBM allied company. Thanks On Wed, Aug 8, 2018 at 2:06 AM Ernst, Eric <eric.ernst@intel.com<mailto:eric.ernst@intel.com>> wrote: Great data-point, thanks Yash. Don’t hesitate to reach out if you have questions on the design or if you find anything unexpected from a usability, compatibility, or performance perspective. Cheers, Eric From: yash jain <ydjainopensource@gmail.com<mailto:ydjainopensource@gmail.com>> Date: Tuesday, August 7, 2018 at 10:39 AM To: "kata-dev@lists.katacontainers.io<mailto:kata-dev@lists.katacontainers.io>" <kata-dev@lists.katacontainers.io<mailto:kata-dev@lists.katacontainers.io>> Subject: [kata-dev] Kata on Mainframes Hi, I am an intern with the Open Mainframe Project<https://www.openmainframeproject.org/>. First off, you guys are doing an awesome job actively developing Kata. Thanks a lot. Second, we were initially working on porting gvisor. However, considering the stability and performance of Kata, we have decided to drop gvisor and we will now be working on porting Kata to the IBM Z mainframe platform. This fork would as of now reside under Qata Containers. I would personally love to have the port incorporated into Qata however, some managerial and legal issues remain a hurdle. Once those are sorted and if the community agrees, we would love to merge the port into Kata. The port is not complete yet. Hence, its not publicly available yet. I am just writing this mail to thank you and inform you about the same. -- Thanks Yash D Jain Github : @ydjainopensource<https://github.com/ydjainopensource> Twitter : @Yash_D_Jain<https://twitter.com/Yash_D_Jain> LinkedIn : in/yash-d-jain<https://www.linkedin.com/in/yash-d-jain/> -- Thanks Yash D Jain Github : @ydjainopensource<https://github.com/ydjainopensource> Twitter : @Yash_D_Jain<https://twitter.com/Yash_D_Jain> LinkedIn : in/yash-d-jain<https://www.linkedin.com/in/yash-d-jain/> -- Thanks Yash D Jain Github : @ydjainopensource<https://github.com/ydjainopensource> Twitter : @Yash_D_Jain<https://twitter.com/Yash_D_Jain> LinkedIn : in/yash-d-jain<https://www.linkedin.com/in/yash-d-jain/>
Indeed, great news! For bringing up the slaves, we can reference the thread where we added the ARM CI slave, as that will hold a lot of the same info you will need - let me find a link... this thread is probably worth a read to begin with: https://github.com/kata-containers/tests/issues/516 Just let us know (opening a github Issue like the above link might be a good idea) when you are ready :) Graham From: Boeuf, Sebastien [mailto:sebastien.boeuf@intel.com] Sent: Thursday, August 16, 2018 4:02 PM To: yash jain <ydjainopensource@gmail.com>; Ernst, Eric <eric.ernst@intel.com>; Jonathan Bryce <jonathan@openstack.org>; anne@openstack.org Cc: kata-dev@lists.katacontainers.io Subject: Re: [kata-dev] Kata on Mainframes That sounds like good news ! Could you follow up with Salvador about this ? He'll point you to the right ppl and guide you on how to enable this through our CI. Thanks, Sebastien ________________________________ From: yash jain [ydjainopensource@gmail.com] Sent: Thursday, August 16, 2018 6:02 AM To: Ernst, Eric; Jonathan Bryce; anne@openstack.org<mailto:anne@openstack.org> Cc: kata-dev@lists.katacontainers.io<mailto:kata-dev@lists.katacontainers.io> Subject: Re: [kata-dev] Kata on Mainframes Hi, Good news. We have decided to finally upstream our work to Kata. If there are no objections, I will have some Z nodes join the existing Jenkins CI cluster by next week. Looking forward to working with you. Thanks, Yash On Wed, Aug 8, 2018 at 2:54 AM yash jain <ydjainopensource@gmail.com<mailto:ydjainopensource@gmail.com>> wrote: @Eric Thanks a lot will reach out if I need help. @Anne, @jbryce, Thank you but the legal hurdles are not from your side but ours. I don't know much but I have been told that theres a lot of high performance networking code optimized for Z which IBM wishes to include in the fork and won't like it going out of their control. Second, CI access for open source is proving difficult without the project residing under a IBM/ IBM allied company. Thanks On Wed, Aug 8, 2018 at 2:06 AM Ernst, Eric <eric.ernst@intel.com<mailto:eric.ernst@intel.com>> wrote: Great data-point, thanks Yash. Don't hesitate to reach out if you have questions on the design or if you find anything unexpected from a usability, compatibility, or performance perspective. Cheers, Eric From: yash jain <ydjainopensource@gmail.com<mailto:ydjainopensource@gmail.com>> Date: Tuesday, August 7, 2018 at 10:39 AM To: "kata-dev@lists.katacontainers.io<mailto:kata-dev@lists.katacontainers.io>" <kata-dev@lists.katacontainers.io<mailto:kata-dev@lists.katacontainers.io>> Subject: [kata-dev] Kata on Mainframes Hi, I am an intern with the Open Mainframe Project<https://www.openmainframeproject.org/>. First off, you guys are doing an awesome job actively developing Kata. Thanks a lot. Second, we were initially working on porting gvisor. However, considering the stability and performance of Kata, we have decided to drop gvisor and we will now be working on porting Kata to the IBM Z mainframe platform. This fork would as of now reside under Qata Containers. I would personally love to have the port incorporated into Qata however, some managerial and legal issues remain a hurdle. Once those are sorted and if the community agrees, we would love to merge the port into Kata. The port is not complete yet. Hence, its not publicly available yet. I am just writing this mail to thank you and inform you about the same. -- Thanks Yash D Jain Github : @ydjainopensource<https://github.com/ydjainopensource> Twitter : @Yash_D_Jain<https://twitter.com/Yash_D_Jain> LinkedIn : in/yash-d-jain<https://www.linkedin.com/in/yash-d-jain/> -- Thanks Yash D Jain Github : @ydjainopensource<https://github.com/ydjainopensource> Twitter : @Yash_D_Jain<https://twitter.com/Yash_D_Jain> LinkedIn : in/yash-d-jain<https://www.linkedin.com/in/yash-d-jain/> -- Thanks Yash D Jain Github : @ydjainopensource<https://github.com/ydjainopensource> Twitter : @Yash_D_Jain<https://twitter.com/Yash_D_Jain> LinkedIn : in/yash-d-jain<https://www.linkedin.com/in/yash-d-jain/> --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
participants (4)
-
Boeuf, Sebastien
-
Ernst, Eric
-
Whaley, Graham
-
yash jain