Renaming the exporter? What is your opinion?

[mrlhansen]

This issue is for getting your feedback on potentially renaming the project.

There have been some requests for renaming the exporter, but I have been hesitant because it's impractical. Most notably, renaming the project will also mean renaming the Docker and Helm repository, which means that all installations using either will have the be migrated to the new repositories.

Even if I rename it, then there is the question of name. There are already several bmc and redfish exporters. I was thinking redfish_bmc_exporter which is unique from what I can see.

Yay or nay? Leave a comment below.

[AlexG14]

Nay.
I can understand reasons behind this requests but consequences are a bit more than replacing a few symbols in a helm chart\docker compose file. You will lose all references (forums\mailing lists). Yes, you always can point to the new project and leave this one 'frozen' forever. Anyone can use any name for container so there is a very limited benefit from renaming.

[ilanni2460]

This issue is for getting your feedback on potentially renaming the project.

There have been some requests for renaming the exporter, but I have been hesitant because it's impractical. Most notably, renaming the project will also mean renaming the Docker and Helm repository, which means that all installations using either will have the be migrated to the new repositories.

Even if I rename it, then there is the question of name. There are already several bmc and redfish exporters. I was thinking redfish_bmc_exporter which is unique from what I can see.

Yay or nay? Leave a comment below.

I agree with your proposal. At first glance, IDRAC only supports Dell. In fact, it now supports data collection from many manufacturers.