linux-formula

353 Commit

26 Rami (Branch)

Albero (Tree): c1b619b7f2

Grafico dei commit

Autore	SHA1	Messaggio	Data
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 anni fa
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 anni fa

Autore

SHA1

Messaggio

Data

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 anni fa

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 anni fa

2 Commit (c1b619b7f22c11eda58a184e282af541c3ab1cfc)