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 ansible roles will download the latest source from GitHub and build the source to do the install. This should not happen. The installer should pull down and install a released version of the code.
Installer users could run an install mid-way during a development cycle and pick up incomplete implementations. This could cause problems and a bad first experience using OpenSDS. This also requires the installation of large packages on the users system like gcc and development packages that are not needed to actually run the service.
There could optionally be a way for them to specify that they want a development build, but that should not be the default thing that happens when running the installer.
The text was updated successfully, but these errors were encountered:
Hi @stmcginnis , we do provide the option to install from release files, but I'm afraid it's not working now, considering we change the format of released files when publishing aruba release. So maybe we should test it at first and change the default way to release after the bug is fixed.
Discussed with Sean about this issue in today's technical meeting. We will backport important bug fixes to stable/aruba. Installation can be either from stable/aruba if choosing source code or from a release tar ball after a Aruba stable release.
The ansible roles will download the latest source from GitHub and build the source to do the install. This should not happen. The installer should pull down and install a released version of the code.
Installer users could run an install mid-way during a development cycle and pick up incomplete implementations. This could cause problems and a bad first experience using OpenSDS. This also requires the installation of large packages on the users system like gcc and development packages that are not needed to actually run the service.
There could optionally be a way for them to specify that they want a development build, but that should not be the default thing that happens when running the installer.
The text was updated successfully, but these errors were encountered: