Community Fork?

[roock]

I see a lot of people have currently forked this repository working independently on new feature and keeping it maintained. What do you guy think of joining forces together and drive this as a community effort?

Tagging everyone how contributed on a fork within the last year:

@cbw @mhollstein @srkaviani @longpaul @n27051538 @baonq-me @root-ali @wardellc

Please let me know what you think and/or willing to do this as a community.

[srkaviani]

Very good.
I agree to join this community.

[baonq-me]

What do you suggest?

[roock]

I have created the hpilo-exporter github organization and sent you invites. I would suggest that we continue the development of this project there and start further discussions there.

[cbw]

I'm open to participating. Thanks @roock for driving this!

[baonq-me]

I have created the hpilo-exporter github organization and sent you invites. I would suggest that we continue the development of this project there and start further discussions there.

Can you be more specific, like which feature or problem should be addressed?

[longpaul]

Sadly the exporter is not actively maintained. That's why I'm also willing to help

[roock]

Can you be more specific, like which feature or problem should be addressed?

The problem I would like to solve is that currently there are 10+ forks of the original repository, all with different features and/or features which have been implemented multiple times independently. I think everyone would benefit if we have one repository which contains all features and is kept uptodate.

I can understand that you have already spend a lot of time to merge some of the changes together, but your repository is lacking some important things like python3 support or automated building of docker image.

[n27051538]

Hello, dears!

I have added this to exporter a few years ago:

• support for Python 3.6.
• ilo_user, ilo_password, ilo_port may be preset via environment.
• storage health information from iLO (cache, controller, logical drives, physical drives).
• temperature values information from iLO.
• per-fan and per-power-supply statuses.
• OA info for Blade servers
• Server ON status.
• Alert rules for Prom
• Also I have Grafana Dashboard about, but it is not published to github.

Since this modification it works well on all HPE servers that I have to monitor.
I am not using docker still, so DockerFile is without any mod and not tested.

[baonq-me]

Here is my dashboard (of course, it works with my fork https://github.com/baonq-me/hpilo-exporter)
https://gist.github.com/baonq-me/75f3041fea0e01f74d6a170c53c95a5e

[roock]

Here is my dashboard (of course, it works with my fork https://github.com/baonq-me/hpilo-exporter) https://gist.github.com/baonq-me/75f3041fea0e01f74d6a170c53c95a5e

Yeah, your Grafana Dashboard looks great, I'm already using it 😄 As you just stated, it works with YOUR fork, I think everyone would benefit from one shared repository where all the improvements are collected and kept uptodate. And which is easy to find and you don't have to look in 5 different forks to get all the features.

Also your Grafana Dashboard contains some hardcoded references (e.g. to datasources and hostnames).

[roock]

Hello, dears!

I have added this to exporter a few years ago:

• support for Python 3.6.
• ilo_user, ilo_password, ilo_port may be preset via environment.
• storage health information from iLO (cache, controller, logical drives, physical drives).
• temperature values information from iLO.
• per-fan and per-power-supply statuses.
• OA info for Blade servers
• Server ON status.
• Alert rules for Prom
• Also I have Grafana Dashboard about, but it is not published to github.

Since this modification it works well on all HPE servers that I have to monitor. I am not using docker still, so DockerFile is without any mod and not tested.

Yeah, you did a great job with the improvements, I would really like to see them in a shared repository. (Unfortunately it's a bit hard to cherry-pick your changes, since you make more or less complete rewrite 😄

[srkaviani]

Here is my dashboard (of course, it works with my fork https://github.com/baonq-me/hpilo-exporter) https://gist.github.com/baonq-me/75f3041fea0e01f74d6a170c53c95a5e

Your Grafana Dashboard is very good. but it contains some hardcoded references. for fix this issue please export dashboard with option "Export for sharing externally".
and I suggest to share this dashboard and other future dashboard of this exporter to grafana.com (same as : https://grafana.com/orgs/soroush7339)

[baonq-me]

Here is my dashboard (of course, it works with my fork https://github.com/baonq-me/hpilo-exporter) https://gist.github.com/baonq-me/75f3041fea0e01f74d6a170c53c95a5e

Your Grafana Dashboard is very good. but it contains some hardcoded references. for fix this issue please export dashboard with option "Export for sharing externally". and I suggest to share this dashboard and other future dashboard of this exporter to grafana.com (same as : https://grafana.com/orgs/soroush7339)

Thanks for your idea. I'll bring the dashboard to grafana.com.

[roock]

I've started creating a repository with all the combined changes of the different forks including a matching Grafana Dashboard and a working Dockerfile with Python3.
https://github.com/hpilo-exporter/hpilo-exporter

[mhollstein]

Hello Roman,You can use everything from my forkand put it into your project if you want. Best Regards,MichaelGesendet mit der mobilen Mail AppAm 06.04.23 um 17:00 schrieb Roman Pertl Von: "Roman Pertl" ***@***.***>Datum: 6. April 2023An: "infinityworks/hpilo-exporter" ***@***.***>Cc: "mhollstein" ***@***.***>,"Mention" ***@***.***>Betreff: [infinityworks/hpilo-exporter] Community Fork? (Issue #21) I see a lot of people have currently forked this repository working independently on new feature and keeping it maintained. What do you guy think of joining forces together and drive this as a community effort? Tagging everyone how contributed on a fork within the last year: @cbw @mhollstein @srkaviani @longpaul @n27051538 @baonq-me @root-ali @wardellc Please let me know what you think and/or willing to do this as a community. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>