Bug 766400

Summary: CSProcessor instance on skynet.bne.redhat.com
Product: [Community] PressGang CCMS Reporter: Joshua Wulf <jwulf>
Component: CSProcessorAssignee: Joshua Wulf <jwulf>
Status: CLOSED WORKSFORME QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.xCC: jwulf, lcarlon
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: 2012-01-30 05:26:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
This is the recipe I used to set up the webservice none

Description Joshua Wulf 2011-12-12 00:47:54 UTC 
I set up an instance of the content spec processor on
skynet.bne.redhat.com. 

It is in /opt/contentspec-processor.

It's running on port 8180; it has read-only
access to the skynet database, and read/write access as user csprocessor
to the CSProcessor schema.

I've created a service script for it, and it's set to autostart. It can
be started with "service csprocessor start", but requires termination
from the process ID to stop, because I couldn't figure out how to get
the remote management interface to run on a port that doesn't clash with
the skynet AS 7 instance.
Comment 1 Joshua Wulf 2011-12-12 00:50:59 UTC 
Created attachment 545465 [details]
This is the recipe I used to set up the webservice