linux-formula

351 커밋

26 브랜치

트리: f61568373c

Commit Graph

작성자	SHA1	메시지	날짜
Mykyta Karpin	40edd5837f	Fix loopback service status Currently when Salt starts setup-loopback-device service systemd executes losetup command and even if it worked successfully, systemd marks service as inactive(dead). And Salt considers service as dead. In order to fix this behavior, we need to add RemainAfterExit=true to loopback systemd unit template. Other changes: .gitreview added Related Prod: https://mirantis.jira.com/browse/PROD-11760 Change-Id: I6d0c3baf1c22d0a626ff1fd6aaab802c08fb029e	7 년 전
Simon Pasquier	375001e027	Add linux.storage.loopback state This state allows to configure loopback device(s). This isn't meant to be used in production but offers a cheap way to test Cinder with LVM volumes.	8 년 전

작성자

SHA1

메시지

날짜

Mykyta Karpin

40edd5837f

Fix loopback service status

Currently when Salt starts setup-loopback-device service
systemd executes losetup command and even if it worked
successfully, systemd marks service as inactive(dead).
And Salt considers service as dead. In order to fix
this behavior, we need to add RemainAfterExit=true to
loopback systemd unit template.

Other changes:
.gitreview added

Related Prod: https://mirantis.jira.com/browse/PROD-11760

Change-Id: I6d0c3baf1c22d0a626ff1fd6aaab802c08fb029e

7 년 전

Simon Pasquier

375001e027

Add linux.storage.loopback state

This state allows to configure loopback device(s). This isn't meant to
be used in production but offers a cheap way to test Cinder with LVM
volumes.

8 년 전

2 커밋 (f61568373cb5ebfb64439e7e9eb545df40d6ded6)