Media mosa architecture - features -10 june 2010

Frans Ward

Technical Product Manager
SURFnet Advanced Services
Frans.Ward@surfnet.nl

MediaMosa:
Architecture & Features
Expertise seminar, 10 juni 2010
MediaMosa, Weblectures & Open Video
`

Agenda

25 min.

SURFnet Video Services
SURFmedia
MediaMosa Architecture
MediaMosa Features
MediaMosa Open Source
MediaMosa Community
MediaMosa Status & Roadmap
5 min.

Questions

3rd generation Video Services
Architecture Requirements

Front-end
• Based on a Service Oriented

SURFmedia
Architecture (SOA)

• Separation of frontend and
backend functionality

• Multiple end-user applications on a
centralized video backend
infrastructure

MediaMosa
• Flexibility: combining components

Back-end
• Performance and High availability

• Scalable for future expansions

• Open source and open source
components !

Expertise seminar: MediaMosa, Weblectures & Open Video, 10 juni 2010
SURFnet. We make innovation work

• Common base for MediaMosa
is Drupal:
✓ Open Source
✓ Content Management System
✓ Web Application Framework
✓ Modulair, Hook-oriented and Scaleable

• Service Oriented Architecture (SOA)
• REST on the outside,
REST on the inside

• Scalability,
Redundancy,
High Availability


Back-end
• Common base for MediaMosa
is Drupal:
✓ Open Source
✓ Content Management System
✓ Web Application Framework
✓ Modulair, Hook-oriented and Scaleable

• Service Oriented Architecture (SOA)
• REST on the outside,
REST on the inside

• Scalability,
Redundancy,
High Availability


REST
Representational State Transfer

• All interactions (messages) with the [GET] .../asset?limit=10
MediaMosa platform are done with REST-calls. <?xml version="1.0"?>
<response>

• REST strictly refers to a collection of network
<header>
<item_count>8</item_count>
<item_count_total>8</item_count_total>
architecture principles which outline how <item_offset>0</item_offset>
resources are deﬁned and addressed. <request_process_time>0.0728</request_process_time>
<request_query_count>55</request_query_count>
<request_result>success</request_result>

• REST is a Client-server, Stateless, <request_result_description></
request_result_description>
Cacheable and Layered protocol. <request_result_id>601</request_result_id>
<request_uri>[GET] asset?
limit=10&user_id=admin&is_app_admin=TRUE</
request_uri>
✓ This reduces the complexity <vpx_version>1.7.3</vpx_version>
</header>
✓ improves the effectiveness of performance <items>
tuning <item id="1">
✓ increases the scalability of pure server <asset_id>ZG3SmyybQ61abezpbVHrJkFF</asset_id>
components ..... etc


Webservices http://mediamosa.org/api
Over 150, divided in services for....

• Play Video (PlayProxy HTML wrapper)
• Authentication (DBUS for EUA)
• Authorization
(Domain, REALM, Group or mixed)
• Upload (PUT, POST, FTP)
• Transcoding
• Media Management: mediaﬁles, assets
and collections
• Search: Contextual Query Language
• Jobs
• Metadata and OAI/PMH
• Notiﬁcation
• Logging and Statistics


Flexible Metadata
Element Sets
Metadata Element Sets Provided:
• Standard Dublin Core (DC)
• Qualified Dublin Core (QDC)
• Learning Object Metadata (IEEE LOM)
• ‘Content Zoek Profiel’ (CZP)
Plus support for own (custom) Metadata Element Sets

CRUD REST-calls on all objects possible. i.e.:
• POST /asset/create?user=John
• GET /asset/$asset_id
• POST /mediafile/$mediafile?filename=NewName
• POST /collection/$coll_id/delete?user=John


Metadata Harvesting
using OAI-PMH
Open Archives Initiative - Protocol for Metadata Harvesting

• is a low-barrier mechanism for repository
interoperability.
• Data Providers are repositories that expose structured
metadata via OAI-PMH.
• Service Providers then make OAI-PMH service
requests to harvest that metadata.
• OAI-PMH is a set of six verbs or services that are
invoked within HTTP.
http://oai.surfmedia.nl/request?verb=Identify
http://oai.surfmedia.nl/request?verb=ListSets
http://oai.surfmedia.nl/request?verb=ListRecords&metadataPrefix=oai_qdc
http://oai.surfmedia.nl/request?verb=ListRecords&metadataPrefix=oai_dc
http://oai.surfmedia.nl/request?verb=ListRecords&metadataPrefix=oai_lom
http://oai.surfmedia.nl/request?verb=ListRecords&metadataPrefix=czp
http://oai.surfmedia.nl/request?verb=ListRecords&metadataPrefix=oai_qdc&set=coll_id:794


Access Management
Default: Media is accessible for everyone.
Option to set access restrictions for playing media on the
following properties:

• Domain, i.e only accessible from surfnet.nl
• Groups of domains, i.e.: Academia group (all universities)
• Realm, i.e. using ASelect, Entree, DigiD, SURFfederation
• Groups of Realms, i.e.: '@teleblik' realm
• User: only give rights to user=john
• Groups of users, i.e.: only give rights to users of group
"class-24".

Combinations of the above are possible! De end-user
application designer decides how and what to use.


Upload Services
• POST upload using End User Application
(limited to 2 GB)

• POST upload directly to MediaMosa Platform
using ticket system (limited to 2 GB)

• HTTP PUT upload using End User Application
(i.e. Java Upload Applet)

• FTP batch upload (“no” limits) including
metadata in XML ﬁle

• Quota per End User Application
MediaMosa
• Support for Master / Slave content sharing
(Provider Application / CLA)


Open Source
GPLv2
Open as in Open Source,
Open Technology, Open
Formats, Open Content,
Open Exchange.

Partner for development:

Main Entry: 1me·dia-mo-sa
Pronunciation: ˈmē-dē-əә-mō-ˈzā
Function: open source software to build a
media management and distribution platform
Release Date: 8 april 2009


MediaMosa: What is included?
✓ The back-end code


✓ The MediaMosa Admin Application


✓ The White Label Enduser Application (WLE)


MediaMosa Community


MediaMosa Community

http://mediamosa.org


• Code repository Subversion (SVN)
• Community Forum
• Documentation
• Issue Tracker
• Online Reference Guide
• Wiki
• Projects:
MediaMosa Building Block for Blackboard
RichMedia EGA for viewing weblecture recordings

Open access
English language
http://mediamosa.org

Planet MediaMosa
WWW
http://mediamosa.org/

Forum
http://mediamosa.org/forum

Lists
announce@lists.mediamosa.org
devel@lists.mediamosa.org
trac@lists.mediamosa.org

Issue Tracker
http://mediamosa.org/trac

Subversion (SVN)
http://mediamosa.org/trac/browser


MediaMosa Status & Roadmap
Available on
mediamosa.org
Release 2.1

Continued development:
2010: Three major releases based on new Drupal 7 framework
Focus to provide a better and more supported
community version for open source development

Some Topics:
• Rich Media - Weblecture recording support
• Transcripting Technology Scout
• MediaMosa Open API / Cloud
• Enhanced support for other content than audio/video


MediaMosa Highlights
★ MediaMosa is the basis for various successful video services
that SURFnet and Kennisnet provide to the Dutch
educational sector

★ Open as in Open Source, Open Technology, Open Formats,
Open Content, Open Exchange, Open Access

★ Options to set access restrictions for playing media

★ Modular and Highly Flexible

★ Features a Rich Feature set

★ New 2.x version introduces many improvements for open
source developers

Todo:
- MediaMosa Demo and Labs environment
- supply VM images for easier startup


Media mosa architecture - features -10 june 2010

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (14)

Similaire à Media mosa architecture - features -10 june 2010

Similaire à Media mosa architecture - features -10 june 2010 (20)

Plus de Andrii Podanenko

Plus de Andrii Podanenko (20)

Dernier

Dernier (20)

Media mosa architecture - features -10 june 2010