Docstoc

Putting the BREIN into Amazon EC2

Document Sample
Putting the BREIN into Amazon EC2 Powered By Docstoc
					When Grids meet Business….(or Business meets Grids)




       Bastian Koller, High Performance Computing Center
                 Stuttgart, University of Stuttgart




       11/27/2011            SSAIE Summer School 2009      Page 1
                         Topics

•   Two Scenarios as basis for the work
•   Enhancing the classical SOA Approach
•   Why BREIN needs semantics
•   Architecture Overview




            11/27/2011            SSAIE Summer School 2009   Page 2
                          Why?

• Todays market needs get more and more complex every day
    – Outsourcing non-core competencies („let the experts do what they are
      good at“)
    Collaboration is strongly needed
• Setting up this collaborations is still difficult and extremely costly,
  difficult to realize and manage
         • Whilst huge market players do not depend on outsourcing, this model
           becomes more and more popular for economic reasons
         • But strong implications for Small and Medium Enterprises
             – Decreased level of competetiveness
             – Usually bound to offer their special service, no enhancement
               possible without investment of high sums


            11/27/2011                SSAIE Summer School 2009               Page 3
                        Realistic business requirements through
                        challenging scenarios – the VE Scenario
Vision:
Generation of significant new business opportunities in software and
services by exploiting the capability of GRID computing to analyse large
numbers of independent design solutions quickly, cheaply and in a secure
fashion
• Find and use low cost computational resources for outsourcing
   purposes
• Enable automation (for a fair price)
• Secure and reliable management needed




           11/27/2011              SSAIE Summer School 2009           Page 4
                          Realistic business requirements through
                          challenging scenarios – the Airport Scenario
Vision:
Advance current means of logistics airport operations, which are designed to handle
point-to-point flights, to allow for virtual hub flights.
• A virtual hub flight is one that is being implemented by coupling two
   independent passenger flights (i.e. its passengers, baggage, and related
   information) offered by two different airlines).
                                              Airport                                               Airport
                                                 A                                                     R




                                              Airport             Virtual                           Airport
                                                 B                 Hub                                 S




                                              Airport                                               Airport
                                                 C                                                     T
                                                                  Flight operated by Airline #1
                                                                  Flight operated by Airline #2
                                                                  Virtual Hub Flight



             11/27/2011                SSAIE Summer School 2009                                   Page 5
                               New advantages, new problems
                                  Advantages                                    Problems
                       - New business: e-Commerce
ICT and
                       - New opportunities: enterprises                 Problems to manage
Internet
                       connection by Internet
                       -Tasks in business processes
                                                                        - More enterprises in the
                       outsourced to expert enterprises
                                                                        supply chain-> Complexity to
+Outsourcing           - Customer can create own complex
                                                                        manage
                       from third parties
                                                                        - Difficult insertion of SMEs
                       services with specifics need
                       - No need of investments and
                                                                        - Application providers
                       maintenance of licenses: pay-per-use
+SaaS                                                                   require more computing
                       - SMEs part of business as services
                                                                        capacities on demand
                       consumers
                                                                        -Needs of technical staff
                       - Computing capacities outsourced
                                                                        - Difficulty in management
+Intelligent           - Sharing and coordinating the
                                                                        enterprise collaboration
Grid                   use of diverse resources
                                                                        - Needs of interoperability,
                       - SME part of business
                                                                        reliability
               11/27/2011                    SSAIE Summer School 2009                          Page 6
                          So…..

• End-users need simplicity
    – It is currently too difficult for real business users to use the Grid,
      respectively eCollaboration middlewares
    – They typically do not have the expertise required for the technical setup
• Real business users need reliability
    – Current Grid service provision is not reliable enough for them to trust
• Collaboration tends to become too huge and complex for effective
  planning and management




            11/27/2011                 SSAIE Summer School 2009                 Page 7
                        What are the requirements of business
                        entities
• Requirements
   – Companies want to provide services, not individual resources
   – The service provider wants to see its goals pursued at all time whilst
     keeping ist ability to take decisions (based on SLAs)
   – Customers and service providers want to have their own business policies
     pursued (and reflected in the SLAs?)
   – Simple and affordable access to the framework
   – Enhanced competiteveness for all business participants
   – Business entities want to be able to rely on the framework and its
     robustness (based on SLAs)




           11/27/2011               SSAIE Summer School 2009               Page 8
                        BREIN main objective

• Create an infrastructure that will increase the level and dynamism of
  collaborations among companies, with special focus on SMEs
                                       or
• To realise the flexible, intelligent Virtual Organisation support to
  significantly reduce the complexity of modern day business-to-business
  collaborations. Companies and enterprises of any size will be able to
  compete equally in a complex and demanding market.

• Technical perspective: The use of Grid, semantic web and multi-
  agents concepts to create this dynamic, intelligent and adaptable
  infrastructure.



           11/27/2011              SSAIE Summer School 2009           Page 9
                             In simple words….

• Autonomy and Automation
    – Integration of Multiagent and Semantic Web concepts into the Grid to expand its
      potential
• Optimisation
    – With respect to the individual business goals and needs. Use of Multiagent
      concepts/technologies to enable self-* mechanisms and to minimize the need of
      inference of end-users
• Semantic-Aware Security
    – Enhance security mechanisms with semantic web technology to close the existing gap
      between high-level business requirements and lower-level system security policies and
      mechanisms.
• Reduced Complexity
    – Simplified provisioning and usage of services
    – Increased support for defining and enacting business objectives
• Foster existing Results
    – No start from scratch, base on results from recent and running projects



             11/27/2011                     SSAIE Summer School 2009                     Page 10
BREIN, SOA and how it can be
enhanced




    11/27/2011   SSAIE Summer School 2009   Page 11
                    Classical SOA Collaboration
                    Support
Customer                                                Service Provider



                    Application / HMI Layer

                       Resource Layer

                      Middleware Layer

                        Network Layer


       11/27/2011            SSAIE Summer School 2009                Page 12
                                          Classical SOA VO Architecture




                                                                                                                  BP Engine
                               Security




                                                                                     Security
                    Policies




                                                                                                Policies
           SLAs




                                                                                                           SLAs
                                          GW                             GW                                                   Resources
Customer




                                               Collaboration Workflows

                                           Membership Management

                                                  VO Management




                  11/27/2011                              SSAIE Summer School 2009                                               Page 13
                      Classical SOA Collaboration
                      Support
  Customer                                                Service Provider



                      Application / HMI Layer

                        One (Virtual) Layer
                         Resource Layer

through which users can interact, participate in collaborations
                      Middleware Layer
        etc. with a maximum degree of transparency

                          Network Layer


         11/27/2011            SSAIE Summer School 2009                Page 14
                     Enhancements
                                   Service Owner                                           resources




                                                                                 Wrapper
                                                                                  Agent
                Business Goals &
                     Policies




                                                              Negotiate / Plan



                                                                                 Wrapper
                                                                                  Agent
   Customer




                                                                                 Wrapper
                                                                                  Agent
Requirements




        11/27/2011                 SSAIE Summer School 2009                                     Page 15
                              Enhanced SOA VO Architecture




                                     BP Engine




                                                 Wrapper
       Security

                  Policies




                                                  Agent
                             SLAs
GW
                                                               Planning

                                                           SelfManagement


                                    Semantic Mapping

                             Artificial Intelligence Layer

                             Human Machine Interfaces




 11/27/2011                                        SSAIE Summer School 2009   Page 16
       Just a simple example….


  …or…how you can maximize chaos with a simple
                 request…




11/27/2011            SSAIE Summer School 2009   Page 17
                        A Customer needs something

                                                                 I am offering
      I need
                                                               something…with
   something…I
                                                              an execution time
  need this with a
                                                              between 8 and 12
   duration of 10                                                I can with
                                                                    minutes
                                                              execution time

   Welcome to Babel
      minutes

       Can you
      But need
      But II need
       provide?
     with duration
     with duration


Customer                                                   Service Provider




           11/27/2011           SSAIE Summer School 2009                      Page 18
                                       Innovation through integration – an
                                       example
•   Overall objective:
    simplify the life of Service Providers and Customers by                                     Customer &
    allowing for semantically enhanced and agent support                                        Business
    handling of the Service Level Agreement lifecycle                                           Interactions

•   BREIN SLA approach
                                                                                             Define
     – semantically annotating SLAs and Templates
     – mapping to lower level infrastructure terms
     – configuring available resources                                                  Business
•   Agents support this process                                                       requirements
     – interpretation and negotiation of SLAs
•   Contracting experience in agent community                      Interpret
     – FIPA Contract net protocol                                                                       Fulfil
                                                                   Negotiate
     – Provides more flexibility than the “usual”                                       Semantic
       Discrete Offer mechanisms                                                       Description
•   Development of a specification of                                                                  Service
    Semantically Annotated Service Level                            Agents                              Level
    Agreements (SA-SLAs)
                                                                                     Configure/Drive Agreements


                  11/27/2011                              SSAIE Summer School 2009                         Page 19
Where are we now?




   11/27/2011   SSAIE Summer School 2009   Page 20
                                       Architecture Building Blocks
                                       Gathers
                                       SLA related
                                       info                 BR Management
                                                                                                 Asks for
                                                                                                 providers
                                                                 Triggers
                         Access                                  negotiation
                         rights   SLA Management                                      WF Management
         Security




                                                               Management Group

                                                                       Data for
                                                                     evaluation           Triggers
                                                                                                             Provides
                                                                                          adaptation
                                                                                                             plan
                                                                                                                        Customer’s
                                                                                          actions
                                            Uses basic                                                                    GOAL
                                            capabilities

                                                                         Adaptation          Planning

                                                                             Agents based capabilities
Tokens
                    Configures                                                             Uses basic
                                                              Data for                     capabilities
                                                            evaluation
                                                     Uses semantic
                                                     components
              Infrastructure Capabilities                                    Semantic Infrastructure
                                                  Infrastructure Group




                     27/11/2011                              SSAIE Summer School 2009                                    Page 21
                        Building Block Role

• Business Relationship Management:
   – Establish and maintain relationships: finding partners, maintaining
     information about them, take decisions on the basis of past experience
   – Semantic technology for supporting discovery, historical information
     analysis
• SLA Management:
   – Management of the whole SLA lifecycle: negotiation, SLA monitoring,
     SLA evaluation
   – Semantic technology for business terms translation, multiagent technology
     for negotiation
• WF Management:
   – Reduce complexity in managing workflow
   – Semantic technology for dynamic workflow concretization, multiagent
     technology for adaptation support
           27/11/2011                SSAIE Summer School 2009                 Page 22
                           Building Block Role

• Adaptation & Planning:
    – Coordinated planning and dynamic adaptation capabilities
    – Multiagent technology to support planning and adaptation, semantic to support
      agents reasoning
• Infrastructure Capabilities:
    – Virtualization, encapsulation, notification, resource management
    – Semantic and agent technology for resource management
• Security:
    – Secure distributed business collaboration
    – Web service technology for security context provisioning, user controlled
      authorization, claim based security for legacy protocols
• Semantic infrastructure:
    – Provides an unified framework for dealing with semantic metadata
    – Semantic metadata annotation service, ontology management service, reasoning

              27/11/2011                  SSAIE Summer School 2009                Page 23
One final remark



    Business Stakeholders need to be integrated in all
    development processes




      11/27/2011            SSAIE Summer School 2009     Page 24
             Ask these guys for a business grid solution




11/27/2011            SSAIE Summer School 2009      Page 25
             And you get something like this




11/27/2011            SSAIE Summer School 2009   Page 26
             And you get this reaction…




11/27/2011           SSAIE Summer School 2009   Page 27
You want the flyer and the dissemination CD!!!




   11/27/2011       SSAIE Summer School 2009   Page 28
Thank you
                   Questions?



  For more information: www.gridsforbusiness.eu



  11/27/2011          SSAIE Summer School 2009    Page 29
                                     Focus on the Semantic Enhancements
            The SLA translator is an ontology repository, which allows for
            managing the local domain ontology. Within it, the Party   Third
                                                                             domain rules
            are formalized. The Translator is a component in both domains.
         Customer Domain                                         <<Semantic Infrastructure>>
                                                                   Ontology Repository
                  The Ontology Repository is a third party storage, where
                                          retrieveOntology


                     Service Providers as well as Customers can store their
          <<Semantic Infrastructure>>
                SLA Mediator

                                                                    parties Domain
               Ontologies to make them available for other Service Provider and vice
                           versa, other parties can query this for ontologies
      evaluate           translate

                                                                                                                    <<Semantic Infrastructure>>
                   <<Semantic Infrastructure>>                    <<Semantic Infrastructure>>                           SLA Translator
                       SLA Translator                                  SLA Mediator             translate



  SLA Negotiator
                                                                                                            SLA Optimizer
                                                 negotiate


                                                                                query
   negotiate    The SLA Mediator is able to match SA-SLA requests and offers, by
             converting SLA documents from other domains (e.g. bids or templates)
<<WF Management>>                                          SLA Negotiator          optimize
   VIM Enactor
               into the local SLA model to be usable inside the respective domain. It
                                      acknowledge


            can either query the Translator for the matching Ontology or, in case the
                                                                                   SATSLA Template Repository
                                                                          party
                 Ontology is not available, request this from a thirdretrieve Ontology
               Provider. With the Mediator, the high level SLA Parameters (between
               Provider and Customer) can be mapped down to the Service Provider
                Infrastructure level. The Mediator is a component in both domains.
          11/27/2011                                         SSAIE Summer School 2009                                                     Page 30
                                                      The negotiation sequence on the SP side
SP : SLA Negotiator       SP : SLA Optimizer     SP : SLA Mediator        SP : SLA Translator            SP : Risk Manager   SP : Business Policies Provider   : SRLM




               1 : optimize()




                                        2 : query()
                                                             3 : translate()


                                                             4 : Ontology
                                                            5 : map()


                                    6 : mapped terms

                                                             7 : estimateRisk()


                                                                     8 : Risk
                                                                                9 : getPolicies()

                                                                                  10 : Policies



                                                                                          11 : checkAvailability()


                                                                                                12 : Availiability
                                 13 : optimizeOffer()


              14 : SLAOffer*




                       11/27/2011                                                SSAIE Summer School 2009                                                       Page 31
LESSONS LEARNT:



   II. It is good to have a lot of experience




     11/27/2011             SSAIE Summer School 2009   Page 32
                         Focus

• Focus on a subset of problems first, don´t try to solve everything at
  once




            11/27/2011              SSAIE Summer School 2009              Page 33
                         Barriers for the adoption of Grid

• Security: application designed with security in mind are accessible
  outside the initial environment(department).
• Lack of standards -> interoperability (WS-* standards are complex)
• Complexity of Grid middleware -> selection of other alternatives.
• Reliability, risk of rely on external Service Providers, (out of your
  control)
• Licensing issues
• Cultural barrier of the IT staff.




            27/11/2011              SSAIE Summer School 2009              Page 34
Back to Babel




    11/27/2011   SSAIE Summer School 2009   Page 35
   I need
                                           Service Provider Domain                     I need the
 something                           duration                                        duration =
                                     Yes we can!!                                    ontology for
with duration                         = ???                                       execution time!!!
                                                                                    this customer




                                                                                SLA Mediator


          The SLA translator is an ontology repository, which allows for
                                                          Here you are
                                                   Within it, the domain rules
          managing the local domain ontology. able to match SA-SLA requests and offers, by
                             The SLA Mediator is
                           converting SLA is a component in both domains.
          are formalized. The Translatordocuments from other domains (e.g. bids or templates)
                            into the local SLA a third be usable inside the respective domain. It
             The Ontology Repository is model toparty storage, where
                          can either query as Translator for the matching Ontology or, in case the
                Service Providers as wellthe Customers can store their
                              Ontology not available, request this from a vice
            Ontologies to make themisavailable for other parties and third party Ontology
                            Provider. With the Mediator, the high level SLA
                  versa, other parties can query this for ontologies Parameters (between
                            Provider and Customer) can be mapped down to the Service Provider
                                                  SLA Translator
                               Infrastructure level. The Mediator is a component in both domains.


                  11/27/2011                         SSAIE Summer School 2009                        Page 36
                                            Semantically Enhanced Negotiation
                                                                                                                             Third Party
                               Customer Domain
                                                                                                                      <<Semantic Infrastructure>>
                                                                                                                        Ontology Repository


                                                     <<Semantic Infrastructure>>
                                                          SLA Mediator

                                                                                                   retrieveOntology

<<WF Management>>
   VIM Enactor                                                                                                                             Service Provider Domain
                                                 evaluate             translate

                                                                                                                                                                        <<Semantic Infrastructure>>
                                                                <<Semantic Infrastructure>>                      <<Semantic Infrastructure>>                                SLA Translator
                                                                    SLA Translator                                    SLA Mediator                translate
                 negotiate

                                          SLA Negotiator                                                                                   <<Infrastructure>>
SLA Repository                                                                                                                                   SRLM
                                                                                                                                                                        <<Adaptation & Planning>>
                                                                                              negotiate                                                                 Business Policies Provider
                    storeSLA
                                                                                                                                query
                                                                                                                                        checkAvailability
                                                                                                                                                            getPolicies

                                                                                                                                                                           <<Adaptation & Planning>>
                                                                                              acknowledge                                                                      Risk Manager
                                                                                                                                    SLA Optimizer



                                                                                                                                                                     estimateRisk




                                                                                                                                                              <<Business Relationship Management>>
                                                                                                                                                                       Reputation Store
                                                                                                                         optimize




                                                                                                                         SLA Negotiator        checkReputation



                                                                                                                                               retrieve               SATSLA Template Repository


                                                                                                             informManager

                                                                                                                                    storeSLA
                                                                                                                 SLA Manager                              SLA Repository



         11/27/2011                                                                SSAIE Summer School 2009                                                                                    Page 37

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:7
posted:11/26/2011
language:English
pages:37