Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TASK] Migrate various names to conform KubeVirt conventions #5

Closed
starbops opened this issue Apr 22, 2024 · 3 comments
Closed

[TASK] Migrate various names to conform KubeVirt conventions #5

starbops opened this issue Apr 22, 2024 · 3 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@starbops
Copy link
Owner

starbops commented Apr 22, 2024

Due to the upcoming project migration schedule, we have some tasks that need to be done before the migration to ensure smooth progress.

One of the tasks is to renaming the CRD and change the API group of it to conform the KubeVirt convention:

  • Changing from KubeBMC to VirtualMachineBMC
  • Changing from zespre.com to kubevirt.org

Also, the components kubebmc-controller and kbmc should be renamed to virt-bmc-controller and virt-bmc, respectively.

Finally, the project's name will be changed to KubeVirtBMC to convey that this project is targeted to work with KubeVirt.

P.S. This is a follow-up issue of #1.

@kashifest
Copy link
Contributor

I can help in this one
/assign @kashifest

@kashifest
Copy link
Contributor

/assign

@starbops
Copy link
Owner Author

@kashifest
Thank you for volunteering to handle this issue! I really appreciate your help. I will assign this issue to you now. If you need any further information or assistance, please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants