Bug 864653

Summary: Need a REST API to request the log directory of a cartridge
Product: OKD Reporter: chris alfonso <calfonso>
Component: MasterAssignee: Lili Nader <lnader>
Status: CLOSED UPSTREAM QA Contact: libra bugs <libra-bugs>
Severity: low Docs Contact:
Priority: medium    
Version: 2.xCC: adietish, ccoleman, dmcphers, hbrock, mfisher, wdecoste
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-01-29 18:58:50 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 chris alfonso 2012-10-09 20:57:29 UTC
Description of problem:
Need a REST API to request the log directory of a cartridge.  Currently, we have to make an assumption on the location of the log directory.  Ideally, we would be able to look this up on a cartridge property.

Although there maybe be a property that contains the log directory of a cartridge, there is no way to know the property is the log directory.  For instance, the node-js cartridge has properties":[{"name":"OPENSHIFT_NODEJS_LOG_DIR","description":"Directory to store application log files.","type":"environment"}]  But we can't count on the existence of _LOG_ in the name to properly identify the environment variable.

Comment 1 Dan McPherson 2012-10-09 21:59:25 UTC
This should probably be a story.

Comment 2 Clayton Coleman 2012-10-15 14:48:46 UTC
The other option is for there to be a script on the node via SSH that aggregates the logs, and for the CLI to invoke that and stream its output.  Then users could tweak it on their gears.

Comment 3 Dan McPherson 2013-01-29 00:04:17 UTC
*** Bug 876721 has been marked as a duplicate of this bug. ***

Comment 4 Dan McPherson 2013-01-29 18:58:50 UTC
Created US3373 to track.