Bug 753309

Summary: [RFE] Workaround for enable/disable services via persist cmd
Product: [Retired] oVirt Reporter: Perry Myers <pmyers>
Component: ovirt-nodeAssignee: Joey Boggs <jboggs>
Status: CLOSED WONTFIX QA Contact: bugs <bugs>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: cristi.falcas, fdeutsch, hadong, iheim, leiwang, ovirt-bugs, ovirt-maint
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: node
Fixed In Version: 3.1 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-22 12:27:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 753302, 908270    

Description Perry Myers 2011-11-11 20:39:54 UTC
Description of problem:
systemd service enable/disable relies on symbolic links, which we cannot use in a stateless linux environment.  So we need to find a way to work around this limitation in stateless linux support so that we can enable services persistently

Comment 1 cristi falcas 2011-12-01 18:03:03 UTC
I don't know if I'm supposed to respond or not (maybe this was opened just for tracking), but I was thinking that it may work with something like 
- boot a default target that also creates a /etc/systemd/system/custom_target on tmpfs
- change to the custom runlevel

Comment 2 Joey Boggs 2011-12-01 19:05:24 UTC
Cristi, 

Feel free to comment/patch any bugs, your idea is along the same lines I was thinking. If you want to take a stab at it go ahead :)

Comment 3 Fabian Deutsch 2013-10-07 10:38:50 UTC
We should really address this to get a clean solution to enable or disable services at runtime.

This should probably also get a feature page. To be discussed on the next node meeting.

Comment 4 Itamar Heim 2014-02-13 18:31:10 UTC
pushing to target release 3.5, assuming its not planned for 3.4 at this point...

Comment 5 Itamar Heim 2014-06-22 12:27:57 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.

i hope the new envisioned model will address this seamlessly