You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The use of zezere as a provisioning tool has never been as complete as we would have liked. The implementation lacks things like overall device management (i.e. removing devices, modifying device config), is limited to provisioning SSH keys, and has unreliable IPv6 support.
Since development and support of zezere has not been a priority within the community and with provisioning alternatives available, I would suggest that we deprecate the use of zezere in Fedora IoT in a future release.
This would at least involve advance communication to the community, a deprecation window for users to adopt alternative provisioning solutions, the wind down of the zezere service in Fedora, and perhaps ultimately archiving the zezere repo.
The text was updated successfully, but these errors were encountered:
The use of zezere as a provisioning tool has never been as complete as we would have liked. The implementation lacks things like overall device management (i.e. removing devices, modifying device config), is limited to provisioning SSH keys, and has unreliable IPv6 support.
There were proposals to enhance
zezere
to properly support FIDO Device Onboard, but that has never gained traction/priority with the folks working on IoT. (See: fedora-iot/zezere#112, fedora-iot/zezere#113, fedora-iot/zezere#114, fedora-iot/zezere#115, fedora-iot/zezere#116)Since development and support of zezere has not been a priority within the community and with provisioning alternatives available, I would suggest that we deprecate the use of zezere in Fedora IoT in a future release.
This would at least involve advance communication to the community, a deprecation window for users to adopt alternative provisioning solutions, the wind down of the
zezere
service in Fedora, and perhaps ultimately archiving thezezere
repo.The text was updated successfully, but these errors were encountered: