On 11-09-12 02:24 AM, Yuji Tokiwa wrote: > Dear Greg, > > Thank you very much for your quick and kind suggestions. > We continue to configure both the epiphan Matterhorn Capture Appliance > (MCA) and the core server. > However they don't work properly now. The status of "Capture Agents" > on "Admin Tools" of the core server does not turn to be "idle".
Do they appear at all? If they are configured as they are below then
they will not be pushing their state to the core. The "Agent State Push
Interval (in seconds)" needs to be set to a positive integer, at which
point the MCA should begin reporting its state to the core again. What
you are seeing in the admin UI is the last known state of the agent,
rather than the current state. This should be made more clear in the
UI, and I believe is already in progress for the 1.3 release.
> May I have further suggestions about configuring the MCA ?
>
> 1. Configuration on Web admin page
> I configured parameters for the MCA on Web admin page like;
>
> Enable Matterhorn {Checked}
> Core Version {1.2.x}
> Core URL {http://core-server:8080}
> Username {matterhorn_system_account}
> Password {CHANGE_ME}
> Agent name {demo_capture_agent}
> Calendar Polling Interval (in minutes) {60}
> Agent State Push Interval (in seconds) {blank}
> Skip Conflicting Captures {Unchecked}
> Maximum Capture Duration (in hours) {8}
> Ingest Interval (in minutes) {60}
>
> I'm afraid that Username, Password, Agent name should be indentical to
> those configured on the core server.
> For Agent name specified in
> /opt/matterhorn/felix/conf/config/services/org.opencastproject.capture.impl.ConfigurationManager.properties
> ---
> # The name of the agent
> capture.agent.name=demo_capture_agent
> ---
This is the demo capture agent's configuration file, not the MCA's. The
MCA does not have a configuration file, instead it has a configuration
GUI as you've already seen.
> Could you please sort out the relationship of parameters between the
> MCA and the core server?
The only parameters which must match between the core and the MCA are:
1) The core's URL
2) The core's version (although this is not a parameter on the core)
3) The username
4) The password
The other parameters are machine specific, so feel free to set them to
values appropriate for your installation.
> 2. Capture device definitions of the epiphan MCA
>
> As we don't specify, for example, /dev/video0 for MCAs because MCAs
> are the appliance device hiding the operating system, I think that
> "Capture device definition" for the networked devices like MCAs is
> different from those exemplified in
> "org.opencastproject.capture.impl.ConfigurationManager.properties"
>
> Would you have any samples for the epiphan MCA ?
There are no Matterhorn specific capture device definitions for the MCA.
The configuration of the capture inputs is done through the admin UI,
look for Stream Setup on the left hand side. There is no way currently
of altering those settings from the core.
G
>
> Reviewing the mailing lists, I appreciate that your work is
> contributing to Matterhorn community.
>
> Best Wishes,
> -----
> Yuji Tokiwa
> Professor
> Research Center for Computing and Multimedia Studies, Hosei University, Japan
> Tel: +81-42-387-6070 Mail: [email protected]
>
>
>
> 2011/9/10 Greg Logan <[email protected]>:
>> On 2011-09-09 6:53 PM, Yuji Tokiwa wrote:
>>> Dear All,
>>>
>>> Nice to meet you. I am new to this community.
>>> Recently we launched Matterhorn project at my university - Hosei
>>> university, Japan.
>>> I'm one of board members of Japanese Sakai community (Ja Sakai) and we
>>> are also planning to deploy Matterhorn project to Japanese
>>> universities as well as Sakai.
>>> Now I am trying to install Matterhorn to my desktop PC. But I have
>>> some problems on connection between "epiphan Matterhorn Capture
>>> Appliance (MCA)" and Matterhorn core server on my desktop PC.
>>> Thank you in advance, I would like to have suggestions from the community.
>>
>> Welcome to Matterhorn! First off, I'll go through some terminology so
>> we're all on the same page. The "core" is the processing
>> machine/cluster which handles processing the media to a streamable
>> format, and then doing that streaming. The CA (Capture Agent) is the
>> reference Java implementation included in Matterhorn. This
>> implementation is run on a separate machine from the core and handles
>> the actual media capture functionality. The core (depending on the
>> configuration) includes a demo CA which uses prerecorded media for
>> demonstration purposes. The MCA is a Epiphan device which implements
>> CA-like functionality, but is an entirely separate code base. I wrote
>> this functionality so you've come to the right place for support :)
>>
>> Comments inline,
>>
>>> 1. System Configuration
>>> 1-1. Capture Agent
>>> - epiphan Matterhorn Capture Appliance (MCA)
>>> (http://www.epiphan.com/products/other-applications/matterhorn/)
>>> - FIRMWARE_VERSION="2.2.0e"
>>>
>>> 1-2. Core Server
>>> - Build on DELL desktop PC from /tags/1.2.0/
>>> - ubuntu 10.10.
>>>
>>> 1-3. Network
>>> - The MCA and the core server are networked on the same network.
>>>
>>> 2. Problems
>>> It seems not to post capabilities to the MCA from the core server.
>>> At the boot-time of the core server, felix generates error message like
>>> follows;
>>>
>>> WARN (AgentConfigurationJob:nnn) - #1 - Unable to post capabilities to
>>> http://{MCA IP address}/.../.../.../configuration
>>
>> The core server contains a demo capture agent, one which records using
>> premade media for demonstration purposes. In this case there is a
>> misconfiguration, see below.
>>
>>> 3. Information we want
>>> I am afraid that we did not configure the MCA and the core server correctly.
>>> About the core server,
>>> "org.opencastproject.capture.impl.ConfigurationManager.properties" may
>>> have wrong parameters.
>>> And about the MCA, in many parameters configured by the Web admin
>>> interface, parameters for "Enable Matterhorn", "Core URL", "Username",
>>> "Agent name" and etc. on the Web admin "Matterhorn" page may be wrong.
>>
>> You are quite correct. There are three places you will need to enter
>> configuration data:
>>
>> 1) The file $FELIX_HOME/conf/config.properties
>> - Full reference at
>> http://opencast.jira.com/wiki/display/MH/Configure+Matterhorn+%28Trunk%29
>> - The important key here is org.opencastproject.server.url. This
>> *MUST* match the URL and port for that machine. Eg:
>> http://my_core.example.org:8080 for the core, and
>> http://my_ca.example.org:8080 for the CA.
>> 2) The file
>> $FELIX_HOME/conf/services/org.opencastproject.capture.impl.ConfigurationManager.properties
>> - The important key is org.opencastproject.capture.core.url, and it
>> defaults to the value of org.opencastproject.server.url in the previous
>> file. On a core you should leave this whole file alone, on the CA this
>> key should be changed to your core's org.opencastproject.server.url value.
>> 3) On the MCA itself (http://{MCA IP address}/admin
>> - Look on the left hand side for Matterhorn. The UI can be very
>> slow at times.
>> - Very important: The version dropdown must be set to the correct
>> Matterhorn version. The MCA will not register with the core otherwise!
>>
>>> I also appreciate to have the sample files for "Core Server" and/or
>>> the screenshot of "Matterhorn view " on MCA's Web admin interface.
>>
>> The system includes demonstration media. Once properly configured you
>> should be able to schedule a capture for the demo_capture_agent. It's
>> not completely up to date, but http://demo.opencastproject.org is a good
>> place to look for a demonstration machine. In this case it's still
>> running 1.1, but basic functionality has not changed.
>>
>>> 4. Miscellaneous
>>> We have done unit test for the MCA and the core server and confirmed
>>> that both systems are working properly.
>>> About the MCS, we can get the live view on our Web browsers from the
>>> MCA with a SONY video camera and a Macbook Pro.
>>> And about the core server, we can generate new contents on Media
>>> Gallery from MOCK samples through the workflow processes.
>>
>> Awesome, you're almost there! The MCA's administration interface has a
>> default username of admin, with a blank password.
>>
>>> I didn't mean to go on so long.
>>> Your collaboration would be very appreciated.
>>
>> Not at all, these are all things that many adopters have experienced.
>>
>> Thanks for using Matterhorn, and let us know (preferably on
>> [email protected]) if you have any more issues!
>>
>> G
>>
>>> Best Wishes,
>>> -----
>>> Yuji Tokiwa
>>> Professor
>>> Research Center for Computing and Multimedia Studies, Hosei University,
>>> Japan
>>> Tel: +81-42-387-6070 Mail: [email protected]
>>> _______________________________________________
>>> Community mailing list
>>> [email protected]
>>> http://lists.opencastproject.org/mailman/listinfo/community
>>>
>>>
>>> To unsubscribe please email
>>> [email protected]
>>> _______________________________________________
>>>
>>
>>
>>
>> _______________________________________________
>> Community mailing list
>> [email protected]
>> http://lists.opencastproject.org/mailman/listinfo/community
>>
>>
>> To unsubscribe please email
>> [email protected]
>> _______________________________________________
>>
> _______________________________________________
> Matterhorn-users mailing list
> [email protected]
> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
