[PQSWPRG-7343] Featureimage/systemd deps#424
Merged
Conversation
…em (start-db-services.in)
…em (factory-reset-live.sh.in)
…stead of hardcoding
…stead of hardcoding (ipc-meta-setup.service.in)
… first, to reduce log noise
…out of natural order
…n for experiments
…f new fty-core defined targets
…just before the end to be sure nobody enables it
…rget, not by the service
…t after EULA is accelted
…asic.target and so an ordering cycle
…arget and other high-profile units for first boot. Autostart only bios-pre-eula.target and fty-license-accepted.target; the latter service should enable the consumers disabled here
…start with/after multi-user.target
…et (and so before bios/ipm2)
…ial boot, and un-mask after EULA
…t relax the check that IPC is listened after start so consumers can start up
…ces during run-time
…ystemd/ not into /etc/... (for NUT units)
…r, it is RequiredBy+PartOf fty-license-accepted.target and breaks units that began initializing already
…nerated) timer implementations
…emd-deps as of 2020-03-24
… only wait for them if the OS is not currently shutting down (systemctl blocks on wait in this case)
…emctl stop --wait for the last step
…emergency targets in addition to shutdown/recovery
…services during OS shutdown
… sec is too long, half the test suite can not connect in case of a crash
…Exec* lines and update the comment about bios.service
…emd-deps as of 2020-04-03
… touch-file to enforce bios-shutdown.target staying active
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The centerpiece of service dependency and trackable milestone rearrangement (adding several intermediate target units and services to manage stuff as a bundle, and work around systemd deficiencies), to make startups and shutdowns of the system and selected services faster, more predictable and less conflicting. Greatly reduces the first-boot footprint (and so time taken to present the wizard).
As a side effect, not easy and quite pointless to excise into a separate PR (at best, would be a required prerequisite to merge the specifically service-related commits), this changeset changes hardcoded paths to delivered files into configure/build-time defined template expansions that should result in same strings as it is for the curent product bundling.
Accompanied by smaller PRs, mostly to reference these targets and/or further real required services, in numerous other components. Related changes in other 42ity components include:
[PQSWPRG-7343] Featureimage/systemd deps fty-asset#129
[PQSWPRG-7343] Featureimage/systemd deps fty-security-wallet#53
Support optional NUT_NOCONF_ALLOWED=true in upsd (and enable for 42ity by default) nut#102
[PQSWPRG-7343] Featureimage/systemd deps fty-alert-engine#235
[PQSWPRG-7343] Featureimage/systemd deps fty-alert-flexible#86
[PQSWPRG-7343] Featureimage/systemd deps fty-alert-list#79
[PQSWPRG-7343] Featureimage/systemd deps fty-alert-stats#22
[PQSWPRG-7343] Featureimage/systemd deps fty-config#27
[PQSWPRG-7343] Featureimage/systemd deps fty-discovery#93
[PQSWPRG-7343] Featureimage/systemd deps fty-email#81
[PQSWPRG-7343] Featureimage/systemd deps fty-info#135
[PQSWPRG-7343] Featureimage/systemd deps fty-kpi-power-uptime#52
[PQSWPRG-7343] Featureimage/systemd deps fty-mdns-sd#38
[PQSWPRG-7343] Featureimage/systemd deps fty-metric-ambient-location#10
[PQSWPRG-7343] Featureimage/systemd deps fty-metric-composite#66
[PQSWPRG-7343] Featureimage/systemd deps fty-metric-compute#44
[PQSWPRG-7343] Featureimage/systemd deps fty-metric-snmp#22
[PQSWPRG-7343] Featureimage/systemd deps fty-metric-store#45
[PQSWPRG-7343] Featureimage/systemd deps fty-metric-tpower#66
[PQSWPRG-7343] Featureimage/systemd deps fty-nut#220
[PQSWPRG-7343] Featureimage/systemd deps fty-outage#52
[PQSWPRG-7343] Featureimage/systemd deps fty-sensor-env#50
[PQSWPRG-7343] Featureimage/systemd deps fty-sensor-gpio#89
[PQSWPRG-7343] Featureimage/systemd deps fty-shm#33
[PQSWPRG-7343] Featureimage/systemd deps fty-srr#23
[PQSWPRG-7343] Featureimage/systemd deps fty-warranty#31
Thoroughly tested as a feature image, deploys much faster than original state and fails less often in the CI runs (the few issues that were occasionally seen in certain components blocking the shutdown rarely, are backlogged).