[
http://opencast.jira.com/browse/MH-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27501#comment-27501
]
Josh Holtzman edited comment on MH-7978 at 7/6/11 12:07 AM:
------------------------------------------------------------
Capture agent configuration is handled via managed service factory. Create a
file in any watch directory (I put the sample in $FELIX/load) with the
following naming convention and contents:
Filename: org.opencastproject.capture.agent-[something unique].cfg
id=demo_capture_agent
organization=mh_default_org
url=http://some.capture.agent:8080/
schedulerRoles=ROLE_INSTRUCTOR, ROLE_ADMIN
Each file will create a record for a capture agent on the server. Any settings
pushed by the CA will augment the initial values.
was (Author: jholtzman):
Capture agent configuration is handled via managed service factory. Create
a file in any watch directory (I put the sample in $FELIX/load) with the
following naming convention and contents:
Filename: org.opencastproject.capture.agent-[something unique].cfg
id=demo_capture_agent
organization=mh_default_org
url=http://some.capture.agent:8080/
schedulerRoles=ROLE_INSTRUCTOR, ROLE_ADMIN
Each file will create a record for a capture agent on the server. Any settings
pushed by the CA will override the initial values.
> Capture agent admin must associate agents with roles and organizations
> ----------------------------------------------------------------------
>
> Key: MH-7978
> URL: http://opencast.jira.com/browse/MH-7978
> Project: Matterhorn Project
> Issue Type: Task
> Components: Administrative Tools, Architecture & Services
> Affects Versions: 1.3
> Reporter: Josh Holtzman
> Assignee: Josh Holtzman
> Fix For: 1.3
>
> Attachments: ca_config.png
>
>
> We need a source of authority that decides which roles are allowed to
> schedule which capture agents. Further, we need to partition capture agents
> by organization, so a single data source can support multiple tenants on the
> same app server.
> The CaptureAdminService seems a logical choice to store this information. It
> can store ACLs along with capture agent identifiers and organization
> identifiers, and filter the list of capture agents based on the current
> user's org and roles.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________