Commit Graph

8 Commits

Author SHA1 Message Date
Robert Baldyga
83a477683f open-cas.service: Increase start timeout
Signed-off-by: Robert Baldyga <robert.baldyga@intel.com>
2021-11-10 10:56:16 +01:00
Robert Baldyga
b689ca3aa6 open-cas.service: Fix license tag
Open CAS Linux and other projects in the Open CAS repo were always intended
to be released under the OSI-approved BSD 3-Clause License.
Change the license tag to the proper one.

Signed-off-by: Robert Baldyga <robert.baldyga@intel.com>
2021-11-10 10:56:16 +01:00
Robert Baldyga
5d33fce70f Revert "utils: lengthen open-cas service timeout"
This reverts commit 40694e5ef3.

Signed-off-by: Robert Baldyga <robert.baldyga@intel.com>
2021-11-10 10:55:55 +01:00
Rafal Stefanowski
43f43068ad Update copyright statements (2021)
Signed-off-by: Rafal Stefanowski <rafal.stefanowski@intel.com>
2021-01-21 13:15:38 +01:00
Rafal Stefanowski
44b4020cc1 Update copyright statements
Signed-off-by: Rafal Stefanowski <rafal.stefanowski@intel.com>
2020-05-04 16:47:38 +02:00
Jan Musial
cefd12edc5 utils: lengthen settle timeout in open-cas service
Signed-off-by: Jan Musial <jan.musial@intel.com>
2020-01-02 09:35:33 +01:00
liuhongtong
40694e5ef3 utils: lengthen open-cas service timeout
Signed-off-by: liuhongtong <hongtongliu@126.com>
2019-11-29 19:52:01 +08:00
Jan Musial
aaedfb35dd Change startup procedure
Current startup procedure works on an assumption that we will
deal with asynchronously appearing devices in asynchronous way
(udev rules) and synchronous events in the system (systemd units)
won't interfere. If we would break anything (mounts) we would just
take those units and restart them. This tactic was working as long
as resetting systemd units took reasonable time.

As hackish as it sounds it worked in all systems that the software
has been validated on. Unfortunately it stopped working because
of *.mount units taking MUCH longer time to restart even on
mainstream OSes, so it's time to change.

This change implements open-cas systemd service which will wait
synchronously with systemd bootup process for all required Open CAS
devices to start. If they don't we fail the boot process just as
failing mounts would. We also make sure that this process takes place
before any mounts (aside from root FS and other critical FS's) are
even attempted. Now opencas-mount-utility can be discarded.

To override this behaviour on per-core basis you can specify
lazy_startup=true option in opencas.conf.

Signed-off-by: Jan Musial <jan.musial@intel.com>
2019-11-14 12:20:08 +01:00