Is this project still maintained?

[bk-lg]

Is this project still maintained?

As there is no actual activity in the developement if this project since july 2021 I want to ask if this project is still mainted by @tristanrobert ?
Do you have no time to maintain this project anymore or need technial support or addtional funding?
There are multiple issues which are blocking the usage of this plugin and I would like to help to find a way to keep this plugin alive.

This is in no way confronting. I can't demand anyone to do something on an open source project and I'm glad for anyone who contributes. I only want to check what is the state ot this project and if there is any way users could help to keep it going.

Thanks in advance for the feedback.

[tristanrobert]

Yes I try to maintain it. But: I am alone, I am working as a hobby, during my free time. I have few free time (father). I have few sponsors and I thank you them but sure I could'nt live with only that financial revenue. Multiple issues are redundants and come from break changes in theforeman code (especially in react UI), many are not fixed and I have to find complexed workarounds. Some foreman issues are blocking: https://projects.theforeman.org/issues/34715. I do my best.

[bk-lg]

@tristanrobert Thank you for your feedback. Your family is definitly a more important part of your live.
Also thanks for the insight, what it makes so complicate to fix some of this things.

[gmalfray]

Thank you Tristan for your work. This plugin works very well for me in the current state so I will no longer update foreman or proxmox ^^

[djken09]

@gmalfray can you please detail your setup? I would like to have mine working but so far no luck with diff versions I have tried. Thanks!

[gmalfray]

@djken09 old version :)
Ubuntu 20.04.4
Ruby 2.7
foreman_fog_proxmox 0.14.0
Proxmox 6.2-12 and 6.4-13
Foreman 3.1.1

[djken09]

Big thanks @gmalfray! Gonna give it a try and let you guys know.

[NausX]

Hi! I was wondering, have this been tested with foreman 3.3?

[ekohl]

if there is any way users could help to keep it going.

Note that from the Foreman organization we can add additional maintainers. If anyone is interested, please let us know. As an open source project we rely on contributors to help.

I've just merged the open PRs.

@tristanrobert can you add the Foreman org as an owner to https://rubygems.org/gems/foreman_fog_proxmox so we can also do releases? I've emailed the exact instructions.

[dmgeurts]

Hi! I was wondering, have this been tested with foreman 3.3?

Wondering the same but about v3.4. Proxmox came up in a conversation today, so I'm trying to assess how viable a Proxmox integration into Foreman currently is.

[ekohl]

Thanks @tristanrobert or adding Foreman to the gem owners. This means we can do a release.

@dmgeurts I can at least do a 0.14.1 bugfix release with the changes since 0.14.0 but I don't have access to a Proxmox setup to verify it really works. Looking at the open issues it may be broken. It'd be good to get some contributions on this plugin.

[jacac]

I'm using it with Foreman 3.3 to deploy LXC containers.

It is possible to use it but you need to find your ways around some issues.

Those commits were applied manually:
4e3023c
a3fd60a
fdad87f
b079471

Current issues I observed:

• Create host fails on 2.5.2 #207
  Thanks to @donywahlberg for finding a workaround. (https://github.com/donywahlberg))](Create host fails on 2.5.2 #207 (comment))

• VLAN Tag is not transmitted to the proxmox api at vm creation #228
  A lot of count and byte fields are hit in miss. For example if the VLAN field is converted to a count field (up/down arrows in the input field) the VLAN id will not be transmitted and need to be set manually in Proxmox. Sometimes the VLAN is just a text field and works. The storage size field is sometimes not converted to a byte_size_f field and needs the value in bytes. This issues is related to Refs #30784 - MemoryAllocation use react helper foreman#8413 (comment) Another comment on that Create host fails on 2.5.2 #207 (comment)

Those are the ones related to both LXC and VM machines I think. They are some other issues with workarounds just for LXC containers. I cannot speak to the VM side.