Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Open Management Using OSGi Technology Enabled Services - Stéphane Frénot, Associate Professor, Inria

239 views

Published on

OSGi World Congress 2005 - Developer Forum Day 2

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Open Management Using OSGi Technology Enabled Services - Stéphane Frénot, Associate Professor, Inria

  1. 1. Open Management UsingOpen Management Using OSGi TechnologyOSGi Technology Enabled ServicesEnabled Services Stéphane Frénot, Phd.Stéphane Frénot, Phd. Associate professorAssociate professor INSA Lyon – CITI - INRIA ArèsINSA Lyon – CITI - INRIA Arès
  2. 2. Classical Access networkClassical Access network SDH DSLAM DSL nodes Home Network Home Network DSLAM DSL nodes DSLAM DSL nodes ✗ Operator oriented network ✗ Current Services (tv, voice...) Connectivity Provider
  3. 3. New Service: user perspectiveNew Service: user perspective • Use case: e-fridgeUse case: e-fridge – Home AutomationHome Automation • Failures: temperature, lightsFailures: temperature, lights • Technical operationTechnical operation – Mass marketingMass marketing • Empty slotsEmpty slots • User preferencesUser preferences • Automatic ordersAutomatic orders
  4. 4. NewNew ParadigmsParadigms: management perspective: management perspective • Multi-Providers, Multi-Services environmentsMulti-Providers, Multi-Services environments – Each provider manages its own servicesEach provider manages its own services (connection, suppliers, users) w/o relying on tiers(connection, suppliers, users) w/o relying on tiers – Deployment and services updatesDeployment and services updates – Managed objects explosionManaged objects explosion – Dynamicity and mobility of these objectsDynamicity and mobility of these objects – Global security modelGlobal security model – Service CooperationService Cooperation
  5. 5. Multi-provider architecture planMulti-provider architecture plan • Multi-provider / Multi-Service architectureMulti-provider / Multi-Service architecture – Overall Architecture and hard pointsOverall Architecture and hard points – Virtual Gateways architectureVirtual Gateways architecture – JMX Management implementationJMX Management implementation • AgentsAgents • ConsoleConsole • Conclusions and evolutionsConclusions and evolutions
  6. 6. Network Overlay of service providersNetwork Overlay of service providers DSLAMDSLAM DSLAM SDH Connectivity Provider
  7. 7. Network Overlay of service providersNetwork Overlay of service providers hard pointshard points UPnP JMX SNMP DSLAMDSLAM DSLAM SDH Service Provider 1 Service Provider 2 Concentrator Concentrator Connectivity Provider
  8. 8. Network Overlay of service providersNetwork Overlay of service providers hard pointshard points ✗Remote Service management •Services and gateways are remotely accessed ✗Service provider isolation •Service should run independently of others ✗Data management •Scatter and dynamic data ✗Mass deployment •Service deployment over many gateways UPnP JMX SNMP DSLAMDSLAM DSLAM SDH Service Provider 1 Service Provider 2 Concentrator Concentrator Connectivity Provider
  9. 9. Virtual Services platformsVirtual Services platforms Service Provider 1 Service Provider 2 Core Gateway Connectivity Provider Virtual Gateway 1 Virtual Gateway 2 PC UPnP device Frigde TV ✗ OSGi core gateways and ✗ embedded virtual OSGi gateways
  10. 10. Virtual services platforms (Overall picture)Virtual services platforms (Overall picture) Service Provider 1 Service Provider 2 Core Gateway Connectivity Provider Virtual Gateway 1 Virtual Gateway 2 PC UPnP device Frigde TV ✗ JMX gateway management ✗ Service combination • Weaving, delegation • Core <-> Virtual (Log) • Virtual <-> Virtual ✗Resource control •Service isolation ✗ OSGi core gateways and ✗ embedded virtual OSGi gateways
  11. 11. JMX management layerJMX management layer Service Provider 1 Service Provider 2 Core Gateway Connectivity Provider Virtual Gateway 1 Virtual Gateway 2 PC UPnP device Frigde TV ✗ Core gateways Host •the JDK standard JMX agent •RmiRegistry •Rmi/http connector •A bundle that represents the core gateway •A remote logger •A remote obr manager •A remote virtual gateway manager ✗ Virtual gateways Host •An embedded JMX agent (MX4J) •JMX/RMI connecting bundles ==> JMX management Console
  12. 12. Gateway management panelGateway management panel ✗Each gateway (core/virtual) has specific tabs ✗This frame is integrated in a JMX Console
  13. 13. JMX ConsoleJMX Console ✗ Runs on top of OSGi ✗ 3 bundles : •Gui layer, Global Components, Gateway Components
  14. 14. Core and Virtual GatewaysCore and Virtual Gateways • Both are OSGi gatewaysBoth are OSGi gateways – A core gateway can run 0-n virtual gatewaysA core gateway can run 0-n virtual gateways – Virtual gateways can get a reference to a core gatewayVirtual gateways can get a reference to a core gateway service (with some restrictions)service (with some restrictions) – Each service provider accesses, owns and managesEach service provider accesses, owns and manages one virtual gateway through its own managementone virtual gateway through its own management protocolprotocol – Core gateway are operated by the network providerCore gateway are operated by the network provider
  15. 15. OSGi Management ModelOSGi Management Model Network Provider Manufacturer Service Platform Server Builds 1 1,* connects Operator uses infrastructure of Owner Service Platform Service Deployement Manager Service Aggregator permits 1 0,* controls 0,* executes 1 1,* owns1 0,*
  16. 16. OSGi Management ModelOSGi Management Model Network Provider Manufacturer Service Platform Server Builds 1 1,* connects Operator uses infrastructure of Owner Service Platform Service Deployement Manager Service Aggregator permits 1 0,* controls 0,* executes 1 1,* owns 1 0,* controls
  17. 17. Evolutions and ImprovementsEvolutions and Improvements • Combination and description of servicesCombination and description of services – Dynamic deployment and discovery of services andDynamic deployment and discovery of services and gatewaysgateways • Service IsolationService Isolation – Real resource control on top of VMReal resource control on top of VM • Security modelSecurity model – Execution securityExecution security – Accessibility securityAccessibility security • End-User managementEnd-User management – A virtual gateway for the end-userA virtual gateway for the end-user
  18. 18. Current development statusCurrent development status • Oscar platformOscar platform – JMX management bundlesJMX management bundles • JMX Wrapper, JMX-RMI connector, Registry, JMX-HTTPJMX Wrapper, JMX-RMI connector, Registry, JMX-HTTP connectorconnector • Service oriented approachService oriented approach – JMX ConsoleJMX Console • JMX Global Components, JMX Components, JMX consoleJMX Global Components, JMX Components, JMX console – OSGi MbeansOSGi Mbeans • OSGi MBean, Remote Logger, OBR, Memory, RealMemoryOSGi MBean, Remote Logger, OBR, Memory, RealMemory – VOSGiVOSGi • Virtual embedded gateway managementVirtual embedded gateway management • Demo available if needed...Demo available if needed...
  19. 19. SupportSupport • MUSE – FP6 – ISTMUSE – FP6 – IST – Alcatel, Thomson, ST-MAlcatel, Thomson, ST-M – Multi-Service access EverywhereMulti-Service access Everywhere – http://www.ist-muse.org/http://www.ist-muse.org/ • Objectweb – opensource communityObjectweb – opensource community – http://www.objectweb.orghttp://www.objectweb.org • INRIA and INSA LyonINRIA and INSA Lyon
  20. 20. Thank you for your attention...Thank you for your attention...

×