-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
RFE: Upstream KubeBMC into KubeVirt codebase? #1
Comments
Great! I'm delighted that this project addresses some of the issues. I'm willing to assist, so please let me know the next steps or how we should proceed 🙂 |
@0xFelix, one of the KubeVirt hackers, knows better but IIUC a potential way forward could be:
There are many if's (😅), first and foremost your willingness to make it an official part of KubeVirt. But I am sure that official support for IPMI (and Redfish) in KubeVirt would be super beneficial for the community! |
@JM1 summarized it pretty well. A first good step would be to introduce KubeBMC on kubevirt-dev and to write a proposal for making it part of the KubeVirt project. An important topic is maintenance of this potential subproject. If it becomes part of KubeVirt, you would also be required to maintain it. |
Thank you, @JM1 and @0xFelix, for your positive feedback and thoughtful suggestions! I'm absolutely open to contributing KubeBMC to KubeVirt and working towards making it an official part of the project. I appreciate the outlined steps and will start by working on a proposal (is here the right place to send the PR?) and introducing KubeBMC to the kubevirt-dev mailing list. |
I am pleased to hear that you want to contribute KubeBMC to KubeVirt. I'd start by introducing it on the kubevirt-dev mailing list and asking for feedback on the project. You could outline the steps to make it a part of the KubeVirt project after the introduction. And yes, a proposal in the community repo would be a good next step after that. |
With the proposal merged, I guess we should start working on the implementation! 🎉
Any volunteers? |
@lentzi90 Thanks for bringing this up. I'll create corresponding issues to better track the progress of those tasks. If anyone is interested in any of the items, they can take and start working on it. |
A small bit of advice from an Ironic community person: don't bother with IPMI. It's a complicated binary protocol, and you'll get diminishing returns out of supporting it compared to the much simpler (HTTP+JSON) Redfish. |
Hi @starbops, what do you think about making this a GSoC project for KubeVirt? |
Hi @0xFelix Thanks for your suggestion about making KubeVirtBMC a GSoC project—I appreciate the idea and am open to exploring it. Could you share more details on how to proceed with that? Also, I wanted to follow up on the project transfer to the KubeVirt organization. While there’s no strict timeline, I’m eager to move forward when the team is ready. Let me know your thoughts! Thanks! We already have some issues labeled with "help wanted", which could spark some ideas for the GSoC project. |
There is a Google Doc for possible GSoC projects in KubeVirt. I've added KubeVirtBMC to it. Can you review and possibly add some notes to it? https://docs.google.com/document/d/13oy-jdAPJjNfl_FpUuOT6O0Sc_q8ruuaZ2e1Q_T90V0/edit?tab=t.0 @aburdenthehand Is there anything left for us to do for now? |
@felix Matouschek ***@***.***>
You will need to create a community issue for the GSoC project that we can
reference in our GSoC page and application.
Please see these issues from last year:
kubevirt/community#254
kubevirt/community#256
kubevirt/community#257
Cheers,
Andrew
…On Fri, Feb 7, 2025 at 10:37 AM Felix Matouschek ***@***.***> wrote:
There is a Google Doc for possible GSoC projects in KubeVirt.
I've added KubeVirtBMC to it. Can you review and possibly add some notes
to it?
https://docs.google.com/document/d/13oy-jdAPJjNfl_FpUuOT6O0Sc_q8ruuaZ2e1Q_T90V0/edit?tab=t.0
@aburdenthehand <https://github.com/aburdenthehand> Is there anything
left for us to do for now?
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEHO4ZHFLDXJZQI3AJ7NXIT2OR5GTAVCNFSM6AAAAABVNJIFBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBSGQZDIMBQHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@0xFelix, I've added some details to the Google Docs. Please let me know if I'm missing anything. Thank you. |
@0xFelix Hello ! As mentioned on the google docs for GSOC , I believe you and starbops are working on phase one right ? |
It is part of the GSoC project to complete the missing parts of the first phase. IIUC it should already be largely completed. @starbops Please correct me. |
Hi @anishbista60, Thanks for contacting us! Most of the tasks in phase one have been completed. As Felix said, the expected outcome of the GSoC project is to transfer KubeVirtBMC to the KubeVirt organization and continue working on the remaining phases, including phase two, three, and, optionally, four. Contributions are always welcome! But I'm unsure whether it conflicts with the GSoC project since it has a clearly defined scope. Might need @0xFelix to help clarify this. |
@starbops I mean regarding conflict of interest i am doing it from GSOC perspective . Will show early on approach and work an d apply through proposal at the end. Thanks |
Just to clarify: Getting familiar with KubeVirtBMC and the GSoC project is fine. But please do not start too much work in advance. Work on the implementation should start as soon as it has been assigned. |
Thanks for KubeBMC, @starbops 🤩 It partially solves a long standing KubeVirt issue☺️
For increased awareness, usage and easier distribution it would be great if KubeBMC would be incorporated into KubeVirt.
The text was updated successfully, but these errors were encountered: