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
I suggest that everything related to AIO is removed from the collection:
In order not to confuse the users
To reduce the maintenance burden
ISSUE TYPE
Feature Idea
COMPONENT NAME
roles/configure_aio_server
roles/setup_aio_server
documentation and examples
ADDITIONAL INFORMATION
The all-in-one (AIO) command for running FDO server is an internal tool used for debugging and development of new features, and is not intended for FDO customers. It isn't mentioned in the user documentation (HOWTO / README) of the FDO package, and makes little sense in real-world manufacturing and onboarding scenarios.
If the AIO roles are removed, it will still be possible to deploy all FDO server types to the same host, e.g. for demo or test purposes, by crafting the inventory in the right way, but their separation (and the playbooks) will be kept close to the real-world usage.
The text was updated successfully, but these errors were encountered:
SUMMARY
I suggest that everything related to AIO is removed from the collection:
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION
The all-in-one (AIO) command for running FDO server is an internal tool used for debugging and development of new features, and is not intended for FDO customers. It isn't mentioned in the user documentation (HOWTO / README) of the FDO package, and makes little sense in real-world manufacturing and onboarding scenarios.
If the AIO roles are removed, it will still be possible to deploy all FDO server types to the same host, e.g. for demo or test purposes, by crafting the inventory in the right way, but their separation (and the playbooks) will be kept close to the real-world usage.
The text was updated successfully, but these errors were encountered: