Ongoing extensions tools and use cases for improving OCCI adoption in industry.

1. 1
INDUSTRIAL OCCI
January 15th 2014, OGF-40, Oxford
Jean Parpaillon

2. 2
INDUSTRIAL OCCI
MOTIVATION
OPEN CLOUD = STANDARDS + OPEN SOURCE + ...
January 15th 2014, OGF-40, Oxford
Jean Parpaillon

3. 3
INDUSTRIAL OCCI
STANDARDS ARE...
STANDARDS
=
FREEDOM (YEAH !)
CONCURRENCY
NEGOCIATIONS
RnD COSTS
USER POV
PROVIDER POV
January 15th 2014, OGF-40, Oxford
Jean Parpaillon

4. 4
INDUSTRIAL OCCI
STANDARDS SHOULD (CAN) BE...
Reusable technology
= RnD savings
January 15th 2014, OGF-40, Oxford
Interoperability
= Broader audience
Jean Parpaillon
Ecosystem
= Partnerships

5. 5
INDUSTRIAL OCCI
USE CASE: COMPATIBLE ONE
CLOUD BROKER
CompatibleOne
January 15th 2014, OGF-40, Oxford
TECHNOLOGY
* Services providers interop
* SLA enforcement
* Monitoring
* Pure OCCI based
* Extern: prOCCI
* Intern: OCCI agents
Jean Parpaillon

6. 6
INDUSTRIAL OCCI
USE CASE: ITEA2-ICARE
CLOUD-ENABLED
BROADCASTING
* Media Assets Management
* Transcoding
* Fingerprinting
* CDN
January 15th 2014, OGF-40, Oxford
Jean Parpaillon
TECHNOLOGY
* Transcoding API: OCCI
* Generic framework for
cloud web services: erocci

7. 7
INDUSTRIAL OCCI
USE CASE: LIZENN
IoT platform
* IoT related services brokering
* IT assets management
* Usage sharing
January 15th 2014, OGF-40, Oxford
Jean Parpaillon
TECHNOLOGY
* OCCI based
* erocci framework
* Not only HTTP transport

8. 8
INDUSTRIAL OCCI
EXTENDING OCCI
OCCI Core
Renderings
Typing: date, regexp, category, etc.
FSM: used in models, not formal
Separation transport/rendering
JSON
XML
Extensions
Tools
Foundations:
SLA, security, credentials
Domain specific:
PaaS, transcoding, ERP,
etc.
January 15th 2014, OGF-40, Oxford
Frameworks
Extensions management
Interoperability tests
Jean Parpaillon

9. 9
INDUSTRIAL OCCI
OCCI CORE: typing
CURRENT
(formal)
PROPOSED
string
string
CURRENT
(extensions)
XML Schema inspired
IP address
enum
Base types
* String
* Integer
* Date
* etc,
number
number
range
January 15th 2014, OGF-40, Oxford
Jean Parpaillon
Extensions/Restrictions
* Enumerations
* Regexps
* Ranges

10. 10
INDUSTRIAL OCCI
OCCI CORE: FSM
Seen in Infrastructure
suspended
suspend
inactive
January 15th 2014, OGF-40, Oxford
Proposal
e.g.: Debian packages
start
active
stop
Software resource
start
States
* installed
* configured
* removed (let config files)
* uninstalled (incl. config)
* etc.
Actions
* install
* reconfigure
* remove
* purge
Jean Parpaillon
<action ...
orig="suspended,inactive"
dest="active" />

11. 11
INDUSTRIAL OCCI
OCCI RENDERING: JSON
Existing
Rationale
Draft specification
Implementations: CompatibleOne, etc.
Attributes:
{ occi :
{ compute :
{ core : 4 } } }
Javascript clients
Web interfaces
Requests:
{ resources :
[ ... ] }
January 15th 2014, OGF-40, Oxford
Jean Parpaillon
or { "occi.compute.core" : 4 }
or { [ ... ] }

12. 12
INDUSTRIAL OCCI
OCCI RENDERING: XML
Proposal
Rationale
XML Schema for OCCI schema
XSD based attributes typing
Variants:
* erocci:
* XSD describes OCCI types
* Resources validated against OCCI
schema
* CompatibleOne:
* XSD describes an extension
* resources validated against XML
schema
XML based protocols (XMPP)
Tools: validation, parsing, generation
Schemas: extensive typing
January 15th 2014, OGF-40, Oxford
Jean Parpaillon

13. 13
INDUSTRIAL OCCI
OCCI PROTOCOL
Current
Proposal
No separation protocol (transport)
/representation
* Describes protocol in separate doc
* CRUD-like
* Queries
* Filters
* Describes rendering independantly.
* Easy for tree-like structures (JSON,
XML):
* data is a node
* protocol is an enclosing node
* Really need to extend to text/plain ?
Issues
Non-HTTP transports: file, XMPP, etc
Implementations:
parsers may needs context (query,
collection, entity, etc)
January 15th 2014, OGF-40, Oxford
Jean Parpaillon

14. 14
INDUSTRIAL OCCI
OCCI EXTENSIONS
CORDS
Domain specific
Extensive OCCI based model
Brokering, domain specific, generic
Intern (multi-agents) and extern
(prOCCI)
Brokering
IaaS: federation, ipaddres, ...
PaaS: software package, ...
HPC: job, workload, ...
CompatibleOne
Publication
Operator
Enquiry
Placement
January 15th 2014, OGF-40, Oxford
Generic
SLA (ws-agreement inspired):
agreement, terms, ...
Session
User
Jean Parpaillon

15. 15
INDUSTRIAL OCCI
OCCI META-EXTENSIONS
Rationale
Legacy applications use
meta-model based stds
Create meta-model to
OCCI connectors
January 15th 2014, OGF-40, Oxford
LDAP
User management
Jean Parpaillon
SNMP
Monitoring
SNMP agent as a sensor
MIB extension as a sensor
mixin

16. 16
INDUSTRIAL OCCI
OCCI TOOLS
CLIENT PROTOCOL
occi_renderer_occi
occi_renderer
occi_renderer_json
occi_renderer
occi_renderer_xml
occi_listener_http
parse
occi_listener_xmpp
based on cowboy
based on exmpp
occi_listener
occi_listener
render
occi_category
occi_renderer
occi_category_mgr
occi_store
parse
mount
/
/myobjects
create
load
update
delete
render
occi_backend
supervisor
supervisor
load
occi_hook
on_save
on_load
on_update
on_delete
on_action
supervisor
</occi:extension>
occi_hook_mgr
occi_backend_mnesia
backend
backend
call
occi_hook_mgr
C hook
STORAGE
occi_hook_mgr
Java hook
January 15th 2014, OGF-40, Oxford
<?xml >
<occi:extension>
<occi:kind>
...
</occi:kind>
notify
erlang hook
occi_backend_riak
instantiate
Jean Parpaillon
APPLICATION APPLICATION
MODEL
LOGIC
categories
description

17. 17
INDUSTRIAL OCCI
THAT'S ALL FOLKS !
January 15th 2014, OGF-40, Oxford
Jean Parpaillon