TOSCA Interop SC – Proposed Timeline for Discussion Revised Sept 10, 2012 Matt Rutkowski.

Slides:



Advertisements
Similar presentations
Mapping Service Templates to Concrete Network Semantics Some Ideas.
Advertisements

TOSCA Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard An Open Standard for Business Application Agility and Portability.
Acquia Cloud Drupal Platform-as-a-Service. Market Size [1,00,000+ sites] Innovation [10,000+ modules] Community [500,000+ members] “… is as much a Social.
TOSCA SugarCRM Deployment
INSTALLATION OF WORDPRESS. WORDPRESS WordPress is an open source CMS, often used as a blog publishing application powered by PHP and MySQL. It has many.
TOSCA Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard An Open Standard for Business Application Agility and Portability.
Presented by Mina Haratiannezhadi 1.  publishing, editing and modifying content  maintenance  central interface  manage workflows 2.
Nilesh Mandani Competencies include: Volume Licensing Enterprise Resource Planning Customer Relationship Management Business Intelligence Proposal for.
Slide Index (per Richard’s sugg. / not to be included in video) What is TOSCA? TOSCA Addresses Critical Cloud Challenges TOSCA models integrate the collective.
Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard TOSCA Interoperability Demonstration Join the TOSCA Technical Committee.
Securing LAMP: Linux, Apache, MySQL and PHP Track 2 Workshop PacNOG 7 July 1, 2010 Pago Pago, American Samoa.
Final Year Project Presentation E-PM: A N O NLINE P ROJECT M ANAGER By: Pankaj Goel.
Additional SugarCRM details for complete, functional, and portable deployment.
TOSCA Interoperability Demonstration
Project Proposal: Academic Job Market and Application Tracker Website Project designed by: Cengiz Gunay Client: Cengiz Gunay Audience: PhD candidates and.
Sage ACT! 2011 What’s New?. Why Sage ACT! 2011? Make contact. Build relationships. Get results. Automate key activities with Smart Tasks Eliminate double-entry.
Introduction: Drupal is a free and open-source content management system (CMS). A content management system(CMS) is a computer program that allows publishing,
Creating a Web Presence Introduction to WordPress Week 1.
MobeSys Technologies MobeSys – helping you overcome mobile technology challenges.
SNIA/SSIF KMIP Interoperability Proposal. What is the proposal? Host a KMIP interoperability program which includes: – Publishing a set of interoperability.
Business and Technology Project Integration. The Origin Budgeting from quality information Several disciplines working in isolation Students need to understand.
Open Source CRM’s A Research Study on Java Open Source CRM’s available in the market with special focus on the very popular SugarCRM and integrating it.
Keys to Successful Beta Testing Presented by Ron Dinwiddie, Product Director, Blackboard Commerce Suite™ Jessica Finnefrock, Product Director, Blackboard.
Proposal by CA Technologies, IBM, SAP, Vnomic
Creating a Modern Electronic Medical Records (EMR) System TJHSST Senior Research Project, Quarter 3 Computer Systems Lab Jeremy Chaikind Period.
Customer Relationship Management. Content CRM SugarCRM System Requirement Installation Process Configuration.
SugarCRM LAMP App Deployment Usecase IBM Vnomic. 2 Objective Using an application which is simple, but also presents the most fundamental deployment challenges,
Copyright © 2004 by The Web Services Interoperability Organization (WS-I). All Rights Reserved 1 Interoperability: Ensuring the Success of Web Services.
Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard TOSCA Interoperability Demonstration Join the TOSCA Technical Committee.
Interoperability event proposal Group Name: WG TST Source: Sookhyun Jeon, TTA, Laurent Velez, ETSI, Meeting Date:
Why Proposed TC Procedures? Define how TC reaches “completion” of what OASIS calls “Committee Specifications” TC procedures lead up to the OASIS process:
November 30, 2004 Topics of Discussion Mariela –Introduction –Stage1: Planning Tammy –Stage 2: Analysis Alex –Stage 3: Design Rachael –Stage 4: Construction.
Video Editing Lesson 11. Modules 11.1Review deliverables 11.2Edit videos 11.3Put together business plan 11.4Continue working on prototype.
1 Web Design Project -- Roles Team organization -- roles –Project manager Ann –Business Ed, Ann –Content Georgette, Phil, Doug –Technology Walt, Claudio,
Design within SharePoint Drag-and-drop Configure and draw at the same time No desktop installs No extra purchase Minimized clicks Guided design.
Web Design 3080 – Week 10 Web Project Life Cycle 1.Conceptualization 2.Research 3.Design 4.Content Creation 5.Construction 6.Presentation 7.Test 8.Launch.
© 2013 IBM Corporation OSLC WG Transition **DRAFT** Plan 8 April 2013 Open Services for Lifecycle Collaboration Lifecycle integration inspired by the web.
SugarCRM Use Case: Plans 1. Reminder When a service template is deployed, its implementation artifacts are deployed – From that time on, the operations.
Objective Propose a simple and concise set of “Core” Entities and Relations for TOSCA useful for any application deployment in a cloud Enable users to.
Objective: Enable portability and semi-automatic management of applications across clouds regardless of provider platform or infrastructure thus expanding.
TOSCA Technical Committee Kick-off December 12, 2011.
Interoperability event Sept 2015 Group Name: WG TST Source: Sookhyun Jeon, TTA, Laurent Velez, ETSI, Meeting Date:
Michael van Dijken Marketing Communications Communications Sector Microsoft Corporation.
Slide Index (per Richard’s sugg. / not to be included in video) What is TOSCA? TOSCA Addresses Critical Cloud Challenges The collective knowledge of app.
U.S. Department of the Interior U.S. Geological Survey LSI Constellation Portal Project WGISS #26, Boulder, Colorado, USA September, 2008 Lyndon R. Oleson.
Developing an Interactive Business Division Website.
TOSCA Interoperability Demonstration
Overview of the Web Development Process.  Website Strategic Plan (Planning)  Content and Site Architecture (Planning)  Website Strawman (Planning)
Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard TOSCA Interoperability Demonstration Join the TOSCA Technical Committee.
Objective Propose a simple and concise set of “Core” Entities and Relations for TOSCA useful for any application deployment in a cloud Enable users to.
INFSO-RI Enabling Grids for E-sciencE File Transfer Software and Service SC3 Gavin McCance – JRA1 Data Management Cluster Service.
28 May 2010 HMA-FO Task 2: Feasibility Analysis Service HMA Follow On Activities Task 2: Feasibility Analysis Service (Sensor Planning Service) Monthly.
ADVANCED HOSTING Adrian Newby, CTO.
Service Delivery and Governance
What is a Blog? short for Weblog journal on a website
Service Delivery and Governance
TOSCA Interoperability Demonstration
TOSCA Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard An Open Standard for Business Application Agility and Portability.
Cloud Application Marketplaces
TOSCA Topology and Orchestration Specification for Cloud Applications (TOSCA) Standard An Open Standard for Business Application Agility and Portability.
Cloud Application Marketplaces
Service Model Monitoring Cloud Application Marketplaces
Cloud Application Marketplaces
Cloud Application Marketplaces
Cloud Application Marketplaces
Service Delivery and Governance
Cloud Application Marketplaces
SODI Live Demonstration
Cloud Application Marketplaces
Presentation transcript:

TOSCA Interop SC – Proposed Timeline for Discussion Revised Sept 10, 2012 Matt Rutkowski

OASIS - TOSCA Interop SC Opening Remarks  Interop SC  We are all working together towards same goals…  TOSCA driving the success of a “Cloud Application Marketplace”  TOSCA adoptees benefit from customer confidence in interoperability  This is your SC. Take a less formal format than at TC  Importance of an Interop demo  TOSCA needs to be made “real” for potential customers  A 4Q interop demo would keep TOSCA momentum going  Customers know they have an Interoperable choice on TOSCA

OASIS - TOSCA Interop SC Public Phase (1Q 2013) Stage 2 ~ 3 Weeks Draft and Share initial TOSCA template for “Deployment Scenario” (XML) Company Review of template, Test, Feedback and Finalize Stage 1 ~ 2 weeks Agree on a basic “Deployment Scenario” (likely based upon SugarCRM) Agree on an initial WD Version for initial template (likely WD 11) Stage 4 ~ 2-3 weeks 2-Way Testing using “front end” scenario code Scheduled based upon company reported “Readiness” Selection of first demo venue (minimum 3 companies) TOSCA Interop SC – Proposed 2-Phase Timeline June Private Phase (4Q 2012) Stage 7 ~ Location(s) TBD Additional 1Q Demo(s) Based upon success of N-way tests Discuss & Update demo scenario to latest Working Drafts Stage 3 ~ 2-3 weeks 1-Way Testing of finalized “Deployment Scenario” template from Phase 2 Report status / findings back to SC; adjust template / scenario Stage 5 ~ 2-3 weeks N-Way Testing Tweaking of scenario “front end” code Begin development of scenario “front end” code Begin developing demo “booth” materials Stage 6 ~ Location TBD 4Q Demo: Based upon success of N-way tests Selection of prospective 1Q Demo locations Expand company participants based upon testing success (4Q 2012 and 1Q 2013)

OASIS - TOSCA Interop SC TOSCA Interop Demo Phase 1 – “Private Phase” Work Stages Stage 1: Interop Scenario Discussion (~2 week)  Agree on an initial WD Version for initial template (likely WD 11) –Using latest Current Working Draft 11 seems logical –Can explore when to update to subsequent Working Draft versions as they become available.  Agree on a basic “Deployment Scenario” (likely based upon SugarCRM) –What is compelling content to a prospective TOSCA audience while keeping on pace for 4Q demo? –Customer developed TOSCA template? from TOSCA template marketplace? Identify Companies interested in a 4Q 2012 and 1Q 2013 Interop Activities  Discuss and Capture Agreed-upon scenario… Phase 2 (~3 weeks)  Draft and Share initial TOSCA template for “Deployment Scenario” (XML)  Company Review of XML template, Test/Feedback to SC and Finalize  Discuss template contents (iterative over a few weeks) … Phase 3 (~ 2-3 weeks)  1-Way Testing of finalized “Deployment Scenario” template from Phase 2  Report status / findings back to SC; adjust template / scenario  Begin development of scenario “front end” code Phase 4 (~ 2-3 weeks)  2-Way Testing using “front end” scenario code  Scheduled based upon company reported “Readiness” (from Phase 3 testing)  Selection of first demo venue; would like minimum of 3 companies to participate

OASIS - TOSCA Interop SC 5 Phase 1: The “SugarCRM” Use Case (as “Private” Interop Candidate)  A prototypical, 2-Tier LAMP –Linux, Apache, MySQL, PHP Application  Popular Open Source (community edition) CRM Business Application (v 6.1.5)  Installed in private and public clouds  Supports multiple databases  Can be deployed in 1 or 2 Tier topology  Interop would show deployment of SugarCRM to more than one cloud provider (from a TOSCA template marketplace of some kind) SugarCRM Service (Model) Web Server Tier Apache Web Server SugarCRM Application SugarCRM Application PHP Module DB Server Tier MySQL Server SugarCRM DB Relationship Typed Connector Requirement DB Connection Capability DB Connection HTTP Client Capability HTTP EndPoint Requirement PHP Support Agreement of basic “Deployment Scenario” using TOSCA’s much discussed SugarCRM use case

OASIS - TOSCA Interop SC TOSCA Interop Demo Phase 1 – Items Towards “Public Phase” Looking Ahead - If “Private Phase” goes well and participating companies agree: Stage 5 (~ 2-3 weeks)  Continue N-Way Testing (for those companies committed to 4Q demo)  Tweaking of scenario “front end” code  Develop demo “booth” marketing materials (with OASIS) Stage 6 (Location TBD)  Execute 4Q Demo (Internal to OASIS) (Based upon success of N-way testing)  Selection of prospective 1Q Public Demo locations  Expand scenario to include more TOSCA features & reflect in interop template  Expand demo company participants (based upon continued N-Way testing success)

OASIS - TOSCA Interop SC Next Steps  Interop Scenario Discussion  Publish agreed-upon scenario back to SC and TC  Begin Development of Initial Scenario Template (XML)  Target a first draft XML template for mid-next week for review/comment at SC meeting 2 weeks from now