After capturing the system information you will want to run some checks and diagnostics depending on what the user selected. You might later these diagnostics can be optional, like you know the optional memory check before an install (do not do memory check this is an example). Some diagnostics may also be run after installing the component or a minor step. Failing fast is best and reporting options to the user. We want to check (do diagnostics on) a few things:
Do virtualbox operations work (if installing a peer or RH)?
Does NAT configuration with test VM creation work?
Test for known bugs in dependencies like VBox or osascript
Proper operation and presence of dependencies need to be checked for the tray and p2p
Check for post installation: might trigger uninstall properly before installation begins
Check to see if any key bugs on any system components occur
Log records can be boolean flagged with diagnostic to note that it is a diagnostic that corresponds to some step of the installation. This can be major, minor, or a full combined with micro path in the taxonomy tree. Diagnostics will not have their own step value but will be related to other step values.
This information should be logged and sent as it is being tested and generated for live views of the installation process. We will not be dealing with logs anymore or asking people to send them.
After these pre-start phases then the installation steps can begin.
crioto
commented
7 years ago
After capturing the system information you will want to run some checks and diagnostics depending on what the user selected. You might later these diagnostics can be optional, like you know the optional memory check before an install (do not do memory check this is an example). Some diagnostics may also be run after installing the component or a minor step. Failing fast is best and reporting options to the user. We want to check (do diagnostics on) a few things:
Log records can be boolean flagged with diagnostic to note that it is a diagnostic that corresponds to some step of the installation. This can be major, minor, or a full combined with micro path in the taxonomy tree. Diagnostics will not have their own step value but will be related to other step values.
This information should be logged and sent as it is being tested and generated for live views of the installation process. We will not be dealing with logs anymore or asking people to send them.
After these pre-start phases then the installation steps can begin.