Bug 907551

Summary: RFE: enable journal-gateway in systemd
Product: [Fedora] Fedora Reporter: Jóhann B. Guðmundsson <johannbg>
Component: systemdAssignee: systemd-maint
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: g.kaviyarasu, johannbg, jonathan, lnykryn, metherid, msekleta, notting, plautrba, sbueno, systemd-maint, vanmeeuwen+fedora, vpavlin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-05 16:17:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jóhann B. Guðmundsson 2013-02-04 17:10:20 UTC
Description of problem:

As I briefly discussed on QA meeting. 

It probably would be nice if Anaconda would enabled the existing systemd journald-gateway ( at least during the development cycle ) to access the journal via HTTP and JSON so log out put could be fetch for automatic/unattended test installs

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Chris Lumens 2013-02-05 15:06:42 UTC
If this is the sort of thing that ought to be set as default, we prefer it to be set as the default in the package itself.  We don't want anaconda to be a store of special-purpose knowledge and hacks.

Comment 2 Kay Sievers 2013-02-05 16:17:03 UTC
Systemd cannot enable anything like that by default. It's under development,
and not supposed to be used by any ordinary user at this moment. It's still
a long way to go, and we will not be quite there for F19.

Comment 3 Jóhann B. Guðmundsson 2013-02-05 20:27:14 UTC
(In reply to comment #1)
> If this is the sort of thing that ought to be set as default, we prefer it
> to be set as the default in the package itself.  We don't want anaconda to
> be a store of special-purpose knowledge and hacks.

I was specifically requesting it to be enabled in anaconda ( since it's running it's own target ) not in the distribution in general but if you dont see the benefit of being able to harvest logs from anaconda via http during the development cycle via automated installation test ( you know something that AutoQA could take advantage of ) I wont pursue it further.

Comment 4 Kay Sievers 2013-02-05 22:22:04 UTC
I totally see the benefit in general, but we should not offer any unfinished
interfaces to the public, also not in anaconda.

It's not only insecure by default, it might also change its interfaces in
the future. It should not be exposed in its current state, only developers
or very specific setups, which are aware of the risks, should use it.

We'll get there when it's ready.