Bartek Szejna, OASIS team

Round table, 28/05/2013

HYPERMANAGER SPINNAKER PROJECT

2

PLAN

• Spinnaker project

• EConnectWare (ECW)

• HyperManager upon ECW

• HyperManager Indicators

• Implementation

• Demo

• Conclusion

3

PLAN

• Spinnaker project

• EConnectWare (ECW)

• HyperManager upon ECW

• HyperManager Indicators

• Implementation

• Demo

• Conclusions

4

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

5

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

6

PLAN

• Spinnaker project

• EConnectWare (ECW)

• HyperManager upon ECW

• HyperManager Indicators

• Implementation

• Demo

• Conclusions

7

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

8

PLAN

• Spinnaker project

• EConnectWare (ECW)

• HyperManager upon ECW

• HyperManager Indicators

• Implementation

• Demo

• Conclusions

9

HYPERMANAGER

• HyperManager in Spinnaker project (abstraction level)

ECW

HM

OtherPartners

Bare metal, RFID, etc..

Software

10

HYPERMANAGER

• Monitor and to act automatically on each element of the architecture

Equipments Equipments Equipments Equipments

HMCustomer

ECW CentralGatewayL2

HMSite

ECW SiteGateway

HMSite

ECW SiteGatewayL1

HMGateway

ECWGateway

HMGW

ECWGW

HMGW

ECWGW

HMGW

ECWGWL0

HMSupervisor L3

• Monitor the behavior of local gateway events

• Report on the health of the ECW Gateway to the upper layer

• Monitoring the behavior and state of local gateways

• Ensuring traceability of local gateways behaviour

• Handle failure in an automatic manner

• Handling configuration and reconfiguration

• Orcheastring firmware and software deployment and updates

• 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

11

HYPERMANAGER

• Component model

HMSiteL1

HMGateway

HMGW

Equipments Equipments Equipments Equipments

ECW CentralGateway

ECW SiteGateway

ECW SiteGateway

ECWGateway

ECWGW

ECWGW

ECWGWL0

L2HM

Customer

HMSite

HMGW

HMGW

HMSupervisor L3

12

HYPERMANAGER USE CASE

13

PLAN

• Spinnaker project

• EConnectWare (ECW)

• HyperManager upon ECW

• HyperManager Indicators

• Implementation

• Demo

• Conclusions

14

HYPERMANAGER INDICATORS

• Different Indicators per level

• Machine (Cpu, Memory, ...)

• Mediation (components, JMS queues,...)

• HMI

• EPCIS errors

• Accessibility by:

• JMX

• DB

• Native library

15

PLAN

• Spinnaker project

• EConnectWare (ECW)

• HyperManager upon ECW

• HyperManager Indicators

• Implementation

• Demo

• Conclusions

16

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

17

HYPERMANAGER - IMPLEMENTATION

HMCustomer

Host with ECW components

Site1

RM

HMSite

GW1 GW2 HMGW

HMGW

GW3 HMGW

Site2

18

PLAN

• Spinnaker project

• EConnectWare (ECW)

• HyperManager upon ECW

• HyperManager Indicators

• Implementation

• Demo

• Conclusions

19

DEMO

• Main starting host (Antofagasta)

• 4 virtual machines

• 2 per 1 site

• Critical events simulation on Hypermanager level

• Temporary solution

• NX technologyJMX

HM

ECW

SIMULATIONLET’S GO!

20

PLAN

• Spinnaker project

• EConnectWare (ECW)

• HyperManager upon ECW

• HyperManager Indicators

• Implementation

• Demo

• Conclusion

21

CONCLUSION & FUTURE WORK

• Extend a list of implemented indicators

• GUI improvement

• Implement other remaining levels

• Lack of support from Tagsys

22

QUESTIONS