220 likes | 366 Views
HyperManager Spinnaker project. Bartek Szejna, OASIS team Round table, 28/05/2013. PLAN. Spinnaker project EConnectWare (ECW) HyperManager upon ECW HyperManager Indicators Implementation Demo Conclusion. PLAN. Spinnaker project EConnectWare (ECW) HyperManager upon ECW
E N D
HyperManager Spinnaker project Bartek Szejna, OASIS team Round table, 28/05/2013
PLAN • Spinnaker project • EConnectWare (ECW) • HyperManager upon ECW • HyperManager Indicators • Implementation • Demo • Conclusion
PLAN • Spinnaker project • EConnectWare (ECW) • HyperManager upon ECW • HyperManager Indicators • Implementation • Demo • Conclusions
Spinnaker project • Transform the current state of the art in RFID-based systems and enable more widespread adoption of the technology, particularly in retail and healthcare sectors • Improve the performance and real-time interconnectivity of wireless-sensing systems • Throughout the supply chain, from manufacturing, distribution, and retail through to the end customer experience. • Lead by TAGSYS • 8 research labs • 4 industrial entities
Spinnaker project • Partners: • INSIDE Secure • Legrand • High-frequency communication • INRIA - OASIS • INP Grenoble – LCIS – ORSYS • Microelectronics Center of Provence • Institut d’électronique et de télécommunications de Rennes • François Rabelais University • ESEO School • University Pierre & Marie Curie Laboratory • Acoustics Laboratory of the University of Maine • Université Paris-Est Marne-la-Vallée – ESYCOM
PLAN • Spinnaker project • EConnectWare (ECW) • HyperManager upon ECW • HyperManager Indicators • Implementation • Demo • Conclusions
Econnectware • By TagsysRFID • New generation for a cloud hosted middleware • Gather RFID information, collected by RFID readers deployed on the client sites (factories, warehouses, shops, etc.) • Set of advanced management and administrative functions • Built using Scalagent JMS • Configuration consist of a server and several gateways
PLAN • Spinnaker project • EConnectWare (ECW) • HyperManager upon ECW • HyperManager Indicators • Implementation • Demo • Conclusions
HyperManager • HyperManager in Spinnaker project (abstraction level) HM ECW Software Other Partners Bare metal, RFID, etc..
HyperManager • Monitor and to act automatically on each element of the architecture L3 HM Supervisor • Offering client oriented facilities • Managing software versioning • Provide cloud-base hosting for customer’s central servers, as an alternative to local hosting on the customer premises L2 ECW Central Gateway HM Customer • Handling configuration and reconfiguration • Orcheastring firmware and software deployment and updates • Monitor the behavior of local gateway events • Report on the health of the ECW Gateway to the upper layer L1 ECW Site Gateway HM Site ECW Site Gateway HM Site • Monitoring the behavior and state of local gateways • Ensuring traceability of local gateways behaviour • Handle failure in an automatic manner L0 HM Gateway HM GW ECW Gateway HM GW HM GW ECW GW ECW GW ECW GW Equipments Equipments Equipments Equipments
HyperManager • Component model L3 HM Supervisor L2 ECW Central Gateway HM Customer L1 ECW Site Gateway HM Site ECW Site Gateway HM Site L0 HM Gateway HM GW ECW Gateway HM GW HM GW ECW GW ECW GW ECW GW Equipments Equipments Equipments Equipments
PLAN • Spinnaker project • EConnectWare (ECW) • HyperManager upon ECW • HyperManager Indicators • Implementation • Demo • Conclusions
HyperManager Indicators • Different Indicators per level • Machine (Cpu, Memory, ...) • Mediation (components, JMS queues,...) • HMI • EPCIS errors • Accessibility by: • JMX • DB • Native library
PLAN • Spinnaker project • EConnectWare (ECW) • HyperManager upon ECW • HyperManager Indicators • Implementation • Demo • Conclusions
HyperManager - implementation • Upon ProActive Parallel Suite • Indicators state exchange between levels: • Pull • Push (critical events) • 19/42 Indicators implemented (25 available) • Automatic event handling – 2 cases • Events stored in DB (Hibernate + SQLite) on L1 • JNI, Plain SQL
HyperManager - implementation HM Customer RM Host with ECW components Site1 GW1 GW2 GW3 Site2 HM Site HM GW HM GW HM GW
PLAN • Spinnaker project • EConnectWare (ECW) • HyperManager upon ECW • HyperManager Indicators • Implementation • Demo • Conclusions
DEMO HM • Main starting host (Antofagasta) • 4 virtual machines • 2 per 1 site • Critical events simulation on Hypermanager level • Temporary solution • NX technology LET’S GO! JMX Simulation ECW
PLAN • Spinnaker project • EConnectWare (ECW) • HyperManager upon ECW • HyperManager Indicators • Implementation • Demo • Conclusion
Conclusion & FUTURE WORK • Extend a list of implemented indicators • GUI improvement • Implement other remaining levels • Lack of support from Tagsys