Hey Josh, 1.1 branch or trunk? Chris
On Tue, 05 Apr 2011 16:39:22 -0700 Josh Holtzman <[email protected]> wrote: > Right Adam, the remote workflow service is needed here. I just today > fixed a problem with the workflow rest endpoint's POST /update > operation, which looks to be the root of the worker ingest problem. > > Josh > > On Thu, Mar 31, 2011 at 9:41 PM, Adam Hochman > <[email protected]>wrote: > > > Adam, > > This shouldn't be a problem but I think you also need to include > > the remote workflow service as well. Unfortunately there appears > > to be a bug where ingest isn't working with the remote workflow > > service. > > > > The problem may just be a misconfiguration, but our current > > installation docs don't touch on multiple ingest points (or ingest > > on profiles other than admin). On distributed QA (opencast01, 02, > > 03), the ingest profile is deployed with the worker profile. From > > the looks of it, this ingest profile has some redundant services > > found in the other profiles, but I'm not sure if that is causing > > problems. Matterhorn builds successfully so I imagine redundant > > service overwrite one another. Perhaps if you added ingest and > > remote workflow modules to the worker rather than deploying ingest > > profile with worker it will work. > > > > Please update this ticket with your findings.MH-7340 > > > > Thanks. > > ~Adam > > > > > > > > > > On 3/31/11 7:39 PM, Adam Mckenzie wrote: > > > > Hi Everyone, > > > > I just wanted to ask a question about doing a distributed install > > with a slightly different service architecture than usual. We have > > successfully installed an Admin server, 3 worker servers sharing a > > cluster file system and an engage server. Everything is working as > > expected but we would like to make one quick modification. If I > > remove the following modules from the admin's pom profile and add > > them to the worker's: > > > > <module>modules/matterhorn-ingest-service-api</module> > > <module>modules/matterhorn-ingest-service-impl</module> > > > > > > Will this allow the ingests from the capture agents to connect > > directly to the workers thus using the admin only for scheduling > > and the service registry? We want to be able to scale the workers > > fairly easily with the number of classes that need to be recorded > > and this seems easier than scaling up the number of admins. > > > > Thanks, > > Adam > > > > -- > > Adam McKenzie > > MSc Student > > ARIES Laboratory, University of Saskatchewan > > > > Web: http://aries.usask.ca/aiwiki/Adam_McKenzie > > Mail: Advanced Research in Intelligent Educational Systems > > Laboratory Department of Computer Science > > University of Saskatchewan > > 176 Thorvaldson Building > > 110 Science Place > > Saskatoon, SK > > S7N 5C9 > > > > > > _______________________________________________ > > Matterhorn-users mailing > > [email protected]http://lists.opencastproject.org/mailman/listinfo/matterhorn-users > > > > > > _______________________________________________ > > Matterhorn-users mailing list > > [email protected] > > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users > > > > -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
