To view this presentation as a slideshow use the following link: SlideShow.


(NOTES)

This presentation is only a draft of the actual presentation to be given at the review.

It's main purpose is to quickly edit and obtain feedback about the contents of the presentation. Following that, the contents shall be transcribed into a proper presentation that follows the MODAClouds presentation template.

Although it seems there are many slides, only 7 are essential (those marked with two stars ** in their title) which will fit in 5 minutes. There are also 14 more slides if we are asked for details or we have enough time. (The reminder 8 are "meta-slides" like described below.)

In some slides there are paragraphs marked with {X} that are meant as annotations, remarks or presentation directives, and are not part of the actual presentation. Moreover some slides, just like this one, titled (NOTES), are not part of the actual presentation, they just provide meta-details about what is to be presented.

T6.5 -- Deployment and run-time management

Partners: IeAT, Imperial, Flexi, CA;

Roadmap:

Presentation agenda

{X} (NOTE: This slide only highlights the presentation topics.)

(NOTES)

{X} (NOTE: This slide is not part of the actual presentation, it just provides meta-details about what is to be presented.)

The following few slides are meant to accustom the reviewer with the context and concepts of the execution platform and it's relation with the other MODACloud's sub-systems.

The goal is to have a clear understanding of the following concepts:

  • application service vs. platform service;
  • application run-time vs. platform run-time;

Zooming into the run-time **

{X} (TODO: Update the diagram to highlight the execution platform.)

{X} (NOTE: This slide is meant to give the reviewer a mental "you-are-here" point within the MODAClouds "picture".)

http://data.volution.ro/ciprian/645d6602b3dacc60370153703ff1012b/2e6d2cb8467d60889dd7f5b91b9ad438.svg

Actor interactions

{X} (NOTE: This slide can be skipped if time is precious.)

The execution platform interacts mainly with:

Although there could be interactions with:

Inter-task collaborations

{X} (NOTE: This slide can be skipped if time is precious.)

Run-time axes (1)

{X} (NOTE: This slide can be skipped if time is precious.)

Horizontally (based on functionality):

Examples of MODAClouds platform services:

{X} (TODO: Provide a picture highlighting the split, based on a simplified diagram of the architecture.)

Run-time axes (2)

{X} (NOTE: This slide can be skipped if time is precious.)

Vertically (stacked):

{i} (The underlaying infrastructure could be different between the application and platform services.)

{X} (TODO: Provide a picture highlighting the split, based on a simplified diagram of the architecture.)

Primary goals (1) **

The execution platform provides support for both application and platform services.

By handling at run-time:

But also aiding at development-time in:

Primary goals (2) **

All is achieved by providing:

Secondary goals

{X} (NOTE: This slide can be skipped if time is precious.)

There are also a few general guidelines:

(NOTES)

{X} (NOTE: This slide is not part of the actual presentation, it just provides meta-details about what is to be presented.)

The following slides focus on the technical aspects of the execution platform:

  • they start from a top level architectural view;
  • then go through a typical application deployment workflow;
  • then give detailed breakdown of the provided services;
  • and finish with the supported deployment models and providers;

Architecture (1) **

{X} (TODO: Provide a simplified diagram of the architecture, that expands into the full architecture on the next slide.)

http://data.volution.ro/ciprian/645d6602b3dacc60370153703ff1012b/fca246fc8bbdd6df70d84f1d65ef485d.svg

Architecture (2)

{X} (NOTE: This slide can be skipped if time is precious.)

http://data.volution.ro/ciprian/645d6602b3dacc60370153703ff1012b/fca246fc8bbdd6df70d84f1d65ef485d.svg

Application life-cycle (1)

{X} (NOTE: This slide can be skipped if time is precious.)

Development:

Preparation:

{i} (These are only the phases where the execution platform is involved in.)

Application life-cycle (2)

{X} (NOTE: This slide can be skipped if time is precious.)

Deployment:

OAM (Operations, Administration, Maintenance)

{i} (These are only the phases where the execution platform is involved in.)

Sub-systems (1)

{X} (NOTE: This slide can be skipped if time is precious.)

There are three broad categories:

Sub-systems (2)

{X} (NOTE: This slide can be skipped if time is precious.)

Examples of platform sub-systems:

{i} (A complete list in found at https://goo.gl/RXQsxc.)

Supported service models **

Application services:

Platform services:

Supported cloud providers (1)

{X} (NOTE: This slide can be skipped if time is precious.)

Through mOSAIC (IaaS only):

Supported cloud providers (2)

{X} (NOTE: This slide can be skipped if time is precious.)

Through Cloud4SOA (PaaS and IaaS), from M18-M24:

Primary achievements (1) **

/!\ (Bare in mind that this is just the proof-of-concept release.)

Primary achievements (2) **

/!\ (Bare in mind that this is just the proof-of-concept release.)

(NOTES)

{X} (NOTE: This slide is not part of the actual presentation, it just provides meta-details about what is to be presented.)

The following demo consists of a video presenting the deployment of OFBiz ontop of mOSAIC, running on IeAT's Eucalyptus instance.

The script is as follows:

  • it starts from a console, where a tool is used to provision a mOSAIC cluster; (the outcome is an URL to the platform controller;)
  • it then displays the application descriptor used to start the OFBiz application; (the descriptor is a JSON file, listing the OFBiz server and MySQL components; for the OFBiz component it provides as configuration the endpoint of an already executing C-SPARQL instance;)
  • it then shows how the descriptor is loaded into the platform controller WUI, and how the deployment commences;
  • it then lists the two components running, and how the OFBiz server is queried for the HTTP endpoint;
  • it uses the obtained HTTP endpoint to check that OFBiz is indeed running;
  • it also checks the C-SPARQL instance for incoming monitoring data;
  • (optional) it continues by show-casing the mOSAIC features (like logging, stopping a component, or cloning a component);

Demo

...

(NOTES)

{X} (NOTE: This slide is not part of the actual presentation, it just provides meta-details about what is to be presented.)

The following slides, highly technical in nature, are provided in case we need to fill some time. They present the story behind the MODAClouds enhancements on-top of mOSAIC.

Technical outcomes (1)

{X} (NOTE: This slide can be skipped if time is precious.)

ME2 (mOSAIC Execution Environment):

mOS (mOSAIC Operating System):

{i} (Only those available in the current release.)

Technical outcomes (2)

{X} (NOTE: This slide can be skipped if time is precious.)

MySQL component:

mOSAIC and the new mOS / ME2 environments:

{i} (Only those available in the current release.)