Hi.
Straight to the topic. Thanks in advance.
* Does Opencast ingest (or Galicaster) splits a video into several
segments, in order to process each part by different workers, hence
increasing process speed? Otherwise, would it make sense? how could
this be done?
* As we are interested in faster processing, we thought to ingest,
encode and do "as most as possible" with locally attached disk, and
store/publish final videos on NFS. If I understood properly, this
configuration could work. Am I right?
org.opencastproject.storage.dir=/data/nfs-path
org.opencastproject.episode.rootdir=/data/nfs-path
org.opencastproject.workspace.rootdir=/data/local-path
org.opencastproject.staticfiles.rootdir=${org.opencastproject.storage.dir}/staticfiles
org.opencastproject.file.repo.path= ???
* According to list comments, multiple engage nodes requiere a
separate solr node. As stated in
https://docs.opencast.org/latest/admin/modules/searchindex/:
/It is important to understand that a solr server provides exactly
one schema, and one schema only. If you want to cluster both the
workflow service and the search service, you will need two separate
solr servers. These solr servers can run on the same machine, but
each will needs its own servlet container and port./
//
* Does that mean I should have a separate solr server for each of the
following?
#org.opencastproject.solr.dir=${karaf.data}/solr-indexes
#org.opencastproject.search.solr.url=http://solr:8983/solr/
#org.opencastproject.archive.solr.dir=${org.opencastproject.solr.dir}/archive
#org.opencastproject.scheduler.solr.dir=${org.opencastproject.solr.dir}/scheduler
#org.opencastproject.search.solr.dir=${org.opencastproject.solr.dir}/search
#org.opencastproject.series.solr.dir=${org.opencastproject.solr.dir}/series
#org.opencastproject.workflow.solr.dir=${org.opencastproject.solr.dir}/workflow
* Do I have to copy
matterhorn/modules/matterhorn-search-service-impl/src/main/resources/solr/conf,
and
matterhorn/modules/matterhorn-workflow-service-impl/src/main/resources/solr/conf
files to solr servers?
Please, observe documentation is explaining how to deploy a solr,
instead of how opencast should be linked to a solr server (which,
IMHO, might do)
* Why custom_properties contains a
/org.opencastproject.elasticsearch.config.dir/ property? wasn't
opencast using solr already?
* Sorry to bother, but I still haven't figured out the proper values
for a multi-service-node environment. Please, confirm they are ok:
org.opencastproject.organization-mh_default_org.cfg
server=domain.com
prop.org.opencastproject.admin.ui.url=http://admin:8080
prop.org.opencastproject.engage.ui.url=http://engage:8080
custom.properties
org.opencastproject.server.url=https://domain.com #please, note
the httpS
org.opencastproject.jobs.url=engage???
Actually, these aren't working for LTI, but that's another issue.
For sure, more to come...
Regards
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
